Description of problem: Android and Windows phones (i.e more than 80% of the smartphone market) use MTP protocol to interact with a PC. I think it would be a goo idea, then, that the package kio-mtp is installed by default on any Mageia clean install. Reproducible: Steps to Reproduce:
Do you mean any Mageia Plasma install, or really any Mageia install? Is kio-mtp used outside KDE / Plasma?
Yes, any Mageia install. I installed Mageia Cinnamon on a netbook for my mother but I forgot to install kio-mtp so she was unable to acces her phone.
This bug report is too generic. It involves various different maintainers. There are several different packages for handling the mtp protocol, so I'm not sure forcing the installation of kio-mtp for everyone is the right solution. I would advise to close this bug report, or rename it as "Make sure the mtp protocol is handled in every Desktop Environment", and create on bug report per Environment where it is missing, in your case one for Cinnamon. These bug reports can be linked to this one via the Blocks: field.
Alternatively, you can make a feature proposal (see the ongoing discussion in the dev@ml.mageia.org mailing list) for better handling of MTP in Mageia in general, but this would need to be more detailed than just adding kio-mtp everywhere. The issue is more complex than that.
Wait, what other packages are involved in managing MTP protocol?
Well, for a starter in cauldron theres kio4-mtp and kio5-mtp. There's also mtp-utils, maybe gmtp, gvfs-mtp...
CCing David Walser who knows better than me.
CC: (none) => luigiwalser
> Well, for a starter in cauldron theres kio4-mtp and kio5-mtp. There's also mtp-utils, maybe gmtp, gvfs-mtp... Fuck yeah ! Why keep it simple!? -_-
We already have a bug (Bug 11394) for kio-mtp installed by default, which was already fixed. kio-mtp isn't a full solution though, because it relies on the mtpfs code which is broken for most newer phones. jmtpfs works fine, but is not packaged. We also have Bug 7638 for that. Upstream KDE also needs to fix kio-mtp. *** This bug has been marked as a duplicate of bug 11394 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE