Bug#787414: systemd: printing broken: udev-configure-printer: no device named /dev/bus/usb/001/010 found while it is there
Martin Pitt
mpitt at debian.org
Tue Jun 2 05:47:34 BST 2015
Control: tag -1 moreinfo
Hey Martin,
> merkaba:~> systemctl status configure-printer at usb-001-010.service
> ● configure-printer at usb-001-010.service - Configure Plugged-In Printer
> Loaded: loaded (/lib/systemd/system/configure-printer at .service; static; vendor preset: enabled)
> Active: failed (Result: exit-code) since Mo 2015-06-01 14:03:34 CEST; 7min ago
> Process: 8674 ExecStart=/lib/udev/udev-configure-printer add %i (code=exited, status=1/FAILURE)
> Main PID: 8674 (code=exited, status=1/FAILURE)
>
> Jun 01 14:03:33 merkaba systemd[1]: Started Configure Plugged-In Printer.
> Jun 01 14:03:33 merkaba systemd[1]: Starting Configure Plugged-In Printer...
> Jun 01 14:03:33 merkaba udev-configure-printer[8674]: add usb-001-010
> Jun 01 14:03:34 merkaba udev-configure-printer[8674]: no device named /dev/bus/usb/001/010 found
> Jun 01 14:03:34 merkaba systemd[1]: configure-printer at usb-001-010.service: Main process exited, code=exited, status=1/FAILURE
> Jun 01 14:03:34 merkaba systemd[1]: configure-printer at usb-001-010.service: Unit entered failed state.
> Jun 01 14:03:34 merkaba systemd[1]: configure-printer at usb-001-010.service: Failed with result 'exit-code'.
Without looking into this too much yet, this very much looks like
another victim of udev callouts not getting a proper environment
(#787263). This should be fixed in 220-3, can you verify?
Thanks,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
More information about the Pkg-systemd-maintainers
mailing list