[SOLVED] Hi, how do I connect my Moto G on Slackware?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am completely lost here, I tried a few solutions I've found on Google but I couldn't make it work. Thunar detects a device when I plug it in but when I double click it I get this:
There is no "/etc/fuse.conf" file and, by the way, to solve libmpt reporting the device as unknow I did this.
EDIT: My mtp-detect reports this now
Code:
root@darkstar:~# mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
Device 0 (VID=22b8 and PID=2e82) is a Motorola Moto G (XT1032).
Found 1 device(s):
Motorola: Moto G (XT1032) (22b8:2e82) @ bus 1, dev 5
Attempting to connect device(s)
Android device detected, assigning default bug flags
And now when I try to open it via Thunar I get this
I don't know if that is normal but I can't access any file from it, it says "file format not recognized" but if I copy the archive to my desktop it works. Any clue? Is that normal?
I don't know if that is normal but I can't access any file from it, it says "file format not recognized" but if I copy the archive to my desktop it works. Any clue? Is that normal?
Have you tried Dolphin instead of Thunar? I have a Nexus 5 and a Nexus 7, both work perfectly with MTP and Dolphin. Just tried with Thunar and am getting read errors if I try to access any file. You may need to upgrade to the latest KDE from AlienBob as early versions of kio-mtp were quite iffy.
I don't know if that is normal but I can't access any file from it, it says "file format not recognized" but if I copy the archive to my desktop it works. Any clue? Is that normal?
Now, if you can't access any file, then it is not working correcty! I also have exactly the same problem with Thunar. I get different errors with different file formats and applications, but if I use Dolphin, then I can open any file with its respected application. I also noticed when I copied a file to my desktop using Thunar, then the filename changed.
Now, if you can't access any file, then it is not working correcty! I also have exactly the same problem with Thunar. I get different errors with different file formats and applications, but if I use Dolphin, then I can open any file with its respected application. I also noticed when I copied a file to my desktop using Thunar, then the filename changed.
Oh, well I don't have any KDE package installed here.
EDIT: But I will give Dolphin a try
Last edited by moisespedro; 04-12-2014 at 08:11 AM.
Well, I had it working but I decided to install a custom ROM on it and now I can't mount it. I am running Slackware64 14.1 with the latest Alienbob's KDE
I just want to be able to use it as I was using it before (clicking on it in Dolphin). It is still quite confusing to me how this is handled (udisks? udisks2? udev? I am like what).
moisespedro: I've been maintaining the kdeconnect SlackBuild for about a year now and the latest version works fine for me on KDE 4.14 and my Moto G. After upgrading, you'll need to restart kdeconnect (the easiest way is logging out of KDE and then logging back in again).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.