Ubuntu
cupsys package

cups: printing to lp0 stopped working on Gutsy

Bug #172509 reported by Stephan Bourduas on 2007-11-28

Affects		Status	Importance	Assigned to	Milestone
	cupsys (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: cupsys

Cups got broken sometime in the last few weeks presumably after a cups upgrade (I'm using Gutsy). All of a sudden, I just couldn't print to my HP LaserJet 2100M anymore. All the jobs just get stuck in the queue and never print. I get the following in my /etc/cups/error_log:

D [28/Nov/2007:06:22:29 +0000] cupsdAcceptClient: 21 from localhost (Domain)
D [28/Nov/2007:06:22:29 +0000] cupsdReadClient: 21 POST / HTTP/1.1
D [28/Nov/2007:06:22:29 +0000] cupsdAuthorize: No authentication data provided.
D [28/Nov/2007:06:22:29 +0000] Get-Jobs ipp://localhost:631/printers/hp2100m
D [28/Nov/2007:06:22:29 +0000] cupsdProcessIPPRequest: 21 status_code=0 (successful-ok)
D [28/Nov/2007:06:22:29 +0000] cupsdCloseClient: 21

I've been searching around and can't seem to find a fix for this. I tried deleting and then adding my printer from scratch using the KDE print system interface, and I still get the same behavior.

Revision history for this message

Stephan Bourduas (stephan-bourduas) wrote on 2007-11-28:

printingbuginfo Edit (2.8 KiB, text/plain)

Revision history for this message

Till Kamppeter (till-kamppeter) wrote on 2007-11-28:

Can you do

sudo aa-complain cupsd

and then try to print again? Does it work for you now?

To get back to the original state do

sudo aa-enforce cupsd

Changed in cupsys:
status:	New → Incomplete

Revision history for this message

Stephan Bourduas (stephan-bourduas) wrote on 2007-11-28:

I tried this before filing the bug report as per the Gutsy release note (https://wiki.ubuntu.com/GutsyGibbon/ReleaseNotes). Just to make sure, I tried it again, and the problem persists.

Revision history for this message

Stephan Bourduas (stephan-bourduas) wrote on 2007-12-02:

I found the following error messages related to cups in dmesg; not sure how to fix this:

[81653.887789] audit(1196288086.151:40): type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13274 profile="/usr/sbin/cupsd"
[81653.888832] audit(1196288086.151:41): type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13274 profile="/usr/sbin/cupsd"
[81653.889282] audit(1196288086.151:42): type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13274 profile="/usr/sbin/cupsd"
[81698.510255] audit(1196288130.785:43): type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13285 profile="/usr/sbin/cupsd"
[81698.510340] audit(1196288130.785:44): type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13285 profile="/usr/sbin/cupsd"
[81698.510401] audit(1196288130.785:45): type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13285 profile="/usr/sbin/cupsd"
[81698.532800] ppdev0: registered pardevice
[81702.697686] ppdev0: unregistered pardevice
[81704.141358] ppdev0: registered pardevice
[81712.700786] ppdev0: unregistered pardevice
[81713.895054] audit(1196288146.178:46): type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13301 profile="/usr/sbin/cupsd"
[81713.895854] audit(1196288146.178:47): type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13301 profile="/usr/sbin/cupsd"
[81713.896451] audit(1196288146.178:48): type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13301 profile="/usr/sbin/cupsd"
[273852.833876] lp0 releasing parport

I found the following error messages related to cups in dmesg; not sure how to fix this:

[81653.887789] audit(1196288086.151:40):  type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13274 profile="/usr/sbin/cupsd"
[81653.888832] audit(1196288086.151:41):  type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13274 profile="/usr/sbin/cupsd"
[81653.889282] audit(1196288086.151:42):  type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13274 profile="/usr/sbin/cupsd"
[81698.510255] audit(1196288130.785:43):  type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13285 profile="/usr/sbin/cupsd"
[81698.510340] audit(1196288130.785:44):  type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13285 profile="/usr/sbin/cupsd"
[81698.510401] audit(1196288130.785:45):  type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13285 profile="/usr/sbin/cupsd"
[81698.532800] ppdev0: registered pardevice
[81702.697686] ppdev0: unregistered pardevice
[81704.141358] ppdev0: registered pardevice
[81712.700786] ppdev0: unregistered pardevice
[81713.895054] audit(1196288146.178:46):  type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13301 profile="/usr/sbin/cupsd"
[81713.895854] audit(1196288146.178:47):  type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13301 profile="/usr/sbin/cupsd"
[81713.896451] audit(1196288146.178:48):  type=1502 operation="sysctl" requested_mask="r" denied_mask="r" na
me="/proc/sys/dev/parport/parport0/autoprobe" pid=13301 profile="/usr/sbin/cupsd"
[273852.833876] lp0 releasing parport

Revision history for this message

Andreas Moog (ampelbein) wrote on 2008-08-21: Old standing report

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.

status incomplete
subscribe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkit6d4ACgkQ06FgkPZwicRCwACfYVX9PPEUxS0GoEtA+SOfTZAE
bSAAoMTNxHAc5hJbk565X9zVI+FBWRb7
=AtOe
-----END PGP SIGNATURE-----

Revision history for this message

Andreas Moog (ampelbein) wrote on 2008-09-10:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!