EACCES in usb backend very difficult to diagnose

Bug #76078 reported by Matt Zimmerman
2
Affects Status Importance Assigned to Milestone
cupsys (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: cupsys

(Till, I've discussed this bug with you briefly in the past)

When there is a problem with device permissions in the usb backend (and potentially with other CUPS backends), such as bug 76077, this does not result in any failure or error message. Jobs sit in the print queue in job-printing state and stay there indefinitely. No error is logged in CUPS error_log, syslog or displayed to the user at any time. The backend can be seen running, but not doing much.

This seems needlessly complex to diagnose using strace on the backend. It should simply fail and report an error to the user so that the problem can be fixed.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

This is a missing feature in CUPS. I have reported it upstream now:

http://www.cups.org/str.php?L2181

Changed in cupsys:
importance: Undecided → Wishlist
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

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?

The upstream bug report http://www.cups.org/str.php?L2181 has been marked "Closed w/Resolution" with a comment that "The current code already errors out if it cannot access any of the USB devices."

Thanks in advance.

Changed in cupsys:
assignee: nobody → charlie-tca
status: New → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. I am closing this bug report based on closing of the upstream report with resolution.
Please continue to report bugs you find.

Changed in cupsys:
assignee: charlie-tca → nobody
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.