FS#65201 - configure-printer@usb-005-002.service loaded failed failed Configure Plugged-In Printer
Attached to Project:
Arch Linux
Opened by Richard PALO (risto3) - Sunday, 19 January 2020, 08:08 GMT
Last edited by freswa (frederik) - Thursday, 20 February 2020, 21:57 GMT
Opened by Richard PALO (risto3) - Sunday, 19 January 2020, 08:08 GMT
Last edited by freswa (frederik) - Thursday, 20 February 2020, 21:57 GMT
|
Details
Description:
Having some issues with a dymo usb labelwriter 450, apparently since 21 december 2019 $ systemctl status configure-printer@usb-005-002.service ● configure-printer@usb-005-002.service - Configure Plugged-In Printer Loaded: loaded (/usr/lib/systemd/system/configure-printer@.service; static; vendor preset: disabled) Active: failed (Result: core-dump) since Sun 2020-01-19 07:27:22 CET; 1h 28min ago Main PID: 1323 (code=dumped, signal=ABRT) janv. 19 07:26:24 sarchx64 udev-configure-printer[1323]: device devpath is /devices/pci0000:00/0000:00:13.0/usb5/5-1 janv. 19 07:26:24 sarchx64 udev-configure-printer[1323]: MFG:DYMO MDL:LabelWriter 450 SERN:01010112345600 serial:14081918362494 janv. 19 07:27:19 sarchx64 udev-configure-printer[1323]: SERN fields match janv. 19 07:27:19 sarchx64 udev-configure-printer[1323]: URI match: usb://DYMO/LabelWriter%20450?serial=01010112345600 janv. 19 07:27:19 sarchx64 udev-configure-printer[1323]: URI of detected printer: usb://DYMO/LabelWriter%20450?serial=01010112345600, normalized: dymo labelwriter 450 serial 01010112345600 janv. 19 07:27:19 sarchx64 udev-configure-printer[1323]: URI of print queue: usb://DYMO/LabelWriter%20450?serial=01010112345600, normalized: dymo labelwriter 450 serial 01010112345600 janv. 19 07:27:19 sarchx64 udev-configure-printer[1323]: free(): invalid pointer janv. 19 07:27:19 sarchx64 udev-configure-printer[1323]: Queue ipp://localhost/printers/DYMO_LabelWriter_450 has matching device URI janv. 19 07:27:22 sarchx64 systemd[1]: configure-printer@usb-005-002.service: Main process exited, code=dumped, status=6/ABRT janv. 19 07:27:22 sarchx64 systemd[1]: configure-printer@usb-005-002.service: Failed with result 'core-dump'. $ coredumpctl info PID: 1323 (udev-configure-) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Sun 2020-01-19 07:27:19 CET (1h 29min ago) Command Line: /usr/lib/udev/udev-configure-printer add usb-005-002 Executable: /usr/lib/udev/udev-configure-printer Control Group: /system.slice/system-configure\x2dprinter.slice/configure-printer@usb-005-002.service Unit: configure-printer@usb-005-002.service Slice: system-configure\x2dprinter.slice Boot ID: 40ec11eb7b2c4f0bac93157fe8277bef Machine ID: 4ebaa767a0b041dc8b1012591595f293 Hostname: sarchx64 Storage: /var/lib/systemd/coredump/core.udev-configure-.0.40ec11eb7b2c4f0bac93157fe8277bef.1323.1579415239000000000000.lz4 (inaccessible) Message: Process 1323 (udev-configure-) of user 0 dumped core. Stack trace of thread 1323: #0 0x00007f3193bcbf25 raise (libc.so.6 + 0x3bf25) #1 0x00007f3193bb5897 abort (libc.so.6 + 0x25897) #2 0x00007f3193c0f258 __libc_message (libc.so.6 + 0x7f258) #3 0x00007f3193c1677a malloc_printerr (libc.so.6 + 0x8677a) #4 0x00007f3193c1814c _int_free (libc.so.6 + 0x8814c) #5 0x000055c08c940ccd n/a (udev-configure-printer + 0x3ccd) #6 0x000055c08c941a58 n/a (udev-configure-printer + 0x4a58) #7 0x000055c08c93f10a n/a (udev-configure-printer + 0x210a) #8 0x00007f3193bb7153 __libc_start_main (libc.so.6 + 0x27153) #9 0x000055c08c93f3ee n/a (udev-configure-printer + 0x23ee) What is even more strange, if I unplug the printer, the plug it in again, I now have $ systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION ● configure-printer@usb-005-002.service loaded failed failed Configure Plugged-In Printer ● configure-printer@usb-005-005.service loaded failed failed Configure Plugged-In Printer LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 2 loaded units listed. Here's a dmesg snippet: [ 5652.862263] usblp1: removed [ 5663.440990] usblp 5-1:1.0: usblp1: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x0922 pid 0x0020 [ 5676.888867] usblp1: removed [ 5676.895897] usblp 5-1:1.0: usblp1: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x0922 pid 0x0020 [ 5693.199523] usb 5-1: USB disconnect, device number 2 [ 5693.199770] usblp1: removed [ 5693.614109] usb 5-1: new full-speed USB device number 4 using ohci-pci [ 5706.875167] usb 5-1: new full-speed USB device number 5 using ohci-pci [ 5707.066964] usb 5-1: New USB device found, idVendor=0922, idProduct=0020, bcdDevice= 1.12 [ 5707.066969] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 5707.066974] usb 5-1: Product: DYMO LabelWriter 450 [ 5707.066977] usb 5-1: Manufacturer: DYMO [ 5707.066980] usb 5-1: SerialNumber: 14081918362494 [ 5707.073057] usblp 5-1:1.0: usblp1: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x0922 pid 0x0020 [ 5707.113854] audit: type=1130 audit(1579420847.609:198): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=configure-printer@usb-005-005 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5707.237792] audit: type=1131 audit(1579420847.733:199): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=configure-printer@usb-005-005 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' How to get things back in order? Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any $ uname -a Linux sarchx64 5.4.12-arch1-1 #1 SMP PREEMPT Tue, 14 Jan 2020 21:44:31 +0000 x86_64 GNU/Linux $ paclog-pkglist |grep -i cups cups 2.3.1-1 cups-filters 1.26.2-1 cups-pdf 3.0.1-4 dymo-cups-drivers 1.4.0.5-4 lib32-libcups 2.3.1-1 libcups 2.3.1-1 python-pycups 1.9.74-3 Steps to reproduce: (upon every reboot) |
This task depends upon
Closed by freswa (frederik)
Thursday, 20 February 2020, 21:57 GMT
Reason for closing: Upstream
Additional comments about closing: Please consult upstream and fill the re-open form if necessary. Thanks :)
Thursday, 20 February 2020, 21:57 GMT
Reason for closing: Upstream
Additional comments about closing: Please consult upstream and fill the re-open form if necessary. Thanks :)
What package is this? I guess some custom or AUR driver pkg?
I use the defaults for both...
Notice the following in man coredump.conf (note that the default is 'external'):
Storage=
Controls where to store cores. One of "none", "external", and "journal". When "none", the core dumps may be logged (including the backtrace if possible), but not stored permanently. When "external" (the
default), cores will be stored in /var/lib/systemd/coredump/. When "journal", cores will be stored in the journal and rotated following normal journal rotation patterns.
When cores are stored in the journal, they might be compressed following journal compression settings, see journald.conf(5). When cores are stored externally, they will be compressed by default, see below.
[root@sarchx64 systemd]# ls -la /var/lib/systemd/coredump/
total 1460
drwxr-xr-x 2 root root 16384 19 janv. 09:43 .
drwxr-xr-x 9 root root 4096 10 sept. 19:21 ..
-rw-r----- 1 root root 364243 19 janv. 07:27 core.udev-configure-.0.40ec11eb7b2c4f0bac93157fe8277bef.1323.1579415239000000000000.lz4
-rw-r----- 1 root root 364336 17 janv. 19:53 core.udev-configure-.0.41e221a6b5b44f0cb9ef548ca990930c.1158.1579287227000000000000.lz4
-rw-r----- 1 root root 363893 18 janv. 06:46 core.udev-configure-.0.5f20a529c9ef4f4abbe7a9fc75c7bfd3.1136.1579326371000000000000.lz4
-rw-r----- 1 root root 363903 19 janv. 09:43 core.udev-configure-.0.da629ec277ce4d97a04455598c2d9eb0.17717.1579423416000000000000.lz4
I believe the 'inaccessible' message is simply that I used 'sudo coredumpctl info' instead of 'sudo coredumpctl info'
Here is the result using that:
$ sudo coredumpctl info
PID: 17717 (udev-configure-)
UID: 0 (root)
GID: 0 (root)
Signal: 6 (ABRT)
Timestamp: Sun 2020-01-19 09:43:36 CET (2h 8min ago)
Command Line: /usr/lib/udev/udev-configure-printer add usb-005-003
Executable: /usr/lib/udev/udev-configure-printer
Control Group: /system.slice/system-configure\x2dprinter.slice/configure-printer@usb-005-003.service
Unit: configure-printer@usb-005-003.service
Slice: system-configure\x2dprinter.slice
Boot ID: da629ec277ce4d97a04455598c2d9eb0
Machine ID: 4ebaa767a0b041dc8b1012591595f293
Hostname: sarchx64
Storage: /var/lib/systemd/coredump/core.udev-configure-.0.da629ec277ce4d97a04455598c2d9eb0.17717.1579423416000000000000.lz4
Message: Process 17717 (udev-configure-) of user 0 dumped core.
Stack trace of thread 17717:
#0 0x00007f2e0017bf25 raise (libc.so.6 + 0x3bf25)
#1 0x00007f2e00165897 abort (libc.so.6 + 0x25897)
#2 0x00007f2e001bf258 __libc_message (libc.so.6 + 0x7f258)
#3 0x00007f2e001c677a malloc_printerr (libc.so.6 + 0x8677a)
#4 0x00007f2e001c814c _int_free (libc.so.6 + 0x8814c)
#5 0x0000557fb4881ccd n/a (udev-configure-printer + 0x3ccd)
#6 0x0000557fb4882a58 n/a (udev-configure-printer + 0x4a58)
#7 0x0000557fb488010a n/a (udev-configure-printer + 0x210a)
#8 0x00007f2e00167153 __libc_start_main (libc.so.6 + 0x27153)
#9 0x0000557fb48803ee n/a (udev-configure-printer + 0x23ee)
I still don't know what "configure-printer@usb-005-002.service" comes from. A typical cups setup doesn't have such service file.
Maybe it's part of dymo-cups-drivers 1.4.0.5-4 from AUR?
But I do find this:
$ sudo find /etc /usr/lib -name 'configure-printer*'
/usr/lib/systemd/system/configure-printer@.service
$ pacman -Qo /usr/lib/systemd/system/configure-printer@.service
/usr/lib/systemd/system/configure-printer@.service appartient à system-config-printer 1.5.12-2
$ cat /usr/lib/systemd/system/configure-printer@.service
[Unit]
Description=Configure Plugged-In Printer
Requires=org.cups.cupsd.socket
After=org.cups.cupsd.socket
[Service]
ExecStart=/usr/lib/udev/udev-configure-printer add "%i"
use system-config-printer on any of my system.
Can you please do a custom build of system-config-printer and apply these two patches to confirm fixing your issue?
https://github.com/OpenPrinting/system-config-printer/commit/cf9903466c1a2d18a701f3b5e8c7e03483e1244d
and https://github.com/OpenPrinting/system-config-printer/commit/b9289dfe105bdb502f183f0afe7a115ecae5f2af
I get similar errors as above, unfortunately.
$ systemctl status configure-printer@usb-005-004.service
● configure-printer@usb-005-004.service - Configure Plugged-In Printer
Loaded: loaded (/usr/lib/systemd/system/configure-printer@.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2020-01-25 16:53:48 CET; 5min ago
Process: 13722 ExecStart=/usr/lib/udev/udev-configure-printer add usb-005-004 (code=exited, status=1/FAILURE)
Main PID: 13722 (code=exited, status=1/FAILURE)
janv. 25 16:53:48 sarchx64 systemd[1]: Started Configure Plugged-In Printer.
janv. 25 16:53:48 sarchx64 udev-configure-printer[13722]: add usb-005-004
janv. 25 16:53:48 sarchx64 udev-configure-printer[13722]: device devpath is /devices/pci0000:00/0000:00:13.0/usb5/>
janv. 25 16:53:48 sarchx64 udev-configure-printer[13722]: Device already handled
janv. 25 16:53:48 sarchx64 systemd[1]: configure-printer@usb-005-004.service: Main process exited, code=exited, st>
janv. 25 16:53:48 sarchx64 systemd[1]: configure-printer@usb-005-004.service: Failed with result 'exit-code'.
dmesg snippet:
[ 773.699693] usb 5-1: USB disconnect, device number 2
[ 773.699896] usblp1: removed
[ 787.850515] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 788.227185] usb 5-1: new full-speed USB device number 4 using ohci-pci
[ 788.418855] usb 5-1: New USB device found, idVendor=0922, idProduct=0020, bcdDevice= 1.12
[ 788.418862] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 788.418865] usb 5-1: Product: DYMO LabelWriter 450
[ 788.418868] usb 5-1: Manufacturer: DYMO
[ 788.418871] usb 5-1: SerialNumber: 14081918362494
[ 788.424965] usblp 5-1:1.0: usblp1: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x0922 pid 0x0020
Perhaps replugging is an unhandled case.