iDevice not detected on Ubuntu13.04 about libimobiledevice

[FunkyM]

Please verify if usbmuxd is running.

[uncommonthinker]

Yes its running, i even started the usbmuxd by forking it
usbmuxd&
But after entering the command its the same...
No device found, is it plugged in?
[1]+ Done usbmuxd

Does automount matters in this case ?
Cause i doubt that system is not allowing it to mount .. i have another ideapad with same 13.04 and , when i had installed the libimobiledevice older version which worked with pre ios7 devices, its working fine there .... So what may keep this 13.04 from not running the commands ?

I connected and had the syslog print the output after i connected the device i found this

ipheth 3-2:4.2: ipheth_rcvbulk_callback: urb status: -71
[ 1212.338835] usb 3-2: USB disconnect, device number 5
[ 1212.367248] ipheth 3-2:4.2: Apple iPhone USB Ethernet now disconnected
[ 1212.700053] usb 3-2: new high-speed USB device number 6 using xhci_hcd
[ 1212.717733] usb 3-2: New USB device found, idVendor=05ac, idProduct=12a8
[ 1212.717751] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1212.717762] usb 3-2: Product: iPhone
[ 1212.717771] usb 3-2: Manufacturer: Apple Inc.
[ 1212.717779] usb 3-2: SerialNumber: e3ef574270f192e6e46ed2d13a38defd6b120165
[ 1212.718158] usb 3-2: ep 0x2 - rounding interval to 8 microframes, ep desc says 10 microframes
[ 1212.718180] usb 3-2: ep 0x81 - rounding interval to 8 microframes, ep desc says 10 microframes
[ 1212.728270] usb 3-2: ep 0x2 - rounding interval to 8 microframes, ep desc says 10 microframes
[ 1212.728282] usb 3-2: ep 0x81 - rounding interval to 8 microframes, ep desc says 10 microframes
[ 1212.739466] ipheth 3-2:4.2: Apple iPhone USB Ethernet device attached
[ 1212.757968] usbmuxd[2997]: segfault at 0 ip 00007f3f80c97301 sp 00007fff15700748 error 4 in libc-2.17.so[7f3f80b2d000+1bf000]
[ 1212.783763] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 1212.784100] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

[FunkyM]

You are most likely still running another instance of usbmuxd. Make sure to disconnect devices, then start usbmuxd manually. If it works, check if you don't have an older version installed in parallel and remove it.
The usbmuxd command is also supposed to be run as an "usbmux" user with USB device privileges (or you can test it as root).
You can manually run "usbmuxd -f" to see what it reports during startup.

[uncommonthinker]

I did as u mentioned .... disconnected devices, rebooted system and entered the command on the terminal
$ sudo usbmuxd -f
[09:58:35.256][3] usbmuxd v1.0.9 starting up
[09:58:35.263][3] Connecting to new device on location 0x10007 as ID 1
[09:58:35.263][3] Initialization complete
$ idevice_id -l
ERROR: Unable to retrieve device list!

Same error... :(

[FunkyM]

Well, usbmuxd must be running all the time, does it exit automatically?
If yes, try to increase verbosity by adding a "-v" argument after "-f".

[uncommonthinker]

Yes, it gave me segfault as seen in dmesg output as i mentioned in my second comment

[FunkyM]

Please run "gdb --args usbmuxd -f -v" as root. Inside the console write "r" to start the process, once it crashes write "bt" and post the output here. You can exit gdb by entering "q".

[uncommonthinker]

Here is the output :

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff731e301 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x00007ffff731e301 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007ffff77a115b in plist_get_string_val (node=0x0,
val=val@entry=0x7fffffffe2b8) at plist.c:582
#2 0x0000000000405500 in client_command (hdr=0x649050, client=0x615c30)
at client.c:479
#3 process_recv (client=0x615c30) at client.c:714
#4 client_process (fd=, events=) at client.c:740
#5 0x0000000000404172 in main_loop (listenfd=8) at main.c:235
#6 main (argc=, argv=) at main.c:642

[FunkyM]

Have you updated and use latest libusbmuxd?

[uncommonthinker]

Its libusbmuxd1.0.9 as given on the libimobiledevice site .... is there any newer version of this ?

I tried again on 2 another ideapads with Ubuntu13.04 and here i am with the same issue .... So is it Ubuntu OS version issue ?? And are there any specific packages needed to be installed for the same ??

Device and version : Lenovo ideapad Ubuntu13.04 raring (x86_64)

[uncommonthinker]

Can you guide me how to remove the entire library from the machine and install afresh ? @FunkyM

I have tried the same process on 2 Ubuntu machines with 12.04 and with success ....

[FunkyM]

The backtrace you posted shows that there is actually a malformed message sent between libusbmuxd and usbmuxd which is the cause of the crash.
However, we are still investigating how such a situation could even be possible...

For removing everything, make sure to remove all related packages in Ubuntu and if you compiled from source, enter each source directory that you used during install and enter "sudo make uninstall". As a last resort check "/usr/lib" and "/usr/local/lib" for traces of any of the libraries.

[uncommonthinker]

Ok, even i am unsure about how this could have happened when the process of installation on both the versions(13.04 and 12.04) were same.

So does earlier versions of usbmuxd and libusbmuxd have dependencies on the newer versions, means do i have to install them and then try again installing the newer versions ?

I will try to make a new installation, but i can do that only 3 days later. So till then maybe you guys can figure out something.

Thanks for all your support @FunkyM. I will be in touch again.

[nikias]

I think I know what happened. The ibusbmuxd 1.0.9 is meant to use libplist 1.11 new API which uses plist_dict_set_item() instead of plist_dict_insert_item(). Now if somehow libusbmuxd 1.0.9 is used with a previous version of libplist, plist_dict_set_item() will not actually insert new keys but would only set the values if the keys are already present - which is not the case. As a result this means that an empty dictionary is sent to usbmuxd which would explain the behavior/crash in usbmuxd.

[FunkyM]

Ah good point, what probably happend is that although he's been compiling the new sources, autofoo picked up the system libplist (which is older) and thus causes this issue.
@nemecence90 Please try to post the output of "# ldd /usr/local/lib/libusbmuxd.so". If you can please do so with the other libraries, too.

[FunkyM]

The backtrace appears to show the same problem reported here: libimobiledevice/usbmuxd#12
The ticket was solved by updating libplist, so there is a chance that this applies here aswell.

[uncommonthinker]

Here is the output you asked for.

$ ldd /usr/local/lib/libusbmuxd.so
linux-vdso.so.1 => (0x00007fffabffe000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f031662d000)
libplist.so.2 => /usr/local/lib/libplist.so.2 (0x00007f0316422000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0316058000)
/lib64/ld-linux-x86-64.so.2 (0x00007f0316a67000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x00007f0315cf5000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f0315af1000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f03158d9000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f03156b7000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f03153b2000)

$ ldd /usr/local/lib/libimobiledevice.so
linux-vdso.so.1 => (0x00007fff317fe000)
libusbmuxd.so.2 => /usr/local/lib/libusbmuxd.so.2 (0x00007fc102147000)
libplist.so.2 => /usr/local/lib/libplist.so.2 (0x00007fc101f3c000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fc101d0b000)
libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007fc101aae000)
libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007fc1016d3000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc101309000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x00007fc100fa6000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc102569000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fc100da2000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fc100b8a000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fc100968000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fc100663000)

$ ldd /usr/local/lib/libplist.so
linux-vdso.so.1 => (0x00007fff60911000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x00007f7ac551c000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7ac5153000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7ac4f4e000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f7ac4d37000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f7ac4b15000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f7ac480f000)
/lib64/ld-linux-x86-64.so.2 (0x00007f7ac5a9f000)

[uncommonthinker]

Hey @FunkyM any solution to the situation ?? Still struggling :(

[uncommonthinker]

Hey @FunkyM .. I installed a afresh and on running

$ sudo usbmuxd -v -f

I am getting the following error and its stopping ... I installed the latest builds again and tried still sam issue ...

The issue :
usbmuxd: symbol lookup error: /usr/lib/libimobiledevice.so.4: undefined symbol: usbmuxd_read_buid

[nikias]

@nemecence90 your usbmuxd is linked against and old version of libimobiledevice.

[uncommonthinker]

So how do i solve it ??

On Friday, 11 April 2014, Nikias Bassen [email protected] wrote:

@nemecence90 https://github.com/nemecence90 your usbmuxd is linked
against and old version of libimobiledevice.

Reply to this email directly or view it on GitHubhttps://github.com//issues/68#issuecomment-40222111
.

• Abhishek Shah
  Sent from my iPhone

[abmobidev]

I tried updating to latest commit of libinobiledevice and also libusbmuxd but to no success .... The issue its showing me is in libinobiledevice.so.4 ... It doesnt automatically update it in in /usr/lib whereas its present in /usr/local/lib

[uncommonthinker]

Hey @FunkyM @nikias , i tried again and the issue seemed with gnome panel and other dependencies which got installed with it, and i was able to perform it for the same.

[uncommonthinker]

Hello,

My about.me page tells my personal and professional story online. I also use it to learn about and connect with others. It's fun, easy, and I thought you'd like it, too.

Best,
Abhishek

https://about.me/new_user?invite_code=5d7e2595e62c468fa322072b5b333741&invite_token=cmHrLE33g17oKDcSxPTm5sKJ4Sqfd8rsZabmFolBDRENZ_wpoKZDus5i5Dg5WmzAJz-n9ZFKFS0FHU4o8902RFEAI9pqCBSGvVaCuOQZJyVswcrxCf_Pg8slW2iLBSYoKQz3BJXG

Learn more: http://about.me