libimobiledevice is built with openssl now
https://launchpad.net/ubuntu/+source/libimobiledevice/1.3.0-4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1854403
Tit
So I've checked with the Debian maintainer, the package needs to build
with gnutls for licensing reasons, specific in https://alioth-
lists.debian.net/pipermail/pkg-gtkpod-devel/2020-June/004615.html , we
are going to fix the gnutls backend if we want that issue resolved
--
You received this bug
Ah, sorry. Yes, if you rebuild the focal package with f56a65f and use
openssl, then connectivity and file transfers work correctly. There does
not appear to be any other changes required. I can't vouch for all the
functionality, of course. The device backup functionality seems popular,
but I don't
@Philip, thanks, I guess my question was not specific enough, let's me
rephrase 'any idea if rebuilding focal with f56a65f included and openssl
is enough or do we need other changes/updates to have a working stack
there?
--
You received this bug notification because you are a member of Ubuntu
Tou
So, the new builds are new enough versions but libimobiledevice is still
built against gnutls and so file transfers don't work. If I build my own
library at the 1.3.0 version against openssl and drop it in, then it all
works fine.
The new builds of libplist and libusbmuxd are very helpful as they
Upstream rolled new versions and they landed in Debian and now Ubuntu
https://bugs.launchpad.net/ubuntu/+source/libplist/2.2.0-3
https://bugs.launchpad.net/ubuntu/+source/libusbmuxd/2.0.2-2
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/1.3.0-2
Could someone with access to a device tr
Unsure if we want to switch to openssl, that would be a request to make
to Debian. There might have been a (license) reason to prefer gnutls
there
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
htt
Upstream fix for the openssl issue is in: f56a65f in libimobiledevice.
Taking advantage of that requires switching the ubuntu build from using
gnutls to openssl.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevic
https://github.com/libimobiledevice/libimobiledevice/issues/941
** Bug watch added: github.com/libimobiledevice/libimobiledevice/issues #941
https://github.com/libimobiledevice/libimobiledevice/issues/941
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
I've upgraded to 20.04 and have checked out the installed versions. For
now, I was able to get it working "just" by upgrading libimobiledevice
to the latest git and building against gnutls (using openssl resulted in
it needing to re-trust every time I plug in because the TLS information
it is savin
Ok, so this is progress. Building against gnutls fixes the trust
pairing, but breaks file transfers. I rebuild the same source with
openssl vs gnutls and that's exactly what I see. With openssl I have to
re-pair every time I plug in but with gnutls, the file transfers don't
work.
The official ubun
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403
may be solved by installing the latest version of
libplist
libimobiledevice
libusbmuxd
usbmuxd
I tested it and write access works again, see comment
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/comm
Ok, I forgot another crucial step to mention:
after installing the libraries, you have to run
sudo ldconfig -v
to move the new libs in /usr/local/lib to the front
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimo
Followed the advice of Jackfritt at
https://github.com/libimobiledevice/libimobiledevice/issues/903
I had to additionally do the same for usbmuxd:
sudo apt-get install
git clone https://github.com/libimobiledevice/usbmuxd.git
./autogen.sh
make
sudo make install
then reboot.
Verified for Ubuntu
In previous comment
sudo apt-get install
should read
sudo apt-get install libusb-1.0-0-dev
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1854403
Title:
Ne
I can't test the latest packages fully because I'm running eoan but I
did install the packages from focal and it didn't work, while I'm home-
built binaries from mid october do work, so maybe some regressed? The
usbmuxd upgrade is fine, but libimobiledevice/libusbmuxd is what breaks
it. I can't dis
iPhone 7, latest software update iOS 13.3 (17C54), seems to fix this. I
could successfully transfer files TO the phone using ubuntu 18.04.3 LTS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https
Photo access (gphoto2://) works in both Ubuntu 18.04 and 20.04.
Documents access (afc://) works in Ubuntu 18.04 in reading mode - I can copy
file from iPhone to PC. But it hangs (forever 0%) while copy one small file to
iPhone device.
In Ubuntu 20.04 I get errors for both case (copy file from iP
No luck with Ubuntu 20.04 (trying to copy mp3 file to VLC folder on
iPhone):
"Error while copying test.mp3. There was error copying file into afc
://some-id/org.videolan.vlc-ios. The connection was interrupted."
Something broken with iOS 13 update...
--
You received this bug notification becaus
I'll try out the focal builds when I get a chance.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1854403
Title:
Need updated libimobiledevice and dependencies to
At the time I filed the bug, I did not notice an updated build in focal
- it was still the same one as in eoan, but perhaps I was just not
paying enough attention. I will try it out. That version is likely to be
new enough to work, although I know there was an update to libusbmuxd
with a version an
We first need to assert if it's working in the current version, then it
would be nice to backport support to Bionic but that might be non
trivial since it involves a soname change/transition
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Thank you for your bug report. Could you try on the current Ubuntu serie
(focal), it should work there?
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/1.2.1~git20190929.60823f9-1
** Changed in: libimobiledevice (Ubuntu)
Importance: Undecided => High
** Changed in: libplist (Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libusbmuxd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: usbmuxd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.la
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libimobiledevice (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libplist (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.l
27 matches
Mail list logo
