This problem was introduced by the 198 bump, and 197 is OK: <heftig> kay: systemd commit 22582bb broke cups usb printing for me <heftig> because the "lp" group isn't applied anymore <heftig> SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", GROUP="lp" <heftig> moving this line to the end of 50-udev-default.rules restores correct behavior, as it's after usb_id <zbyszek> heftig: please post a patch <heftig> i guess one could move all the stuff after the default_permissions section to before that section This results in these: http://bugs.gentoo.org/show_bug.cgi?id=461456 http://www.chakra-project.org/bbs/viewtopic.php?id=9883&p=2 http://forums.gentoo.org/viewtopic-t-953970-start-0-postdays-0-postorder-asc-highlight-.html Proposed fix is: heftig> that said, try editing 50-udev-default.rules and move the stuff after LABEL="default_permissions_end" to the beginning of the file
This commit is the culprit: http://cgit.freedesktop.org/systemd/systemd/commit/rules/50-udev-default.rules?id=22582bb2cbe85b40de5f561589e0468dac769515
Created attachment 342660 [details, diff] Possible fix (thanks to heftig) Possible fix, untested
Created attachment 342662 [details, diff] Correct patch. Still untested.
Works for me printing a test page I restarted udev and cupsd after patching Thanks for tracking it down Samuli
After editing the file I simple switched my printer off and on. Now I could readd the printer in cups. It is printing again.
Committed to Portage now because upstream got it now too: http://cgit.freedesktop.org/systemd/systemd/commit/?id=bbb7f2ae5035105575365750592caa87213d7072 +*udev-198-r2 (20 Mar 2013) + + 20 Mar 2013; Samuli Suominen <ssuominen@gentoo.org> +udev-198-r2.ebuild: + Move builtins section before permissions section in + /lib/udev/rules.d/50-udev-default.rules to fix eg. USB printing wrt #462346 The patch in portage is slightly adjusted, since in git the firmware line is in it's own file, which isn't the case yet for 198
*** Bug 461456 has been marked as a duplicate of this bug. ***
*** Bug 462988 has been marked as a duplicate of this bug. ***
