Am Dienstag, 2. Juni 2015, 06:47:34 schrieb Martin Pitt: > Control: tag -1 moreinfo > > Hey Martin, > > > merkaba:~> systemctl status configure-printer@usb-001-010.service > > ● configure-printer@usb-001-010.service - Configure Plugged-In Printer > > > > Loaded: loaded (/lib/systemd/system/configure-printer@.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@usb-001-010.service: Main process exited, > > code=exited, status=1/FAILURE Jun 01 14:03:34 merkaba systemd[1]: > > configure-printer@usb-001-010.service: Unit entered failed state. Jun > > 01 14:03:34 merkaba systemd[1]: configure-printer@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?
Right now I want to take my time for things that are more important for me. It works with the package I mentioned removed anyway, so feel free to close. If I ever choose to install that printer autoconfigure package again and if it happens again then, I will reopen. Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
