Description of problem: Plugging in my printer (a Samsung CLP-500) does not cause a print queue to be generated. This is because the created device node has group 'wheel', not 'lp'. Version-Release number of selected component (if applicable): system-config-printer-udev-1.3.12-7.fc18.x86_64 systemd-197-1.fc18.2.x86_64 cups-1.5.4-20.fc18.x86_64 How reproducible: Always Steps to Reproduce: 1. Plug in printer. 2. 3. Actual results: The device node for the printer has group set to 'wheel' Expected results: The device node for the printer has group set to 'lp' and the printer is set up in CUPS. Additional info: [axa@enyo rules.d]$ lsusb ... Bus 003 Device 008: ID 04e8:3248 Samsung Electronics Co., Ltd Color Laser Printer ... [axa@enyo 003]$ ls -al total 0 drwxr-xr-x. 2 root root 80 Mar 15 21:55 . drwxr-xr-x. 6 root root 120 Mar 12 22:08 .. crw-rw-r--. 1 root root 189, 256 Mar 12 22:08 001 crw-rw----. 1 root wheel 189, 263 Mar 15 21:55 008 Using chgrp on the device node allows CUPS to detect the printer when subsequently poked. Printing worked a couple of weeks ago on this then-up-to-date F18 system, and out-of-the-box when I first installed F18.
Seems like /usr/lib/udev/rules.d/70-printers.rules has to be updated.
I haven't been able to reproduce this here. Please follow this procedure: 1. Disconnect the printer. 2. Run 'udevadm monitor --property | tee events.txt' 3. Connect the printer. 4. Wait for the output to finish, then press Control+C Finally, attach events.txt here. Thanks...
Created attachment 718238 [details] Output from running udevadm monitor --property Hi Tim, thanks for the debugging steps. Here's the output you asked for.
Oh, is it this issue maybe? http://cgit.freedesktop.org/systemd/systemd/commit/?id=bbb7f2ae5035105575365750592caa87213d7072
Yes, that looks like the culprit.
systemd-201-2.fc18.1 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/systemd-201-2.fc18.1
Package systemd-201-2.fc18.2: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.2' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.2 then log in and leave karma (feedback).
Package systemd-201-2.fc18.4: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.4' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.3 then log in and leave karma (feedback).
Package systemd-201-2.fc18.5: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.5 then log in and leave karma (feedback).
systemd-201-2.fc18.6 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6
Package systemd-201-2.fc18.6: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6 then log in and leave karma (feedback).
Unfortunately, it doesn't look like we've pinpointed the issue as it's not resolved when using systemd-201-2.fc18.6.
This continues to be an issue for me in F19. Steps to workaround, in case anyone else is experiencing the same issue: sudo chgrp lp /dev/bus/usb/<bus>/<device> sudo systemctl start c<tab> Which, last time for me, expanded to: sudo chgrp lp /dev/bus/usb/003/002 sudo systemctl start configure-printer But the bus and device numbers will obviously change depending on how your machine is set up. I'm liking these dynamically-generated units :).
It seems to work fine here with a parallel port adapter and a printer: $ ls -l /dev/bus/usb/003/014 crw-rw-r-- 1 root lp 189, 269 20. Jun 14:09 /dev/bus/usb/003/014