-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Sat, 2019-10-05 at 14:50 +0200, Yves-Alexis Perez wrote: > That beeing said, it would be helpful to know when the problem started > appearing for you. libimobiledevice wasn't updated recently, but libusbmuxd > was, and it seems that there might be a really tight dependency between both, > and the libimobiledevice currently in testing and sid (there's a one sitting > in NEW) was built against the previous version of libusbmuxd.
If the crashed appeared recently, I'd guess it's due to the struct change in: https://github.com/libimobiledevice/libusbmuxd/commit/f5a7387a54ae08c9cd1d83a415393e0e909dc6e6#diff-038b1c435b1baca0fc7faaf5e375f401L37 Unfortunately, there is no real SONAME tracking in libusbmuxd apparently, and I missed it too. I think a rebuild of libimobiledevice should fix the issue at hand, until the new one exits NEWS. Long term a proper solution should be found, I'll try to ask upstream about that. Regards, - -- Yves-Alexis -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl2YnXcACgkQ3rYcyPpX RFskrggApmspfJRWofKg3JxrG5JSQpgWmNyk4GPqw2lAcMllqYnQZ2Gu7lPlHziN JNaADOPxze+frdyapaOHQBoccFT/gTcyyZ+y7nPvM7OiJux8GIENV8fKYV/YBBON Y5C8VeOQC080yBfB+V4zJadrLT1AdoOLPuD6ve9CH3UfClIsiHu1bcvIN5B0tAZW JKVK/J2kLMtJRLrH2Q9zkXkOrSC9q/Pb+6VkHN75pIbYc9K1YKK0Dim3cT++OXHb nqRKXWpX/275BxQpnuQuoXxqLSDsk6jSGEZUx2qikbJgyyBWAeT7iNds15iCu1j/ nIs8wURnEXWMLDy4M+SMLsy+EcACXA== =Lm+g -----END PGP SIGNATURE-----
