Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#60789 - [usbmuxd] Version incompatibility or package outdated?

Attached to Project: Arch Linux
Opened by Mateusz Paluszkiewicz (TheAifam5) - Tuesday, 13 November 2018, 11:09 GMT
Last edited by Giancarlo Razzolini (grazzolini) - Thursday, 22 November 2018, 17:31 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Giancarlo Razzolini (grazzolini)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description:
The issue applies to both packages. I am unable to determine if that's a version compatibility issues or just package is outdated.
The package versions looks ok, I mean they are up-to-date. One of the members of this project said:

you need to use latest libimobiledevice. I introduced a change that made the most recent commit necessary.

Error message:
preflight_worker_handle_device_add: ERROR: Could not connect to lockdownd on device XXXXX, lockdown error -8

Additional info:
Related GitHub issue: https://github.com/libimobiledevice/usbmuxd/issues/95

Steps to reproduce:
1. Install libimobiledevice
2. Install usbmuxd
3. Connect an Apple device (with iOS12?)
4. Execute `usbmuxd -f -v`
5. Search for `preflight_worker_handle_device_add` error message.
This task depends upon

Closed by  Giancarlo Razzolini (grazzolini)
Thursday, 22 November 2018, 17:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with new versions of libimobiledevice, usbmuxd and libusbmuxd
Comment by Mateusz Paluszkiewicz (TheAifam5) - Tuesday, 13 November 2018, 11:10 GMT
Also looks like downgrading the usbmuxd package to 1.1.0+28+g46bdf3e-1 fixes the problem (based on GitHub comment).
Comment by Gabriel Morrison Lima Dantas (countercraft) - Wednesday, 14 November 2018, 12:05 GMT
I did upgrade the related packages (usbmuxd, libusbmuxd and libimobiledevice) to the current git master and this also solves the problem, as indicated by the devs on the GitHub issue.
Comment by F. Kiersch (Mortes) - Wednesday, 14 November 2018, 12:52 GMT
I flagged libusbmuxd as out of date. I assume libimobiledevice should be correct at 1.2.0+66+g5a85432-2?
Comment by Gabriel Morrison Lima Dantas (countercraft) - Wednesday, 14 November 2018, 13:03 GMT
No, the Arch version of libimobiledevice is also too old, that's part of the problem. I've flagged libimobiledevice as well.
Comment by Giancarlo Razzolini (grazzolini) - Sunday, 18 November 2018, 23:49 GMT
I have updated all the relevant packages and I have tested iphone connection and it seems to be working. ifuse was affected by this issue as well and it is also working. Can you guys please test with the current packages and let me know if it works?
Comment by Eli Schwartz (eschwartz) - Monday, 19 November 2018, 04:06 GMT
So uh, score 1 for packaging development versions with no clear cause?
Comment by Giancarlo Razzolini (grazzolini) - Monday, 19 November 2018, 10:04 GMT
@Eli,

The packages have been packaging from git master branches for quite some time, check the git log. libimobiledevice, usbmuxd and libusbmuxd haven't received a proper release in quite some time now. I don't like it as much as you, but it is the only way to get recent code.
Comment by Gabriel Morrison Lima Dantas (countercraft) - Monday, 19 November 2018, 11:50 GMT
@Giancarlo, thanks, I can confirm everything is working now.
Comment by Mateusz Paluszkiewicz (TheAifam5) - Monday, 19 November 2018, 12:22 GMT
@grazzolini Im gonna make an issue there to integrare a proper semantic version system.
Comment by Giancarlo Razzolini (grazzolini) - Monday, 19 November 2018, 12:50 GMT
@Mateusz

I think the main issue is, that libimobiledevice, usbmuxd and libusbmuxd have not been actively maintained over the last 4 years. There has been very little activity on the repositories and no official releases in quite a long time. But, still, these projects have seen some patches here and there, to make sure they continue working. Make an issue if you want, but I don't see anything changing in the near future without an active maintainer.

Loading...