Bug#929764: usbmuxd segfaults on startup
Bernhard Übelacker wrote: > I guess this issue could be related to following shared library. > > 0x77b6a0e0 0x77b7af47 Yes (*) > > /usr/local/lib/libimobiledevice.so.6 > It looks like this file is a manual installed version, > while the debian version of that library should be loaded > from here: /usr/lib/x86_64-linux-gnu/libimobiledevice.so.6 > Can you check if you really need that local file? > And if it is renamed, does the problems disappear? Bernhard, that's it! I checked: # dpkg -S /usr/local/lib/libimobiledevice.so.6 libimobiledevice: /usr/local/lib/libimobiledevice.so.6 # dpkg -S /usr/lib/x86_64-linux-gnu/libimobiledevice.so.6 libimobiledevice6:amd64: /usr/lib/x86_64-linux-gnu/libimobiledevice.so.6 # But I noticed the libimobiledevice package isn't in sid anymore. I wonder if it's been deprecated. I removed it, and now only have libimobiledevice6 installed. And now: # usbmuxd # No segfault! As a user: $ ifuse /media/iphone/ $ ls /media/iphone/ BooksDCIM iTunes_Control PhotoStreamsData Radio CloudAssets Downloads PhotoData Purchases Recordings $ ideviceinfo ActivationState: Activated ActivationStateAcknowledged: true BasebandActivationTicketVersion: V2 [... etc ...] $ fusermount -u /media/iphone/ $ It turns out this old libimobiledevice package was interfering. Thank you, Bernhard and Yves-Alexis for your help! I'm so glad to be able to mount this phone and get the photos off after so many months... Please close this bug as fixed.
Bug#929764: [Pkg-gtkpod-devel] Bug#929764: usbmuxd segfaults on startup
Hello James Henried, I guess this issue could be related to following shared library. > 0x77b6a0e0 0x77b7af47 Yes (*) > /usr/local/lib/libimobiledevice.so.6 It looks like this file is a manual installed version, while the debian version of that library should be loaded from here: /usr/lib/x86_64-linux-gnu/libimobiledevice.so.6 Can you check if you really need that local file? And if it is renamed, does the problems disappear? Kind regards, Bernhard
Bug#929764: [Pkg-gtkpod-devel] Bug#929764: usbmuxd segfaults on startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2019-05-31 at 10:35 -0400, James Henried wrote: > Please let me know if this is useful/ok or if I need to do anything > else. It looks OpenSSL related, but besides that I don't have much clue yet. It might help to install dbgsym packages for usbmuxd, libssl and libusbmuxd though. See https://wiki.debian.org/SourcesList#Debug_Symbol_Packages for example. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlzxXTQACgkQ3rYcyPpX RFu+wggAp15qEZo4qe43XiNU3dKM3lmGzeSui+1QIgzMRHJJL54LywGPrTsFZpmx AtvUj6bUKLbkGXRgaQ3zBmFzoRt0OWPayTqCcMDrgYRtHYjEz6s5RJ2mChSl/FbE kMdlpL8AZ1QeuYIKAcOX4838yISIkzFUSn+EhISS2m9OrVRlW9UGlFS1rt8TU0k/ aQb6qQNzqQ036tqFGvu4uCNrJAUbU8h4sCRiZvdoY108lJTZc8KoRHl+COlmiByr J+r17HEB5//34NoaXy/ffU/OUbR0dT7JDVJuBWQdmmZbrI33i4TcIalVhRF4nZMi FJ2+cwglEVteBKwpqDPaCrj1M9kFeQ== =1FAP -END PGP SIGNATURE-
Bug#929764: usbmuxd segfaults on startup
Yves-Alexis Perez wrote: > Hi, can you also provide the information asked in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919630#10 ? Yes, I'm happy to: > When does this behavior started? Is it recently or > more ancient? It's not recent. I've used ifuse on this system for years, but have been having trouble for at least 6 months, possibly longer. > I can't reproduce this (it works fine whether I plug an iPhone and let > udev/systemd runs usbmuxd or wether I run usbmuxd manually). What is the iOS > version? This is an iPhone 5 with IOD 10.3.3 (14G60). > Is the iPhone correctly seen by lsusb? Yes: $ lsusb Bus 006 Device 002: ID 8087:8002 Intel Corp. Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 8087:800a Intel Corp. Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ > What does ideviceinfo reports? $ ideviceinfo No device found, is it plugged in? double free or corruption (fasttop) Aborted $ > Can you install the various debugging packages and take a backtrace? Yes. I will do this now and send in response to Bernhard Übelacker's post. Thank you, all, for your continued help.
Bug#929764: usbmuxd segfaults on startup
Bernhard Übelacker wrote: > Maybe you could install the package systemd-coredump. > That way in the journal would appear a backtrace that > could give some hints where the segmentation fault happens. > Visible in the output of: > journalctl --no-pager Here it is: May 31 10:29:05 debian systemd[1]: /lib/systemd/system/usbmuxd.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/usbmuxd.pid → /run/usbmuxd.pid; please update the unit file accordingly. May 31 10:29:05 debian systemd[1]: getty@tty1.service: Current command vanished from the unit file, execution of the command list won't be resumed. May 31 10:29:05 debian systemd[1]: Listening on Process Core Dump Socket. May 31 10:29:19 debian su[28045]: pam_unix(su:session): session closed for user root May 31 10:29:34 debian su[29407]: (to root) jh on pts/0 May 31 10:29:34 debian su[29407]: pam_unix(su:session): session opened for user root by (uid=1000) May 31 10:29:38 debian usbmuxd[29410]: [1] Another instance is already running (pid 26593). exiting. May 31 10:29:38 debian kernel: do_general_protection: 496 callbacks suppressed May 31 10:29:38 debian kernel: traps: usbmuxd[29410] general protection ip:7f9e393d49bd sp:7ffd67ab0b60 error:0 in libc-2.28.so[7f9e39372000+148000] May 31 10:29:38 debian systemd[1]: Created slice system-systemd\x2dcoredump.slice. May 31 10:29:38 debian systemd[1]: Started Process Core Dump (PID 29411/UID 0). May 31 10:29:38 debian systemd-coredump[29412]: Process 29410 (usbmuxd) of user 0 dumped core. Stack trace of thread 29410: #0 0x7f9e393d49bd __GI___libc_free (libc.so.6) #1 0x7f9e391a09f0 OPENSSL_sk_pop_free (libcrypto.so.1.1) #2 0x7f9e392ccc29 n/a (libssl.so.1.1) #3 0x7f9e3913af1a OPENSSL_cleanup (libcrypto.so.1.1) #4 0x7f9e3938a2b7 __cxa_finalize (libc.so.6) #5 0x7f9e3903c093 n/a (libcrypto.so.1.1) #6 0x7f9e399bf6f6 _dl_fini (ld-linux-x86-64.so.2) #7 0x7f9e39389d8c __run_exit_handlers (libc.so.6) #8 0x7f9e39389eba __GI_exit (libc.so.6) #9 0x7f9e393740a2 __libc_start_main (libc.so.6) #10 0x55821d8f0b0a n/a (usbmuxd) > Additional you could install the package gdb and start > usbmuxd with the following command: Done: Script started on 2019-05-31 10:32:30-04:00 [TERM="xterm-256color" TTY="/dev/pts/0" COLUMNS="69" LINES="41"] Reading symbols from usbmuxd...(no debugging symbols found)...done. Starting program: /usr/sbin/usbmuxd [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. __GI___libc_free (mem=0x101040104070701) at malloc.c:3093 3093malloc.c: No such file or directory. rax0x0 0 rbx0x0 0 rcx0x1 1 rdx0x79e 1950 rsi0x77923f08 140737346944776 rdi0x101040104070701 72343471423686401 rbp0x55589d20 0x55589d20 rsp0x7fffdf10 0x7fffdf10 r8 0xf 15 r9 0x5556da50 93824992336464 r100x0 0 r110x246 582 r120x778e92b0 140737346704048 r130x77b2cd90 140737349078416 r140x2 2 r150x77b2cd80 140737349078400 rip0x779f49bd 0x779f49bd <__GI___libc_free+29> eflags 0x10202 [ IF RF ] cs 0x3351 ss 0x2b43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 1: x/i $pc => 0x779f49bd <__GI___libc_free+29>:mov-0x8(%rdi),%rax #0 __GI___libc_free (mem=0x101040104070701) at malloc.c:3093 #1 0x777c09f0 in OPENSSL_sk_pop_free () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #2 0x778ecc29 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #3 0x7775af1a in OPENSSL_cleanup () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #4 0x779aa2b7 in __cxa_finalize (d=0x778b2000) at cxa_finalize.c:83 #5 0x7765c093 in ?? () from
Bug#929764: [Pkg-gtkpod-devel] Bug#929764: usbmuxd segfaults on startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2019-05-30 at 12:36 -0400, James Henried wrote: > Reopening #919630. > > Have been running into trouble mounting an iPhone with ifuse. Noticed that > usbmuxd segfaults on startup: Hi, can you also provide the information asked in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919630#10 ? It still doesn't happen here so there's something system-specific somewhere. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlzw0+4ACgkQ3rYcyPpX RFvmSwgAvx5vpvjEJi1ZsHoyIXaWZFMut3X58p/HTyr3v4FFJ1NjDeiZ9DWYg5kW kpCHXPvWB5cYe+KkwdfO8mSHbhoBw++x8qrnP6pRplON4J9E5pO/hl4aJenZX1rD S7p9kHDt+x7PGp4HQ1ux5hGHESkNbk7A7IHPih87juuOWnF1CObWFz3uAkDSoZy8 qeGWNBuc2o2ZP+vUCZrgG6wOE3eewxNyXgW0NLX30pt3e9OsVA1s44Vcg5TYzRXn FIGQzSxLOJQmtjLGGrsk+sFH0KgQ+1UHJl1a+Pf1hT5T4FhXyCFmEdvK/1IkL78c O4X8PdXJ6pIt8B81qsjUE+wC3jztaA== =thI3 -END PGP SIGNATURE-
Bug#929764: usbmuxd segfaults on startup
Control: tags -1 + moreinfo Hallo James Henried, was just looking through some random bug reports. Maybe you could install the package systemd-coredump. That way in the journal would appear a backtrace that could give some hints where the segmentation fault happens. Visible in the output of: journalctl --no-pager Additional you could install the package gdb and start usbmuxd with the following command: script -a ~/gdb-usbmuxd_$(date +%Y-%m-%d_%H-%M-%S).log -c "gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'run' -ex 'info reg' -ex 'display/i \$pc' -ex 'bt' -ex 'info share' -ex 'bt full' -ex detach -ex quit --args usbmuxd" That should generate a file with a better backtrace of the crashing process that you may forward to this bug report. Even better would be if before running this you install some debug symbol packages like described in following link: https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols In your case the package usbmuxd-dbgsym would be the first, maybe others get requested when a first backtrace is received. Kind regards, Bernhard
Bug#929764: usbmuxd segfaults on startup
Package: usbmuxd Version: 1.1.1~git20181007.f838cf6-1 Severity: important Dear Maintainer, Reopening #919630. Have been running into trouble mounting an iPhone with ifuse. Noticed that usbmuxd segfaults on startup: # usbmuxd Segmentation fault # usbmuxd free(): double free detected in tcache 2 Aborted # usbmuxd Segmentation fault # usbmuxd free(): double free detected in tcache 2 Aborted # When running ifuse, I get similar errors: # ifuse /media/iphone/ No device found, is it connected? If it is make sure that your user has permissions to access the raw usb device. If you're still having issues try unplugging the device and reconnecting it. double free or corruption (fasttop) Aborted # -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages usbmuxd depends on: ii adduser3.118 ii libc6 2.28-5 ii libimobiledevice6 1.2.1~git20181030.92c5462-1 ii libplist3 2.0.1~git20190104.3f96731-1 ii libusb-1.0-0 2:1.0.22-2 usbmuxd recommends no packages. usbmuxd suggests no packages. -- no debconf information This has been happening for a while. Previously, I had no problem mounting an iphone and reading its contents. Now, ifuse doesn't see it at all. This is a phone with IOD 10.3.3. It's seen by lsusb: Bus 001 Device 012: ID 05ad:13a8 Apple, Inc. iPhone5/5C/5S/6 # ideviceinfo No device found, is it plugged in? double free or corruption (fasttop) Aborted # Thanks so much for your help!
