Description of problem: Current version for libimobiledevice in Mageia 4 can't communicate with my iPad so therefor I'm requesting a backport of this package along with its deps such as plist, ifuse, usbmuxd and perhaps also libusbmuxd2. I have tested if this issue exists in Cauldron and it seems to be solved as pressing "Allow" makes the window to stop reappearing. Version-Release number of selected component (if applicable): 1.1.6 How reproducible: All the time. Steps to Reproduce: 1. Install Mageia 4. 2. Use all medias except Backports. 3. Install all the above mentioned packages in case they're not installed. 4. Connect any Apple device to the USB-slot. 5. When prompted on the device, press "Allow". 6. Now, on the computer you should see a window message stating that the device is locked and that you need to unlock it. Reproducible: Steps to Reproduce:
This happens on all the preinstalled kernels for both archs and also in 3.12.26-tmb-laptop-1.mga4
CC: (none) => kristoffer.grundstrom1983Version: 4 => Cauldron
Priority: Normal => High
Summary: libmobiledevice can't communicate with Apple devices => libimobiledevice can't communicate with Apple devices
I hope this helps in any way: but under current Cauldron I can import my iPad pictures with digikam. Use the menu <import> two or three times in a row and it works. I did not check if it uses libimobiledevice, but I suspdct it does.
CC: (none) => dvgeversComponent: Backports => RPM Packages
It might be a permission issues on /dev/* in mga4
CC: (none) => thierry.vignaud
I'll test this when I get home.
(In reply to Dick Gevers from comment #2) > I hope this helps in any way: but under current Cauldron I can import my > iPad pictures with digikam. Use the menu <import> two or three times in a > row and it works. I did not check if it uses libimobiledevice, but I suspdct > it does. The problem isn't importing pictures. The problem is that Mageia can't communicate and mount the iPad (when you press the Allow-button on it) on the desktop because of a faulty library.
How soon can I expect the version to become backported from Cauldron?
*** Bug 14021 has been marked as a duplicate of this bug. ***
CC: (none) => leon244
More than a backport, I guess there should be an update to libimobiledevice. I'm not sure about the other packages that you mention though: plist, ifuse, usbmuxd and perhaps also libusbmuxd2. Do they really need to be updated, or did you just list them because you would like their latest versions to be backported for additional features?
Priority: High => NormalVersion: Cauldron => 4Severity: minor => normal
Summary: libimobiledevice can't communicate with Apple devices => libimobiledevice can't communicate with Apple devices (works in cauldron)
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD