Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #177141 > unrolled thread
| Started by | roba@openmailbox.org |
|---|---|
| First post | 2017-01-30 22:50 +0100 |
| Last post | 2017-02-04 03:00 +0100 |
| Articles | 10 on this page of 30 — 6 participants |
Back to article view | Back to linux.debian.user
CUPS in stretch Ricoh printer SP112 SP112-su roba@openmailbox.org - 2017-01-30 22:50 +0100
Re: CUPS in stretch Ricoh printer SP112 SP112-su Mark Fletcher <mark27q1@gmail.com> - 2017-01-31 00:00 +0100
Re: CUPS in stretch Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-01-31 00:10 +0100
Re: CUPS in stretch Ricoh printer SP112 SP112-su roba@openmailbox.org - 2017-01-31 00:40 +0100
Re: CUPS in stretch Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-01-31 10:30 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su roba@openmailbox.org - 2017-01-31 23:20 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-02-01 00:10 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su roba@openmailbox.org - 2017-02-01 00:50 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-02-01 01:00 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su roba@openmailbox.org - 2017-02-01 01:00 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su roba@openmailbox.org - 2017-02-01 01:20 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-02-01 11:00 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Roba <roba@openmailbox.org> - 2017-02-01 15:20 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-02-01 16:40 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Roba <roba@openmailbox.org> - 2017-02-01 23:00 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-02-02 00:30 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-02-02 01:00 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-02-02 21:10 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Roba <roba@openmailbox.org> - 2017-02-04 02:30 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Roba <roba@openmailbox.org> - 2017-02-04 02:50 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Mark Fletcher <mark27q1@gmail.com> - 2017-02-04 07:00 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Roba <roba@openmailbox.org> - 2017-02-04 13:20 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-02-04 16:40 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Roba <roba@openmailbox.org> - 2017-02-05 00:10 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Gene Heskett <gheskett@shentel.net> - 2017-02-05 00:50 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-02-05 01:10 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Roba <roba@openmailbox.org> - 2017-02-05 01:50 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Brian <ad44@cityscape.co.uk> - 2017-02-08 22:00 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Lisi Reisz <lisi.reisz@gmail.com> - 2017-02-23 15:50 +0100
Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su Roba <roba@openmailbox.org> - 2017-02-04 03:00 +0100
Page 2 of 2 — ← Prev page 1 [2]
| From | Mark Fletcher <mark27q1@gmail.com> |
|---|---|
| Date | 2017-02-04 07:00 +0100 |
| Subject | Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su |
| Message-ID | <t71y9-4vz-3@gated-at.bofh.it> |
| In reply to | #177370 |
On Sat, Feb 04, 2017 at 01:42:00AM +0000, Roba wrote: > /etc/cups/cupsd.conf (I thought whereis would have found it, I am wrong) > > # Show general information in error_log. > LogLevel warn > MaxLogSize 0 > Listen /var/run/cups/cups.sock > Listen /var/run/cups/cups.sock > Browsing On > BrowseLocalProtocols dnssd In my _working_ CUPS on Jessie, I have : Listen /var/run/cups/cups.sock Listen 192.168.11.5:631 which I find fascinating, as 192.168.11.5 is _NOT_ the IP address of my computer, yet somehow it works anyway. The port scan you did a reply or two ago showed you had something listening on UDP port 631, but nothing on TCP port 631, which is why printing is not working. Indulge us, and add a line to your cupsd.conf as follows: Listen localhost:631 and restart CUPS and see what happens. Assuming that works, you are going to want to know why it was necessary to add it, and I am afraid I have no idea. I can tell you though, for what use this is, it is _NOT_ a direct cause of the wheezy --> jessie upgrade. I performed that upgrade (a good while ago, to be fair) and did not experience this problem. So in the absence of better information I'd have to guess something you did or something else you installed resulted in this happening to your conf file. I really have no idea what that could be though. Mark
[toc] | [prev] | [next] | [standalone]
| From | Roba <roba@openmailbox.org> |
|---|---|
| Date | 2017-02-04 13:20 +0100 |
| Subject | Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su |
| Message-ID | <t77tU-hQ-7@gated-at.bofh.it> |
| In reply to | #177372 |
Yes, this worked without specifying an ip just localhost:631 The upgrade was from jessie to stretch and I had never edited this file, yesterday I didn't even know where it was. If this line is by default in this file and this file pre-existed on jessie how could that line be omitted? Or was the upgrade from cups 1.7 to 2.2?? replacing this file? My frustration as I recommend to others to leave their non-open non-free systems and trying debian is that after a successful installation their basic utilities (of an average Win7 user) are there. No shell command writing or editing script files. It seems as this is not the case as it is with 20% of packages installed not working with a particular desktop, etc. In the case of a near-sighted person leading the blind some experience is not very confidence inspiring. Most of the manuals have an extensive administration and programmer experience as a prerequisite. In other words I have yet to find ONE debian manual page that explains one thing without knowledge of many other things that appear as common knowledge but are a foreign language to many of us mortals. And it is getting more complex instead of being simplified. >In my _working_ CUPS on Jessie, I have : >Listen /var/run/cups/cups.sock >Listen 192.168.11.5:631 >which I find fascinating, as 192.168.11.5 is _NOT_ the IP address of my >computer, yet somehow it works anyway. The port scan you did a reply or >two ago showed you had something listening on UDP port 631, but nothing >on TCP port 631, which is why printing is not working. >Indulge us, and add a line to your cupsd.conf as follows: >Listen localhost:631 >and restart CUPS and see what happens. >Assuming that works, you are going to want to know why it was necessary >to add it, and I am afraid I have no idea. I can tell you though, for >what use this is, it is _NOT_ a direct cause of the wheezy --> jessie >upgrade. I performed that upgrade (a good while ago, to be fair) and >did >not experience this problem. So in the absence of better information >I'd >have to guess something you did or something else you installed >resulted >in this happening to your conf file. I really have no idea what that >could be though. >Mark Mark Fletcher: >In my _working_ CUPS on Jessie, I have : Listen /var/run/cups/cups.sock Listen 192.168.11.5:631 which I find fascinating, as 192.168.11.5 is _NOT_ the IP address of my computer, yet somehow it works anyway. The port scan you did a reply or two ago showed you had something listening on UDP port 631, but nothing on TCP port 631, which is why printing is not working. Indulge us, and add a line to your cupsd.conf as follows: Listen localhost:631 and restart CUPS and see what happens. Assuming that works, you are going to want to know why it was necessary to add it, and I am afraid I have no idea. I can tell you though, for what use this is, it is _NOT_ a direct cause of the wheezy --> jessie upgrade. I performed that upgrade (a good while ago, to be fair) and did not experience this problem. So in the absence of better information I'd have to guess something you did or something else you installed resulted in this happening to your conf file. I really have no idea what that could be though. Mark
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-02-04 16:40 +0100 |
| Subject | Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su |
| Message-ID | <t7aBs-2oh-5@gated-at.bofh.it> |
| In reply to | #177372 |
On Sat 04 Feb 2017 at 14:55:18 +0900, Mark Fletcher wrote: > On Sat, Feb 04, 2017 at 01:42:00AM +0000, Roba wrote: > > /etc/cups/cupsd.conf (I thought whereis would have found it, I am wrong) > > > > # Show general information in error_log. > > LogLevel warn > > MaxLogSize 0 > > Listen /var/run/cups/cups.sock > > Listen /var/run/cups/cups.sock > > Browsing On > > BrowseLocalProtocols dnssd > > In my _working_ CUPS on Jessie, I have : > > Listen /var/run/cups/cups.sock > Listen 192.168.11.5:631 > > which I find fascinating, as 192.168.11.5 is _NOT_ the IP address of my > computer, yet somehow it works anyway. The port scan you did a reply or You don't mean localhost:631 works, surely? What is 192.168.11.5? Does cupsd run on it? > two ago showed you had something listening on UDP port 631, but nothing > on TCP port 631, which is why printing is not working. Exactly. > Indulge us, and add a line to your cupsd.conf as follows: > > Listen localhost:631 > > and restart CUPS and see what happens. It would solve his problem. > Assuming that works, you are going to want to know why it was necessary > to add it, and I am afraid I have no idea. I can tell you though, for > what use this is, it is _NOT_ a direct cause of the wheezy --> jessie > upgrade. I performed that upgrade (a good while ago, to be fair) and did > not experience this problem. So in the absence of better information I'd > have to guess something you did or something else you installed resulted > in this happening to your conf file. I really have no idea what that > could be though. There is nothing in the postinst script for cups which would replace a "Listen localhost:631" line. Easily tested with apt-get --reinstall install cups -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Roba <roba@openmailbox.org> |
|---|---|
| Date | 2017-02-05 00:10 +0100 |
| Subject | Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su |
| Message-ID | <t7hCV-7B2-1@gated-at.bofh.it> |
| In reply to | #177393 |
Brian: > On Sat 04 Feb 2017 at 14:55:18 +0900, Mark Fletcher wrote: >> Indulge us, and add a line to your cupsd.conf as follows: >> >> Listen localhost:631 >> >> and restart CUPS and see what happens. > > It would solve his problem. > > There is nothing in the postinst script for cups which would replace a > "Listen localhost:631" line. Easily tested with > > apt-get --reinstall install cups Are you repeatedly denying what I have repeatedly said or is it that you just don't know and can't guess? For the rest of the people following the thread I can assure you that neither I or has there been anybody "physically" that has touched this pc and omitted this line. I have no idea whether the update from jessie to stretch would replace this file, I assume it is not the same as the packages are different so the conf I suspect it might be different, I don't know. That would put this change within the past 2-3 weeks. Unless I read specific instructions form a reliable source to edit a conf. file I don't go about messing with them, I know that much. So for me the puzzle remains, for Brian the explanation maybe I sleepwalk and change things unconsciously.
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-02-05 00:50 +0100 |
| Subject | Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su |
| Message-ID | <t7ifD-7Ri-5@gated-at.bofh.it> |
| In reply to | #177425 |
On Saturday 04 February 2017 18:04:00 Roba wrote: > Brian: > > On Sat 04 Feb 2017 at 14:55:18 +0900, Mark Fletcher wrote: > >> Indulge us, and add a line to your cupsd.conf as follows: > >> > >> Listen localhost:631 > >> > >> and restart CUPS and see what happens. > > > > It would solve his problem. > > > > There is nothing in the postinst script for cups which would replace > > a "Listen localhost:631" line. Easily tested with > > > > apt-get --reinstall install cups > > Are you repeatedly denying what I have repeatedly said or is it that > you just don't know and can't guess? For the rest of the people > following the thread I can assure you that neither I or has there been > anybody "physically" that has touched this pc and omitted this line. > I have no idea whether the update from jessie to stretch would replace > this file, I assume it is not the same as the packages are different > so the conf I suspect it might be different, I don't know. That would > put this change within the past 2-3 weeks. > > Unless I read specific instructions form a reliable source to edit a > conf. file I don't go about messing with them, I know that much. Do you want it fixed, or do you just want to whine about it? I don't know why the paranoia over security has caused that to be removed some years ago, but those of us with well isolated home networks have been putting that line back in our /etc/cups/cupsd.conf for years. If you refuse to do it, take your whine on down the hall where there might be some cheese and maybe some pickles to go with it. > So for me the puzzle remains, for Brian the explanation maybe I > sleepwalk and change things unconsciously. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-02-05 01:10 +0100 |
| Subject | Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su |
| Message-ID | <t7iz0-8eJ-17@gated-at.bofh.it> |
| In reply to | #177426 |
On Sat 04 Feb 2017 at 18:44:04 -0500, Gene Heskett wrote: > On Saturday 04 February 2017 18:04:00 Roba wrote: > > > Brian: > > > On Sat 04 Feb 2017 at 14:55:18 +0900, Mark Fletcher wrote: > > >> Indulge us, and add a line to your cupsd.conf as follows: > > >> > > >> Listen localhost:631 > > >> > > >> and restart CUPS and see what happens. > > > > > > It would solve his problem. > > > > > > There is nothing in the postinst script for cups which would replace > > > a "Listen localhost:631" line. Easily tested with > > > > > > apt-get --reinstall install cups > > > > Are you repeatedly denying what I have repeatedly said or is it that > > you just don't know and can't guess? For the rest of the people > > following the thread I can assure you that neither I or has there been > > anybody "physically" that has touched this pc and omitted this line. > > I have no idea whether the update from jessie to stretch would replace > > this file, I assume it is not the same as the packages are different > > so the conf I suspect it might be different, I don't know. That would > > put this change within the past 2-3 weeks. > > > > Unless I read specific instructions form a reliable source to edit a > > conf. file I don't go about messing with them, I know that much. > > Do you want it fixed, or do you just want to whine about it? I don't know > why the paranoia over security has caused that to be removed some years > ago, but those of us with well isolated home networks have been putting > that line back in our /etc/cups/cupsd.conf for years. If you refuse to > do it, take your whine on down the hall where there might be some cheese > and maybe some pickles to go with it. A problem was stated and diagnosed and a solution offered. Up to now, the OP hasn't even had the grace to say what the solution did for him. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Roba <roba@openmailbox.org> |
|---|---|
| Date | 2017-02-05 01:50 +0100 |
| Subject | Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su |
| Message-ID | <t7jbH-8uq-5@gated-at.bofh.it> |
| In reply to | #177426 |
Thank you very much Gene, You are the first person to ever mention that "the line was removed" for security paranoia, not that I mistakenly removed it by mistake over the past few months of it running under jessie and not running under stretch. This is what I wanted to find out, why did this happen. Now it DOES make sense. I arrest my case! You can have the pickles I am allergic and you must have a craving for them for mentioning them, save one for Brian! Gene Heskett: > > Do you want it fixed, or do you just want to whine about it? I don't know > why the paranoia over security has caused that to be removed some years > ago, but those of us with well isolated home networks have been putting > that line back in our /etc/cups/cupsd.conf for years. If you refuse to > do it, take your whine on down the hall where there might be some cheese > and maybe some pickles to go with it. > >> So for me the puzzle remains, for Brian the explanation maybe I >> sleepwalk and change things unconsciously. > > > Cheers, Gene Heskett >
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-02-08 22:00 +0100 |
| Subject | Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su |
| Message-ID | <t8Hvl-56F-65@gated-at.bofh.it> |
| In reply to | #177428 |
On Sun 05 Feb 2017 at 00:39:00 +0000, Roba wrote: > Thank you very much Gene, > You are the first person to ever mention that "the line was removed" for > security paranoia, not that I mistakenly removed it by mistake over the > past few months of it running under jessie and not running under > stretch. This is what I wanted to find out, why did this happen. > Now it DOES make sense. > > I arrest my case! This is a case of the perfect memory versus the contents of cups' postinst script. The "perfect memory" is accessible to only one person; the postinst script is accessible to everyone. All the somebodies (that could be the OP if he feels inclined to other than speculation and ad hominem) could examine it and point out where it replaces 'Listen localhost:631' with something else. Not that it is important in the grand scheme of things, but having a technical detail or two wouldn't break the bank. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2017-02-23 15:50 +0100 |
| Subject | Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su |
| Message-ID | <te2Su-2AJ-5@gated-at.bofh.it> |
| In reply to | #177425 |
On Saturday 04 February 2017 23:04:00 Roba wrote: > Brian: > > On Sat 04 Feb 2017 at 14:55:18 +0900, Mark Fletcher wrote: > >> Indulge us, and add a line to your cupsd.conf as follows: > >> > >> Listen localhost:631 > >> > >> and restart CUPS and see what happens. > > > > It would solve his problem. > > > > There is nothing in the postinst script for cups which would replace a > > "Listen localhost:631" line. Easily tested with > > > > apt-get --reinstall install cups > > Are you repeatedly denying what I have repeatedly said or is it that you > just don't know and can't guess? For the rest of the people following > the thread I can assure you that neither I or has there been anybody > "physically" that has touched this pc and omitted this line. > I have no idea whether the update from jessie to stretch would replace > this file, I assume it is not the same as the packages are different so > the conf I suspect it might be different, I don't know. That would put > this change within the past 2-3 weeks. > > Unless I read specific instructions form a reliable source to edit a > conf. file I don't go about messing with them, I know that much. > > So for me the puzzle remains, for Brian the explanation maybe I > sleepwalk and change things unconsciously. Do stop being so rude to one of the most helpful and knowledgeable people on the list who is trying to help you. Lisi
[toc] | [prev] | [next] | [standalone]
| From | Roba <roba@openmailbox.org> |
|---|---|
| Date | 2017-02-04 03:00 +0100 |
| Subject | Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su |
| Message-ID | <t6XNT-1Lb-9@gated-at.bofh.it> |
| In reply to | #177369 |
/etc/cups/printers.conf # Printer configuration file for CUPS v2.2.1 # Written by cupsd # DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING <DefaultPrinter RICOH-SP-112SU-DDST> UUID urn:uuid:========deleted============== Info RICOH SP 112SU DDST Location hubbabubba MakeModel Ricoh Aficio SP 100, pstoricohddst-gdi 0.5 alpha DeviceURI usb://RICOH/SP%20112SU%20DDST?serial=X004MB30122&interface=1 State Stopped StateMessage Unplugged or turned off StateTime 1486071181 ConfigTime 1485807894 Reason paused Type 8392772 Accepting Yes Shared Yes JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job </DefaultPrinter> <Printer RICOH_SP_112SU_DDST> UUID urn:uuid:================================= Info RICOH SP 112SU DDST Location Here DeviceURI usb://RICOH/SP%20112SU%20DDST?serial=X004MB30122&interface=1 State Stopped StateMessage Unplugged or turned off StateTime 1486071181 ConfigTime 1485812060 Reason paused Type 8388612 Accepting Yes Shared Yes JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 AllowUser xxxx AllowUser yyyy AllowUser zzzz AllowUser xtxtxtx OpPolicy default ErrorPolicy retry-job Option number-up 4 </Printer> Roba: > Let us see. > I HAVE explained I have done nothing to alter what existed from "stock" > in Jessie (when cups) did work from the browser, right? > Now it does not and I HAVE DONE NOTHING other than upgrading from stable > to testing. And cups does not work. Now how would your question > address this issue? > > You want to see output published here on the list but your email does > not really exist, so you read the list from elsewhere. That makes me > wonder with who or what am I talking to. > > $ whereis cupsd.conf > cupsd: /usr/sbin/cupsd /usr/share/man/man8/cupsd.8.gz > > $ ls -al /usr/sbin/cup* > -rwxr-xr-x 1 root root 174416 Jan 19 15:44 /usr/sbin/cups-browsed > -rwxr-xr-x 1 root root 27980 Feb 16 2016 /usr/sbin/cups-genppdupdate > -rwxr-xr-x 1 root root 10232 Jan 18 15:06 /usr/sbin/cupsaccept > -rwxr-xr-x 1 root root 10232 Jan 18 15:06 /usr/sbin/cupsaddsmb > -rwxr-xr-x 1 root root 10232 Jan 18 15:06 /usr/sbin/cupsctl > -rwxr-xr-x 1 root root 416328 Jan 18 15:06 /usr/sbin/cupsd > lrwxrwxrwx 1 root root 10 Jan 18 15:06 /usr/sbin/cupsdisable -> > cupsaccept > lrwxrwxrwx 1 root root 10 Jan 18 15:06 /usr/sbin/cupsenable -> > cupsaccept > -rwxr-xr-x 1 root root 26920 Jan 18 15:06 /usr/sbin/cupsfilter > lrwxrwxrwx 1 root root 10 Jan 18 15:06 /usr/sbin/cupsreject -> > cupsaccept > > Anything else I can help you with? > Because it doesn't seem any more that I am seeking help from someone who > wants to help but from someone who wants to interrogate and arrogantly > wants to make anybody seem inferior. If that really matters to you, I > do not know and I do not wish to compete with any experts for the > position of the expert. It is not even that extreme for me to make the > damn printer work. > > BUT > > If CUPS worked and one does nothing to affect it (consciously at least > because I'd rather do work than be fiddling with debian bugs) and after > some upgrade/update it doesn't I suspect it is a bug on behalf of the > system and not MY PROBLEM. Because if I had left the damn thing alone > unupdated in its old stable state I wouldn't be here asking questions. > > I suspect this is not what DEBIAN as a community want or expect. > > Now if we can address the issue and not the bearer of the symptom we can > become constructive again. > > > > > > > Brian: >> On Wed 01 Feb 2017 at 23:58:15 +0000, Brian wrote: >> >>> On Wed 01 Feb 2017 at 23:21:00 +0000, Brian wrote: >>> >>>> When cupsd starts (as yours has done) it listens for incoming connections >>>> on port 631 for tcp and tcp6. Print jobs are sent to port 631. A browser >>>> connects to tcp port 631. Your netstat output shows no listening on tcp >>>> port 631. No wonder http://localhost:631 will not work. >>>> >>>> Reason? No idea, but that is problem. It could lie with your cupsd.conf >>>> in /etc/cups. Or something you have done with the networking setup. >>> >>> The default cupsd.conf has the line >>> >>> Listen localhost:631 >>> >>> Does yours? >> >> A simple enough question. Well? >> > >
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.debian.user
csiph-web