Bug#682561: dolphin: Fail to browse MTP directory
Package: dolphin Version: 4:4.8.4-1 Severity: normal Dear Maintainer, * What led up to the situation? I'm trying to connect my Galaxy Nexus (Android 4.1) and browse some the filesystem. * What exactly did you do (or not do) that was effective (or ineffective)? Plug my phone, after new device is fired, trying to browse it 2 directories appear : - Mass Storage Camera - Samsung Galaxy Nexus/Galaxy S (i9250, Android 4.0 updates@usb:001,006) * What was the outcome of this action? If I try to browse Mass Storage Camera folder : An unknown error 150 is fired (sorry it is in french) : Code d'erreur 150 inconnu Mauvais paramètres Veuillez envoyer un rapport de bogue détaillé à http://bugs.kde.org.; * What outcome did you expect instead? List of available folders ! I have tried with gMTP and MTPfs (fuse module) and it works more or less (lots of freezing, segfault, errors when copying files)... I don't know if it is from kio or libmtp9 or dolphin... Thanks to take care of that trouble. Kind regards Mourad -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dolphin depends on: ii kde-runtime4:4.8.4-1 ii libc6 2.13-33 ii libkcmutils4 4:4.8.4-3 ii libkdecore54:4.8.4-3 ii libkdeui5 4:4.8.4-3 ii libkfile4 4:4.8.4-3 ii libkio54:4.8.4-3 ii libknewstuff3-44:4.8.4-3 ii libkonq5abi1 4:4.8.4-1 ii libkparts4 4:4.8.4-3 ii libnepomuk44:4.8.4-3 ii libnepomukquery4a 4:4.8.4-3 ii libnepomukutils4 4:4.8.4-3 ii libphonon4 4:4.6.0.0-2 ii libqt4-dbus4:4.8.2-1 ii libqtcore4 4:4.8.2-1 ii libqtgui4 4:4.8.2-1 ii libsoprano42.7.6+dfsg.1-1 ii libstdc++6 4.7.1-2 ii libxrender11:0.9.7-1 ii phonon 4:4.6.0.0-2 Versions of packages dolphin recommends: ii ruby4.9 ii ruby1.8 [ruby] 1.8.7.358-4 Versions of packages dolphin suggests: pn kdesdk-dolphin-plugins none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682561: dolphin: Fail to browse MTP directory
Looking at the most recent entry in http://packages.debian.org/changelogs/pool/main/libm/libmtp/current/changelog leads me to think you might have more luck with the libmtp from Unstable. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682561: dolphin: Fail to browse MTP directory
On 23/07/2012 20:09, Scott Kitterman wrote: Looking at the most recent entry in http://packages.debian.org/changelogs/pool/main/libm/libmtp/current/changelog leads me to think you might have more luck with the libmtp from Unstable. I have already seen it ! I Just update it but unfortunatly no significant progress :( Regards Mourad -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682561: dolphin: Fail to browse MTP directory
No need to cc: me on the updates, I get the bug reports. I have a Samsung Galaxy S 3 and I have, eventually, gotten it working on Kubuntu. The path that works for me is (with the phone set to MTP device: camera:/USB PTP Class Camera@usb:/store_00010001/ With it set to PTP device, this path sometimes works: camera:/USB PTP Class Camera@usb:002,015/store_00010001/ The KIO for camera provided by Kamera is, well, not the most elegant code you'll ever see is the kindest way I can put it. That doesn't work every time, sometimes I get a crash. I haven't filed a bug on bugs.kde.org yet, but it's definitely an upstream bug. If I follow the other path: camera:/Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus@usb:002,012/ it never works. Either I will get the same KIO crash (The process for the camera protocol died unexpectedly.) or your error 150. I also ran into a problem at one point of having been a bit too aggressive at disabling services off the phone and I had to re-enable one (I think it was DirectShareManager). I don't know if yours is the same. It seems it's a bit of a mess and I think it's a KDE mess as Kamera is rather unmaintained. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
