Incorrect permissions for printer devices

Bug #16306 reported by samefab
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Fix Released
Critical
Jeff Bailey

Bug Description

after breezy dist-upgrade my printer "SAMSUNG ML-1710P" is no more recognized by
ubuntu.
I'm getting the following message "printer-stopped" when I'm trying to print any
doc.
No way to put in order the printer.

Revision history for this message
samefab (fabien-delhaye) wrote :

seems to be a permission problem : printer work after "chmod 777 /dev/usb/lp0"

Revision history for this message
Matt Zimmerman (mdz) wrote :

Confirmed here, and by others as well on IRC.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Analysis so far:

The new version of udev no longer seems to set permissions based on the device
path (/etc/udev/permissions.d/udev.permissions seems to be ignored now), and
rather sets them based on the attributes of the hotplug event
(/etc/udev/udev.permissions.rules). The old rule was:

usb/lp[0-9]*:root:lp:0660

but now it uses:

SUBSYSTEM="printer", GROUP="lp"

However, when I connect my printer, the events that are generated all have
SUBSYSTEM=usb; there is no SUBSYSTEM=printer event.

udevsend.env.7591:SUBSYSTEM=usb
udevsend.env.7591:DEVPATH=/devices/pci0000:00/0000:00:07.2/usb1/1-2/1-2.1/1-2.1.3/1-2.1.3.4/1-2.1.3.4.3
udevsend.env.7594:SUBSYSTEM=usb
udevsend.env.7594:DEVPATH=/devices/pci0000:00/0000:00:07.2/usb1/1-2/1-2.1/1-2.1.3/1-2.1.3.4/1-2.1.3.4.3/1-2.1.3.4.3:1.0
udevsend.env.7596:SUBSYSTEM=usb
udevsend.env.7596:DEVPATH=/devices/pci0000:00/0000:00:07.2/usb1/1-2/1-2.1/1-2.1.3/1-2.1.3.4/1-2.1.3.4.3/1-2.1.3.4.3:1.1
udevsend.env.7600:SUBSYSTEM=usb
udevsend.env.7600:DEVPATH=/class/usb/lp0
udevsend.env.7602:SUBSYSTEM=usb
udevsend.env.7602:DEVPATH=/devices/pci0000:00/0000:00:07.2/usb1/1-2/1-2.1/1-2.1.3/1-2.1.3.4/1-2.1.3.4.3/1-2.1.3.4.3:1.2

It seems that only parallel printers get SUBSYSTEM=printer.

Revision history for this message
Matt Zimmerman (mdz) wrote :

*** Bug 16339 has been marked as a duplicate of this bug. ***

Revision history for this message
Jeff Bailey (jbailey) wrote :

Fixed in 0.056-2ubuntu2, please reopen the bug if you have any further troubles!

Tks,
Jeff Bailey

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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