Your message dated Thu, 5 Apr 2018 18:27:13 +0100 with message-id <[email protected]> and subject line Re: Bug#894664: cups: Libreoffice doesn't see my network printer has caused the Debian Bug report #894664, regarding cups: Libreoffice doesn't see my network printer to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 894664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894664 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: cups Version: 2.2.1-8+deb9u1 Severity: normal Dear Maintainer, I have a printer connected via USB to a local server (running Debian stable as well). This printer is made visible to my clients by running cups-browsed. My clients have no locally-configured printers (and hence no "default" printer), and indeed when I go to "localhost:631" I don't see any printers there. Yet, this somehow works: e.g. evince sees my network printer just fine. But Libreoffice doesn't. I haven't tried all applications to figure out which do and which don't, so maybe Libreoffice is not the only one affected. I've seen bug#867818 which seems related, but my `cups` is an older version than the one that seems to be affected by that problem. I've also seen bug#772097, but that one seems older than mine (back around that time, cups-browsed would actually cause the network printer to appear in /etc/cu0ps/printers.conf and in localhost:631 and Libreoffice could see it fine then). -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-3-686-pae (SMP w/4 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cups depends on: ii cups-client 2.2.1-8+deb9u1 ii cups-common 2.2.1-8+deb9u1 ii cups-core-drivers 2.2.1-8+deb9u1 ii cups-daemon 2.2.1-8+deb9u1 ii cups-filters 1.11.6-3 ii cups-ppdc 2.2.1-8+deb9u1 ii cups-server-common 2.2.1-8+deb9u1 ii debconf [debconf-2.0] 1.5.61 ii ghostscript 9.20~dfsg-3.2+deb9u1 ii libavahi-client3 0.6.32-2 ii libavahi-common3 0.6.32-2 ii libc-bin 2.24-11+deb9u3 ii libc6 2.24-11+deb9u3 ii libcups2 2.2.1-8+deb9u1 ii libcupscgi1 2.2.1-8+deb9u1 ii libcupsimage2 2.2.1-8+deb9u1 ii libcupsmime1 2.2.1-8+deb9u1 ii libcupsppdc1 2.2.1-8+deb9u1 ii libgcc1 1:6.3.0-18+deb9u1 ii libstdc++6 6.3.0-18+deb9u1 ii libusb-1.0-0 2:1.0.21-1 ii poppler-utils 0.48.0-2+deb9u2 ii procps 2:3.3.12-3 Versions of packages cups recommends: ii avahi-daemon 0.6.32-2 ii colord 1.3.3-2 ii cups-filters [ghostscript-cups] 1.11.6-3 pn printer-driver-gutenprint <none> Versions of packages cups suggests: ii cups-bsd 2.2.1-8+deb9u1 pn foomatic-db-compressed-ppds | foomatic-db <none> ii hplip 3.16.11+repack0-3 ii printer-driver-cups-pdf [cups-pdf] 2.6.1-22 ii printer-driver-hpcups 3.16.11+repack0-3 pn smbclient <none> ii udev 232-25+deb9u2 -- Configuration Files: /etc/cups/cupsd.conf changed: LogLevel warn MaxLogSize 0 SystemGroup lpadmin Listen localhost:631 Listen /var/run/cups/cups.sock Browsing On BrowseLocalProtocols dnssd DefaultAuthType Basic WebInterface Yes <Location /> Order allow,deny </Location> <Location /admin> Order allow,deny </Location> <Location /admin/conf> AuthType Default Require user @SYSTEM Order allow,deny </Location> <Policy default> # Job/subscription privacy... JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default # Job-related operations must be done by the owner or an administrator... <Limit Create-Job Print-Job Print-URI Validate-Job> Order deny,allow </Limit> <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document> Require user @OWNER @SYSTEM Order deny,allow </Limit> # All administration operations require an administrator to authenticate... <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices> AuthType Default Require user @SYSTEM Order deny,allow </Limit> # All printer operations require a printer operator to authenticate... <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs> AuthType Default Require user @SYSTEM Order deny,allow </Limit> # Only the owner or an administrator can cancel or authenticate a job... <Limit Cancel-Job CUPS-Authenticate-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit> <Limit All> Order deny,allow </Limit> </Policy> <Policy authenticated> # Job/subscription privacy... JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default # Job-related operations must be done by the owner or an administrator... <Limit Create-Job Print-Job Print-URI Validate-Job> AuthType Default Order deny,allow </Limit> <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document> AuthType Default Require user @OWNER @SYSTEM Order deny,allow </Limit> # All administration operations require an administrator to authenticate... <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default> AuthType Default Require user @SYSTEM Order deny,allow </Limit> # All printer operations require a printer operator to authenticate... <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs> AuthType Default Require user @SYSTEM Order deny,allow </Limit> # Only the owner or an administrator can cancel or authenticate a job... <Limit Cancel-Job CUPS-Authenticate-Job> AuthType Default Require user @OWNER @SYSTEM Order deny,allow </Limit> <Limit All> Order deny,allow </Limit> </Policy> -- debconf information: cupsys/backend: lpd, socket, usb, snmp, dnssd cupsys/raw-print: true
--- End Message ---
--- Begin Message ---On Thu 05 Apr 2018 at 11:28:51 -0400, Stefan Monnier wrote: > Is "local" above meant to refer to the DNS domain appended to the host > (i.e. does it mean the complete host name that was tried is > "server.local")? Yes. > > Till, Stefan has provided quite a lot of information (is it enough?). > > Are we looking at a misconfiguration, a tweak to cups-browsed.conf or > > a bug? > > Hmm... now I looked further into my cups-browsed.conf and I think > I found the culprit: I had "BrowseOrder Allow,Deny" in there. > I removed it and now the printer appears. I can now reproduce the behaviour you described. There's a lesson for me here: if necessary, ask to see the user's cups-browsed.conf. > Not sure how it got there. Maybe it's when I tried to prevent those > "spurious" printers advertized by some local laptops from appearing, and > since I was testing this with `evince` I got the impression that none of > the BrowseDeny/BrowseAllow directives had any effect and left the config > file in this broken state without noticing. > > It's also not clear why the debug log doesn't say that those printers are > simply "denied by default" and why it gives this odd "could not > determine IP address" instead. > > But at least, on my side you can consider this bug closed as a "pilot > error" (tho I'll be happy to provide more info if you want to dig > further). Closing the report. > Thank you very much for your help, Without your willingness to probe your system and do at least half the work we would not have got there. Cheers, Brian.
--- End Message ---
