Your message dated Sat, 15 Oct 2016 20:35:21 +0100
with message-id <20161015193521.ga6...@copernicus.org.uk>
and subject line Re: Bug#840327: stopped working, no helpful feedback
has caused the Debian Bug report #840327,
regarding stopped working, no helpful feedback
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 ow...@bugs.debian.org
immediately.)
--
840327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cups
Version: 1.7.5-11+deb8u1
Printing had been working fine for a long time but about 20 minutes ago
I tried to print something and an error popup appeared in GNOME asking
if I wanted to diagnose the printer. My document appeared paused in the
queue.
I looked at /var/log/cups/*log and found nothing about the error
I went to the control panel and also the CUPS web interface on port 631
and tried re-enabling the printer and each time I did that it failed again.
I looked at /var/log/daemon.log and observed:
hpcups[16590]: prnt/hpcups/HPCupsFilter.cpp 707: First raster data plane..
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 1...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 2...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 3...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 4...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 5...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 6...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 7...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 8...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 9...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 10...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 11...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 12...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 13...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 14...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 15...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 16...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 17...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 18...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 19...
hp[16592]: io/hpmud/jd.c 820: mdns lookup ABC123DEF.local retry 20...
hp[16592]: io/hpmud/jd.c 816: error timeout mdns lookup ABC123DEF.local
hp[16592]: io/hpmud/jd.c 93: unable to read device-id
hp[16592]: prnt/backend/hp.c 808: ERROR: open device failed stat=12:
hp:/net/HP_LaserJet_3055?zc=ABC123DEF
I killed the cups process and modified /etc/cups/printers.conf to change
the URI from:
DeviceURI hp:/net/HP_LaserJet_3055?zc=ABC123DEF
to something like:
DeviceURI hp:/net/HP_LaserJet_3055?ip=192.168.1.234
and started cups again and now printing works again.
What is really wrong here?
Why did the popup not tell me the root cause of the problem? Why did I
have to go hunting around in the log files like this? How many
non-developers would be comfortable troubleshooting a problem like that
without more details?
--- End Message ---
--- Begin Message ---
On Thu 13 Oct 2016 at 19:13:59 +0100, Brian Potkin wrote:
> On Tue 11 Oct 2016 at 12:19:30 +0200, Daniel Pocock wrote:
>
> > >> On 10/10/16 21:22, Brian Potkin wrote:
> > >
> > > My view would be that with printing problems users have to be prepared
> > > to dig into log files, particularly the error_log. Without it a user
> > > will get nowhere -fast.
> > >
> > > [...Snip...]
> >
> > In that case, we really need to anticipate having a GUI for browsing
> > SysLog in the default desktop. Text based log files are not great for
> > the average user and even for power users, the text-based log files
> > don't distinguish errors from warnings or info messages.
>
> As promised:
>
> https://wiki.debian.org/Dissecting%20and%20Debugging%20the%20CUPS%20Printing%20System#Problems_with_mdns.2FDNS-SD
>
> It will eventually be linked to from a forthcoming hplip page/section
> and perhaps from elsewhere.
>
> IMO, there is no bug of any description in cups or hplip; that does not
> mean the error messages in logs are clearly understandable or cover all
> possible causes of failure. An all-encompassing GUI to browse text logs
> and make them understandable on all levels to all users is well beyond
> the resources and remit of the printing framework; a Debian-wide effort
> would be necessary. Perhaps opening a discussion on -devel would lead to
> a consensus?
I am taking it upon myself to close this report on the following
grounds:
1. The reporter had a firewall misconfiguation.
2. The reporter's solution was sensible but did not address the basic
problem. (HPLIP should work with zc= or ip=).
3. Having addressed the basic problem the issue was resolved,
4. There was nothing in the problem or its solution which involved the
CUPS printing system.
5. The issue that text based log files are not great for the average user
and even for power users is fundamentally outside the scope of the
printing team and should be dealt with elsewhere.
Regards,
Brian.
--- End Message ---
