you don't have an UMS mode ?

no, I can only switch between MTP and PTP, or enable debugging.

Just updatet to KDE 4.10.5 from updates_testing, no changes.

I noticed that even DigiKam can't access the PTP-Device. CPU-Load goes up to 100%, and nothing more.

Did some further testing: Dolphin and DigiKam even can't access my old Sony Cybershot when it's set to PTP-mode. Shotwell works fine, so it looks like a KDE-related problem with PTP devices.

Update: When launching Dolphin as root it works. Wrong permissions somewhere?

This bug still persists in Mageia 4b2. Dolphin and DigiKam can't access PTP-devices, testet with Galaxy S3 smartphone and Sony Cybershot cam.

Can you try if it works on Mageia 4 beta 2 with GNOME ? To be sure that it's KDE related and not from libmtp. Thx.

CC: (none) => mageia

I have the same problem with my Samsung Galaxy S5 mini and Mageia 4. When I plug my smartphone, Mageia offers me to open it with Dolphin, but Dolphin then displays this error:

"Le processus traitant le protocole mtp s'est arrêté de façon inattendue"

which means "the process which ran the mtp protocol stopped working in an unexpected way".

CC: (none) => LpSolit

I use Dolphin 4.12.5.

The full error message is:

$ mtpfs android
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
   Found 1 device(s):
   Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 15
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0

Yes, I don't know why the mtp stuff is still broken, when there's code out there (jmtpfs and go-mtpfs) that works.

Packaging jmtpfs would be nice (someone has done the work in Bug 7638 already but it's not in the repos), but Dolphin wouldn't benefit from that.

Version: 3 => Cauldron
Whiteboard: (none) => MGA4TOO

Hi,

I would like to put my experiences here too. On MGA5, KDE4 needs to be installed:
# urpmi libmtp9 mtpfs kio-mtp

Then the user must be in the group uucp:
usermod -a -G uucp <USER>

Restart a computer.

After that, modify a file /usr/share/apps/solid/actions/solid_mtp.desktop, where the line:
Exec=kioclient exec mtp:udi=%i/

replace with:
Exec=dolphin "mtp:/"

Now Dolphin is able to open a device from notification window.


What is an issue?:
- if you keep Dolphin opened (as user)
- open Krusader (as user)
- no access to device anymore, from Dolphin, Krusader

How to "repair"?:
- close all file managers
- disconnect a device and connect again
- open only one file manager

I am not sure, if we can do a reset of udev, when the smartphone is still connected with PC.

More information:
https://wiki.mageia.org/en/User:Jharms/File_Transfer_with_Android_Devices
http://translate.google.cz/translate?hl=cs&sl=cs&tl=en&u=http%3A%2F%2Fwiki.mageia.cz%2Fsoftware%3Aostatni%3Aprenos_souboru_mezi_mageiou_a_multimedialnim_zarizenim&sandbox=1
- take care, Google Translate changes command lines. Original in Czech lang. an URL is: http://wiki.mageia.cz/software:ostatni:prenos_souboru_mezi_mageiou_a_multimedialnim_zarizenim

CC: (none) => yullaw

I have found the problem with other android smartphones. The user has not the perms to read the device which is mounted.

A solution is to use MCC -> Scurity -> Configure... -> parameters -> permissions -> add a rule (example for user pierre) :

/usr/bin/mount  	root 	root 	755  (force)	pierre:acl

It can be easier to do: 
echo -e "/usr/bin/mount\troot\troot\t755\tforce\tpierre:acl" >> /etc/security/msec/perms.conf

I don't know if it is the best solution, but it works fine.

This kind of bug is enough to lose a great number of mageia users.

CC: (none) => jarillon

This bug must not be linked to dolphin but related to installation of Mageia.

The workaround (Comment 13) has been tested with Mageia 5, 2 PC and 2 smartphones.

(In reply to Pierre Jarillon from comment #13)
> This kind of bug is enough to lose a great number of mageia users.

No, it's not specific to Mageia (although some distros have packaged jmtpfs), and it's not about permissions, it's just that mtpfs is broken.

> No, it's not specific to Mageia (although some distros have packaged jmtpfs), and it's not about permissions, it's just that mtpfs is broken.

I am sure you are true but what mageia users need is a working solution. If not, they are disappointed, they return to Windows and say that Linux is only for geeks.

It seems to be the same than
https://bugs.mageia.org/show_bug.cgi?id=7638 ?

(In reply to Pierre Jarillon from comment #16)
> I am sure you are true but what mageia users need is a working solution. If
> not, they are disappointed, they return to Windows and say that Linux is
> only for geeks.

The maintainers do their best, there is no need to use this kind of argument to obtain anything. I had this problem for several years, I just moved the content from the phone to the card and I used a 6 in 1 card reader as a workaround.

CC: (none) => gouessej

(In reply to Julien Gouesse from comment #18)
> (In reply to Pierre Jarillon from comment #16)
> > I am sure you are true but what mageia users need is a working solution. If
> > not, they are disappointed, they return to Windows and say that Linux is
> > only for geeks.
> 
> The maintainers do their best, there is no need to use this kind of argument
> to obtain anything. I had this problem for several years, I just moved the
> content from the phone to the card and I used a 6 in 1 card reader as a
> workaround.

Exactly, and honestly, even when you get it working (like with jmtpfs), MTP is still absolutely horrible.  It does not allow random access or seeking in files or transfer of metadata-only, so for instance, if you want to sync a directory through MTP, you have to retransfer everything every time.  It's a really slow, horrible, crappy, badly designed and implemented protocol.  So, because of this, people have found other solutions that work a lot better, like installing an SSH server on their phone and using scp or sftp, or using things like KDE connect that can transfer data over a LAN connection.

d=10571

--- Comment #19 from David Walser <luigiwalser@yahoo.com> ---
(In reply to Julien Gouesse from comment #18)
> (In reply to Pierre Jarillon from comment #16)
> > I am sure you are true but what mageia users need is a working solution. If
> > not, they are disappointed, they return to Windows and say that Linux is
> > only for geeks.
> 
> The maintainers do their best, there is no need to use this kind of argument
> to obtain anything. I had this problem for several years, I just moved the
> content from the phone to the card and I used a 6 in 1 card reader as a
> workaround.

Exactly, and honestly, even when you get it working (like with jmtpfs), MTP is
still absolutely horrible.  It does not allow random access or seeking in files
or transfer of metadata-only, so for instance, if you want to sync a directory
through MTP, you have to retransfer everything every time.  It's a really slow,
horrible, crappy, badly designed and implemented protocol.  So, because of
this, people have found other solutions that work a lot better, like installing
an SSH server on their phone and using scp or sftp, or using things like KDE
connect that can transfer data over a LAN connection.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Thanks very much for your reply. Now I can understand...
But when users want to see their photos, they must find a solution. It is not always possible to remove the card from the smartphone.

As we don't expect a quick good solution, we have to offer a set of workarounds to make the copy of pictures possible and the Mageia users will be happy.

If there is a slot to insert a microSD card, I don't see how it would be impossible to remove it from the device.

I don't see what you mean as it works for me. I'm going to upload a screen capture.

Created attachment 6976 [details]
MTP working :)

I can't see the files in the phone, I can only see those in the card and the transfers don't seem to work.

Connecting to my phone seems to work (however crappy the MTP protocol is), but maybe it depends on the phone. What's the status of this bug in current cauldron?

Closing, please reopen if still valid.

Status: NEW => RESOLVED
CC: (none) => mageia
Resolution: (none) => OLD