Bug#958104: system-config-printer-udev: ABRT: free(): invalid pointer
Hello there! On Tue, Apr 28, 2020 at 12:35:52AM +0200, Bernhard Übelacker wrote: > Dear Maintainer, > looking at the backtrace from message 13 and at the changes > done by upstream, following commit sounds related: > > https://github.com/OpenPrinting/system-config-printer/commit/b9289dfe105bdb502f183f0afe7a115ecae5f2af#diff-d3f2f90b6e176486d4b8dfe3222577f7 Indeed! I opened a MR at https://salsa.debian.org/gnome-team/system-config-printer/-/merge_requests/1 picking that and the previous, related, commit. After trying, the thing doesn't crash anymore, though it does still fail: Apr 29 18:58:45 warren systemd[1]: Started Configure Plugged-In Printer. Apr 29 18:58:45 warren udev-configure-printer[3076204]: add usb-001-008 Apr 29 18:58:45 warren udev-configure-printer[3076204]: device devpath is /devices/pci:00/:00:14.0/usb1/1-1 Apr 29 18:58:45 warren udev-configure-printer[3076204]: Device already handled Apr 29 18:58:45 warren systemd[1]: configure-printer@usb-001-008.service: Main process exited, code=exited, status=1/FAILURE Apr 29 18:58:45 warren systemd[1]: configure-printer@usb-001-008.service: Failed with result 'exit-code'. I didn't debug further, and I know nothing about udev so maybe it just needs some poking? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#958104: system-config-printer-udev: ABRT: free(): invalid pointer
Dear Maintainer, looking at the backtrace from message 13 and at the changes done by upstream, following commit sounds related: https://github.com/OpenPrinting/system-config-printer/commit/b9289dfe105bdb502f183f0afe7a115ecae5f2af#diff-d3f2f90b6e176486d4b8dfe3222577f7 Kind regards, Bernhard
Bug#958104: system-config-printer-udev: ABRT: free(): invalid pointer
Backtrace attachment with related dbgsym installed. Regards (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7f3de0cb055b in __GI_abort () at abort.c:79 #2 0x7f3de0d09008 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f3de0e15f3e "%s\n") at ../sysdeps/posix/libc_fatal.c:181 #3 0x7f3de0d103aa in malloc_printerr (str=str@entry=0x7f3de0e140e0 "free(): invalid pointer") at malloc.c:5339 #4 0x7f3de0d11d9c in _int_free (av=, p=, have_lock=0) at malloc.c:4173 #5 0x55904b38916f in for_each_matching_queue (flags=1, fn=0x55904b387c00 , usblpdev=0x7fffde6ef5c8 "", usblpdevlen=, device_uris=, device_uris=, context=0x0) at udev/udev-configure-printer.c:1515 #6 0x55904b389f89 in do_add (cmd=0x7fffde6f0efa "/lib/udev/udev-configure-printer", devaddr=) at udev/udev-configure-printer.c:1663 #7 0x55904b387724 in main (argc=3, argv=0x7fffde6f0c38) at udev/udev-configure-printer.c:1871
Bug#958104: system-config-printer-udev: ABRT: free(): invalid pointer
Package: system-config-printer-udev Version: 1.5.12-1 Followup-For: Bug #958104 Dear Maintainer, in my case it's a strange bug, when I physically turn on the printer I see the segv and coredump in the logs, but then the printer works, system log attached. Note that for this printer I had to install proprietary drivers: samsung-uld_V1.00.39_01.17.tar.gz unfortunately it is not clear what they are going to install it is not a package and I have not found a log. Let me know if you need more information I can look at it. Thanks -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages system-config-printer-udev depends on: ii libc62.30-4 ii libcups2 2.3.1-11 ii libglib2.0-0 2.64.2-1 ii libudev1 245.5-1 ii libusb-1.0-0 2:1.0.23-2 ii python3 3.8.2-3 ii python3-cups 1.9.73-3+b1 ii python3-cupshelpers 1.5.12-1 ii python3-dbus 1.2.16-2 system-config-printer-udev recommends no packages. system-config-printer-udev suggests no packages. -- no debconf information Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: URI contains USB serial number Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: URI match: usb://Samsung/M2020%20Series?serial=08HVB8GKCB019MM Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: free(): invalid pointer Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: URI of detected printer: usb://Samsung/M2020%20Series?serial=08HVB8GKCB019MM, normalized: samsung m2020 series serial 08hvb8gkcb019mm Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: URI of print queue: usb://Samsung/M2020%20Series?serial=08HVB8GKCB019MM, normalized: samsung m2020 series serial 08hvb8gkcb019mm Apr 22 15:23:40 hellspawn udev-configure-printer[74160]: Queue ipp://localhost/printers/samsung-m2026 has matching device URI Apr 22 15:23:40 hellspawn systemd[1]: Created slice system-systemd\x2dcoredump.slice. Apr 22 15:23:40 hellspawn systemd[1]: Started Process Core Dump (PID 74191/UID 0). Apr 22 15:23:40 hellspawn systemd[1]: configure-printer@usb-005-002.service: Main process exited, code=dumped, status=6/ABRT Apr 22 15:23:40 hellspawn systemd[1]: configure-printer@usb-005-002.service: Failed with result 'core-dump'. Apr 22 15:23:40 hellspawn systemd-coredump[74193]: Process 74160 (udev-configure-) of user 0 dumped core. Stack trace of thread 74160: #0 0x7f3de0cc6761 __GI_raise (libc.so.6 + 0x3b761) #1 0x7f3de0cb055b __GI_abort (libc.so.6 + 0x2555b) #2 0x7f3de0d09008 __libc_message (libc.so.6 + 0x7e008) #3 0x7f3de0d103aa malloc_printerr (libc.so.6 + 0x853aa) #4 0x7f3de0d11d9c _int_free (libc.so.6 + 0x86d9c) #5 0x55904b38916f n/a (udev-configure-printer + 0x416f) #6 0x55904b389f89 n/a (udev-configure-printer + 0x4f89) #7 0x55904b387724 n/a (udev-configure-printer + 0x2724) #8 0x7f3de0cb1e0b __libc_start_main (libc.so.6 + 0x26e0b) #9 0x55904b3879ea n/a (udev-configure-printer + 0x29ea) Apr 22 15:23:40 hellspawn systemd[1]: systemd-coredump@0-74191-0.service: Succeeded. Apr 22 15:23:56 hellspawn lightdm[74105]: pam_unix(lightdm:auth): Couldn't open /etc/securetty: No such file or directory Apr 22 15:23:56 hellspawn lightdm[74105]: gkr-pam: unable to locate daemon control file Apr 22 15:23:56 hellspawn lightdm[74105]: gkr-pam: stashed password to try later in open session Apr 22 15:23:56 hellspawn lightdm[74105]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files Apr 22 15:23:57 hellspawn systemd[1]: Stopping Session c8 of user lightdm. Apr 22 15:23:57 hellspawn lightdm[74036]: pam_unix(lightdm-greeter:session): session closed for user lightdm Apr 22 15:23:57 hellspawn systemd[1]:
Bug#958104: system-config-printer-udev: ABRT: free(): invalid pointer
Package: system-config-printer-udev Version: 1.5.12-1 Hi, every time I connect my printer, a new failed systemd service appear. It has been this way for at least a year (when I started looking at failed systemd units), and I'm only now reporting it. An example: root@warren ~ # systemctl status configure-printer@usb-001-014.service ● configure-printer@usb-001-014.service - Configure Plugged-In Printer Loaded: loaded (/lib/systemd/system/configure-printer@.service; static; vendor preset: enabled) Active: failed (Result: signal) since Fri 2020-04-17 09:55:34 CEST; 1 day 5h ago Process: 906558 ExecStart=/lib/udev/udev-configure-printer add usb-001-014 (code=killed, signal=ABRT) Main PID: 906558 (code=killed, signal=ABRT) … root@warren ~ # journalctl -u configure-printer@usb-001-014.service -- Logs begin at Wed 2019-03-13 19:07:17 CET, end at Sat 2020-04-18 15:40:54 CEST. -- Apr 17 09:55:27 warren systemd[1]: Started Configure Plugged-In Printer. Apr 17 09:55:27 warren udev-configure-printer[906558]: add usb-001-014 Apr 17 09:55:27 warren udev-configure-printer[906558]: device devpath is /devices/pci:00/:00:14.0/usb1/1-1 Apr 17 09:55:27 warren udev-configure-printer[906558]: MFG:Kyocera MDL:FS-820 SERN:- serial:XEN4Z00438 Apr 17 09:55:34 warren udev-configure-printer[906558]: URI contains USB serial number Apr 17 09:55:34 warren udev-configure-printer[906558]: URI match: usb://Kyocera/FS-820?serial=XEN4Z00438 Apr 17 09:55:34 warren systemd[1]: configure-printer@usb-001-014.service: Main process exited, code=killed, status=6/ABRT Apr 17 09:55:34 warren udev-configure-printer[906558]: free(): invalid pointer Apr 17 09:55:34 warren udev-configure-printer[906558]: URI of detected printer: usb://Kyocera/FS-820?serial=XEN4Z00438, normalized: kyocera fs 820 serial xen4z00438 Apr 17 09:55:34 warren systemd[1]: configure-printer@usb-001-014.service: Failed with result 'signal'. Apr 17 09:55:34 warren udev-configure-printer[906558]: URI of print queue: usb://Kyocera/FS-820?serial=XEN4Z00438, normalized: kyocera fs 820 serial xen4z00438 Apr 17 09:55:34 warren udev-configure-printer[906558]: Queue ipp://localhost/printers/Kyocera_FS-820 has matching device URI I noticed similar reports around, for example this: https://bugs.archlinux.org/task/65201 But I couldn't spot anything conclusive. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
