Bug 922279
| Summary: | CUPS fails to configure printer due to wrong group ownership of device node | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew Aylett <andrew> | ||||
| Component: | systemd | Assignee: | systemd-maint | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 19 | CC: | harald, johannbg, jonathan, jpopelka, kay, lnykryn, metherid, mschmidt, msekleta, plautrba, rvokal, systemd-maint, twaugh, udev-maint, vpavlin, zbyszek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-06-20 12:12:30 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Andrew Aylett
2013-03-15 23:03:27 UTC
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 |