usbmuxd is not compatible with libusbmuxd2 in ubuntu 14.10

Bug #1363583 reported by Xu Zhen
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
usbmuxd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

In Ubuntu 14.10, the version of libusbmuxd2 is 1.0.9, but usbmuxd is still 1.0.8.
usbmuxd 1.0.8 does not support the new commands used in libusbmuxd2 1.0.9
Any program which use libusbmuxd2 will simply crash.

$ ideviceinfo
ideviceinfo: plist.c:194: plist_copy_node: Assertion `data' failed.
Aborted

the debug output of usbmuxd:
$ sudo usbmuxd -v -f -u
[15:29:58.274][3] usbmuxd v1.0.8 starting up
[15:29:58.274][4] Creating socket
[15:29:58.274][4] Initializing USB
[15:29:58.276][4] Found new device with v/p 05ac:129a at 2-7
[15:29:58.276][4] Found interface 1 with endpoints 04/85 for device 2-7
[15:29:58.277][4] Using wMaxPacketSize=512 for device 2-7
[15:29:58.277][3] Connecting to new device on location 0x20007 as ID 1
[15:29:58.277][4] 1 device detected
[15:29:58.277][3] Initialization complete
[15:29:58.278][3] Connected to v1.0 device 1 on location 0x20007 with serial number *******
[15:30:07.646][4] New client on fd 14
[15:30:07.646][1] Unexpected command 'ListDevices' received!
[15:30:07.646][4] Client 14 connection closed
[15:30:07.646][4] Disconnecting client fd 14
[15:30:07.647][4] New client on fd 14
[15:30:07.747][4] Client 14 connection closed
[15:30:07.747][4] Disconnecting client fd 14
[15:30:07.747][4] New client on fd 14
[15:30:07.754][4] New client on fd 15
[15:30:07.755][1] Unexpected command 'ReadPairRecord' received!
[15:30:07.755][4] New client on fd 16
[15:30:07.755][1] Unexpected command 'ReadPairRecord' received!
[15:30:07.757][4] Disconnecting client fd 14
[15:30:07.757][4] Client 15 connection closed
[15:30:07.757][4] Disconnecting client fd 15
[15:30:07.757][4] Client 16 connection closed
[15:30:07.757][4] Disconnecting client fd 16

I complied the latest source from https://github.com/libimobiledevice/usbmuxd, everything works.
$ sudo usbmuxd -v -f -u
[15:38:13.038][3] usbmuxd v1.0.9 starting up
[15:38:13.038][4] Creating socket
[15:38:13.038][4] Initializing USB
[15:38:13.040][4] Found new device with v/p 05ac:129a at 2-7
[15:38:13.041][4] Found interface 1 with endpoints 04/85 for device 2-7
[15:38:13.042][4] Using wMaxPacketSize=512 for device 2-7
[15:38:13.042][3] Connecting to new device on location 0x20007 as ID 1
[15:38:13.042][4] 1 device detected
[15:38:13.042][3] Initialization complete
[15:38:13.042][3] Connected to v2.0 device 1 on location 0x20007 with serial number *******
[15:38:13.042][4] preflight_worker_handle_device_add: Starting preflight on device *******...
[15:38:13.043][4] New client on fd 16
[15:38:13.045][4] device_control_input: AppleUSBDeviceMux::handleConnectResult new session 0x8bc4a000 established 62078<-lo0->49706 62078<-usb->1
[15:38:13.050][4] New client on fd 18
[15:38:13.054][4] New client on fd 20
[15:38:13.184][4] preflight_worker_handle_device_add: StartSession success for device *******
[15:38:13.184][4] preflight_worker_handle_device_add: Finished preflight on device *******
[15:38:13.188][4] Disconnecting client fd 16
[15:38:13.189][4] device_control_input: void AppleUSBDeviceMux::handleMuxTCPInput(__mbuf*) received reset, closing 0x8bc4a000
[15:38:30.383][4] New client on fd 15
[15:38:30.383][4] New client on fd 16
[15:38:30.383][4] Client 15 connection closed
[15:38:30.383][4] Disconnecting client fd 15

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in usbmuxd (Ubuntu):
status: New → Confirmed
Revision history for this message
Steven Douglas (stevesmename) wrote :

I believe that usbmuxd being out of date is causing other issues too:
https://github.com/libimobiledevice/libimobiledevice/issues/172

Revision history for this message
Dylan Aïssi (daissi) wrote :

Ubuntu 14.10 is EOL since July 2015. New versions of Ubuntu have new versions of usbmuxd and libusbmuxd

Changed in usbmuxd (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.