Comment 8 for bug 611020

Same problem. The process stays resident after the phone has been disconnected. It occurs after multiple connect/disconnect cycles.

Arch:
Linux 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:05:27 UTC 2010 x86_64

I have an Athlon II processor if that matters.

Here is the backtrace:

(gdb) thread apply all bt

Thread 1 (Thread 0x7ff48efd3700 (LWP 29856)):
#0 0x00007ff48ebd7e72 in send () from /lib/libpthread.so.0
#1 0x00007ff48ca698bb in usbmuxd_send () from /usr/lib/libusbmuxd.so.1
#2 0x00007ff48e18301d in ?? () from /usr/lib/libimobiledevice.so.0
#3 0x00007ff48e1830fa in ?? () from /usr/lib/libimobiledevice.so.0
#4 0x00007ff48d2a55da in ?? () from /usr/lib/libgnutls.so.26
#5 0x00007ff48d2a278d in _gnutls_send_int () from /usr/lib/libgnutls.so.26
#6 0x00007ff48d2bf07d in gnutls_alert_send () from /usr/lib/libgnutls.so.26
#7 0x00007ff48d2a2c43 in gnutls_bye () from /usr/lib/libgnutls.so.26
#8 0x00007ff48e182a59 in idevice_connection_disable_ssl ()
   from /usr/lib/libimobiledevice.so.0
#9 0x00007ff48e183357 in idevice_disconnect ()
   from /usr/lib/libimobiledevice.so.0
#10 0x00007ff48e184f46 in property_list_service_client_free ()
   from /usr/lib/libimobiledevice.so.0
#11 0x00007ff48e1872c9 in lockdownd_client_free ()
   from /usr/lib/libimobiledevice.so.0
#12 0x000000000040182f in ?? ()
---Type <return> to continue, or q <return> to quit---
#13 0x00000000004012ef in ?? ()
#14 0x00007ff48de18c4d in __libc_start_main () from /lib/libc.so.6
#15 0x00000000004011b9 in ?? ()
#16 0x00007fff47d05f58 in ?? ()
#17 0x000000000000001c in ?? ()
#18 0x0000000000000001 in ?? ()
#19 0x00007fff47d07d44 in ?? ()
#20 0x0000000000000000 in ?? ()