Your message dated Sat, 16 May 2020 21:13:09 +0200 with message-id <[email protected]> and subject line Re: [Pkg-gtkpod-devel] Bug#941703: Bug#941703: libimobiledevice6: Crashes upower with stack smashing when connecting an iPhone has caused the Debian Bug report #941703, regarding libimobiledevice6: Crashes upower with stack smashing when connecting an iPhone to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 941703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941703 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libimobiledevice6 Version: 1.2.1~git20181030.92c5462-1 Severity: important Whenever you connect an iPhone when upower is running, a crash in upower is triggered, apparently because libimobiledevice is doing something leading to a stack smash crash. The same happens if you already have the iPhone connected when upower starts. I'm attaching a trace and log of the first case (connecting the iPhone when upower is already running). Note that this crash triggers upower to endlessly reload because of the crash-restart-crash cycle it gets into. TI:18:18:15 on_battery = no TI:18:18:15 SYSFS add /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2 TI:18:18:15 no changes TI:18:18:15 failed to refresh /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2 TI:18:18:15 object path = /org/freedesktop/UPower/devices/phone_1_2x2 TI:18:18:15 added /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2 TI:18:18:15 emitting added: /org/freedesktop/UPower/devices/phone_1_2x2 TI:18:18:15 SYSFS add /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.0 TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.0 [New Thread 0x7ffff532e700 (LWP 5588)] TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.0 [Thread 0x7ffff532e700 (LWP 5588) exited] TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.0 TI:18:18:15 unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2 TI:18:18:15 SYSFS remove /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.0 TI:18:18:15 ignoring remove event on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:1.0 TI:18:18:15 SYSFS add /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.0 TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.0 [New Thread 0x7ffff532e700 (LWP 5594)] TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.0 [Thread 0x7ffff532e700 (LWP 5594) exited] TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.0 TI:18:18:15 SYSFS add /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.2 TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.2 [New Thread 0x7ffff532e700 (LWP 5596)] TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.2 [Thread 0x7ffff532e700 (LWP 5596) exited] TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.2 TI:18:18:15 SYSFS add /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.1 TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.1 [New Thread 0x7ffff532e700 (LWP 5598)] TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.1 [Thread 0x7ffff532e700 (LWP 5598) exited] TI:18:18:15 failed to coldplug /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.1 TI:18:18:15 unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.1 TI:18:18:15 unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.2 TI:18:18:15 unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.2/1-2.2:4.0 TI:18:18:16 Unknown state on supply /org/freedesktop/UPower/devices/battery_BAT0; forcing update after 1 seconds TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 using min design voltage TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 Setup poll for 'BAT0' every 120 seconds TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 Setup poll for 'BAT0' every 120 seconds TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 Setup poll for 'BAT0' every 120 seconds TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no TI:18:18:16 on_battery = no [Thread 0x7ffff5b2f700 (LWP 5543) exited] *** stack smashing detected ***: <unknown> terminated Thread 1 "upowerd" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007ffff7a1c081 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007ffff7a07535 in __GI_abort () at abort.c:79 #2 0x00007ffff7a5ddb8 in __libc_message (action=<optimized out>, fmt=fmt@entry=0x7ffff7b688a2 "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:181 #3 0x00007ffff7aec81d in __GI___fortify_fail_abort (need_backtrace=need_backtrace@entry=false, msg=msg@entry=0x7ffff7b68880 "stack smashing detected") at fortify_fail.c:28 #4 0x00007ffff7aec7d2 in __stack_chk_fail () at stack_chk_fail.c:29 #5 0x00007ffff7bdc4b7 in idevice_new (device=0x7fffffffe1c0, udid=<optimized out>) at idevice.c:262 #6 0x0000000000000000 in () -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libimobiledevice6 depends on: ii libc6 2.29-2 ii libgcrypt20 1.8.5-2 ii libgnutls30 3.6.9-5 ii libplist3 2.0.1~git20190104.3f96731-1 ii libtasn1-6 4.14-3 ii libusbmuxd4 1.1.0~git20190924.b097ea3-2 Versions of packages libimobiledevice6 recommends: ii usbmuxd 1.1.1~git20181007.f838cf6-1+b1 Versions of packages libimobiledevice6 suggests: pn libusbmuxd-tools <none> -- no debconf information
--- End Message ---
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Version: 1.2.1~git20190921.a9e69b1-1 On Tue, 2019-10-15 at 16:08 +0200, Yves-Alexis Perez wrote: > On Mon, 2019-10-14 at 18:35 -0500, Diego Escalante Urrelo wrote: > > Anyway, thanks for your work on this. Let me know if I can help with > > anything else. > > I'm still waiting for the binNMU or the package from NEW to be accepted, > unfortunately. It seems that I forgot to close this one. - -- Yves-Alexis -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl7AO0YACgkQ3rYcyPpX RFvvMggAiZMSy2aHPiHWFWJql4H9rurhyiz4PHpf+76C6qs+PtM+45Duk7E8t5VX h7YdVc8ZQqYWsb+w+fAORi4VL7/HUaSnFfk3aq65/PDA5Uw4mmiCNLHK5nDSSf+1 V3rCH+ZkNHk6mZjb2DujPspkgu1lu8CF6xkvzw/c+02N4UWu3BTJKyVIG67QwJTZ XkRAcTTs+nXXxWeIRKNvTSDmsJC6uNDe/klAYgmNoBnCPHobDmnffMDRWA8OAJ5A DO/5vIroyyvmsgOoZao/lw1JxGbtO76ip+0NFAO7oRfG1Pabq3dWQC7js1B1AAHo fYI1I//62sfq5Ya1MgNZqCR0YX8vog== =G5Eg -----END PGP SIGNATURE-----
--- End Message ---
