Libiphone libiphone

Comments and changes to this ticket

• 

  Martin S. May 11th, 2010 @ 12:45 PM

  • Tag set to “debian, ifuse, mounting”
  • State changed from “new” to “open”

  Run "sudo usbmuxd -v -f" manually and watch the output after pluging in your device.
  If then ideviceinfo works as regular user, it's a permission issue.

• You flagged this item as spam.
  

  Ferry May 11th, 2010 @ 03:53 PM

  Martin,
  Thanks for yr response. I have the same issue as root, normal user or using sudo.

  vink@debian:~$ sudo usbmuxd -v -f
  [17:45:06.283][3] usbmuxd v1.0.0 starting up [17:45:06.283][4] Creating socket [17:45:06.283][4] Initializing USB [17:45:06.284][4] 0 devices detected [17:45:06.284][3] Initialization complete [17:45:12.980][4] Caught SIGUSR1/2 but we weren't started in --udev mode, ignoring [17:45:13.292][4] Found new device with v/p 05ac:1293 at 5-3

  vink@debian:~$ ideviceinfo
  recv: Success
  usbmuxd_get_device_list: Did not get response to scan request (with result=0)...
  No device found, is it plugged in?

  Anything else I can check?

• 

  Martin S. May 14th, 2010 @ 01:55 PM

  The issue is most likely a misconfigured system.

  Did you ever install libiphone (have traces of it left in /usr/lib/libiphone*)?

  Please run "sudo usbmuxd -v -f" and keep it running in a terminal.
  Open another one and enter "ideviceinfo" there (non root).

  The usbmuxd output should show more than the "[17:45:13.292][4] Found new device with v/p 05ac:1293 at 5-3" line.
  Does usbmuxd perhaps exit/crash after this line or why is there no more output (there must be more)?

• You flagged this item as spam.
  

  Ferry May 14th, 2010 @ 03:08 PM

  Install is clean. No leftovers.

  When I run usbmuxd without the device being plugged in I get this:
  vink@debian:~$ sudo usbmuxd -v -v -f
  [sudo] password for vink: [17:00:32.052][3] usbmuxd v1.0.0 starting up [17:00:32.053][4] Creating socket [17:00:32.053][5] client_init [17:00:32.053][5] device_init [17:00:32.053][4] Initializing USB [17:00:32.053][5] usb_init for linux / libusb 1.0 [17:00:32.054][4] 0 devices detected [17:00:32.054][3] Initialization complete

  On the other terminal I call ideviceinfo without the device being plugged in. The muxd output then looks like this:
  [17:01:32.219][4] New client on fd 7 [17:01:32.220][5] Client command in fd 7 len 16 ver 0 msg 3 tag 2 [17:01:32.220][5] send_pkt fd 7 tag 2 msg 1 payload_length 4 [17:01:32.220][5] Client 7 now LISTENING [17:01:33.220][4] Client 7 connection closed [17:01:33.220][4] Disconnecting client fd 7

  And the other terminal shows it can't find the device (logical):
  vink@debian:~$ ideviceinfo
  No device found, is it plugged in?

  When I plug in the device:
  [17:02:14.517][4] Caught SIGUSR1/2 but we weren't started in --udev mode, ignoring [17:02:15.064][4] Found new device with v/p 05ac:1293 at 5-4

  Then I do a ideviceinfo again:
  vink@debian:~$ ideviceinfo
  recv: Success
  usbmuxd_get_device_list: Did not get response to scan request (with result=0)...
  No device found, is it plugged in?

  Something strange going on here. Appreciate your time.

• 

  Martin S. May 14th, 2010 @ 03:55 PM

  On the last step, with a plugged in device, please look again at what usbmuxd outputs in the other terminal.
  Basically I need the full output of usbmuxd after plugging in the device and running ideviceinfo in parallel.

• You flagged this item as spam.
  

  Ferry May 14th, 2010 @ 05:41 PM

  Well it does not give anymore output and it remains running. There is no sudden kill of usbmuxd or anything like that. No other output either. When I plug out the device and plug it into a other usb port I need to restart usbmuxd to respond. But no messages after it says "Found new device with ..."

• 

  Martin S. May 19th, 2010 @ 02:49 PM

  • Tag changed from “debian, ifuse, mounting” to “debian, ifuse, mounting, usbmuxd”

  Please try the latest usbmuxd 1.0.4 version and repeat the step by manually starting "sudo usbmuxd -v -v -f", then hotplugging the device. I think you should also do a "sudo killall usbmuxd" before actually attempting to run usbmuxd again to make sure to kill any possibly stalled instances. From your description it looks like there is actually an instance of usbmuxd running already.

• You flagged this item as spam.
  

  Ferry May 24th, 2010 @ 06:49 PM

  Installed v1.0.4 no change to what was happening before. Made sure there where no other instances of usbmux running. Any other options I can look at?

• 

  Martin S. June 17th, 2010 @ 04:22 PM

  Still, please post the output of preferably of the latest usbmuxd git master with the verbose flags.

  Also list the versions of libimobildevice, libplist and check /usr/local/lib/ for any leftover "libiphone/libimobiledevice" libraries.

• You flagged this item as spam.
  

  Mark van Walraven October 8th, 2010 @ 09:14 AM

  • Tag cleared.

  I had identical symptoms from 1.0.4 with the Lenny 2.6.26-2-686 kernel. Upgrading to the Squeeze 2.6.32-5-686 kernel has fixed it.

• You flagged this item as spam.
  

  Mark van Walraven October 8th, 2010 @ 09:16 AM

  • Tag set to “debian ifuse mounting usbmuxd”

  (pardon me - tags restored)

• 

  Martin S. March 26th, 2011 @ 10:07 AM

  • Tag changed from “debian ifuse mounting usbmuxd” to “debian, ifuse, mounting, usbmuxd”
  • State changed from “open” to “resolved”

  This looks like a low-level USB issue in Debian to me. Since some time passed by without further information I assume this is fixed.
  If you still encounter this issue please reopen.