Public bug reported:
Binary package hint: system-config-printer
When you try to set up a printer, it seems that a lot of debugging
information is spewed on standard error, and (for most users) lands in
your .xsession-errors.
If this is useful information, it should be put where people will find
it. I'm a pathological case because I run tail -f on my .xsession-
errors, but for most users, this information might as well not be there.
And for those times when it does matter, there is a pesky "feature" in
gdm which stops logging to .xsession-errors when it decides the file is
about to get too big. (That's bug #15027.)
Here's a transcript of me setting up a Samba printer and looking around
a bit.
(gnome-panel:5563): GWeather-WARNING **: Failed to get METAR data.
fetchDevices
Lock acquired for devices thread
Devices thread started
Connecting (devices)
Fetching devices
Closing connection (devices)
Releasing devices lock
Got devices
queryPPDs
Lock acquired for PPDs thread
PPDs thread started
Connecting (PPDs)
Fetching PPDs
Closing connection (PPDs)
Releasing PPDs lock
fetchPPDs
queryPPDs
Lock acquired for PPDs thread
PPDs thread started
Connecting (PPDs)
Fetching PPDs
Closing connection (PPDs)
Releasing PPDs lock
Got PPDs
No ID match for device smb://53kr1t5tuphph/server/printer:
<manufacturer>Generic</manufacturer>
<model>Printer</model>
<description>Generic Printer</description>
<commandset></commandset>
Using lsb/usr/cups-included/textonly.ppd
set PageSize = Letter
/usr/bin/gs: found
/usr/bin/hpijs: found
/usr/lib/cups/filter/foomatic-rip: found
612.000000 792.000000
48960 63360
fetchDevices
Lock acquired for devices thread
Devices thread started
Connecting (devices)
Fetching devices
Closing connection (devices)
Releasing devices lock
Got devices
queryPPDs
Lock acquired for PPDs thread
PPDs thread started
Connecting (PPDs)
Fetching PPDs
Closing connection (PPDs)
Releasing PPDs lock
fetchDevices
Lock acquired for devices thread
Devices thread started
Connecting (devices)
Fetching devices
Closing connection (devices)
Releasing devices lock
Got devices
queryPPDs
Lock acquired for PPDs thread
PPDs thread started
Connecting (PPDs)
Fetching PPDs
Closing connection (PPDs)
Releasing PPDs lock
fetchPPDs
queryPPDs
Lock acquired for PPDs thread
PPDs thread started
Connecting (PPDs)
Fetching PPDs
Closing connection (PPDs)
Releasing PPDs lock
Got PPDs
No ID match for device smb://53kr1t5tuphph/server/printer:
<manufacturer>Generic</manufacturer>
<model>Printer</model>
<description>Generic Printer</description>
<commandset></commandset>
Using lsb/usr/cups-included/textonly.ppd
fetchDevices
Lock acquired for devices thread
Devices thread started
Connecting (devices)
Fetching devices
Closing connection (devices)
Releasing devices lock
Got devices
queryPPDs
Lock acquired for PPDs thread
PPDs thread started
Connecting (PPDs)
Fetching PPDs
Closing connection (PPDs)
Releasing PPDs lock
Note the absence of any information about what is causing these lines to
be logged (including "system-config-printer: " in all messages would be
a suitable workaround) but more generally the routine nature of most of
these messages. If somebody wants to debug the program, there should be
a command-line option for enabling these messages, but they should be
disabled by default.
** Affects: system-config-printer (Ubuntu)
Importance: Undecided
Status: New
--
Excessively verbose messages filling up .xsession-errors
https://bugs.launchpad.net/bugs/221747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
