Bug 363947 - kde connect: Could not mount device.
Summary: kde connect: Could not mount device.
Status: RESOLVED NOT A BUG
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
: 363907 364072 364084 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-06-04 16:05 UTC by Gerry
Modified: 2019-03-25 12:53 UTC (History)
17 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerry 2016-06-04 16:05:27 UTC
The exact error I get is: Could not mount device.
The reported error was:
Could not mount device filesystem

KDEconnect allows me all the other option available i.e. ping android, control desktop etc.  Except I cannot click on phone which is listed in places and explore my phone filesystem.  I have in the past been able to do this but noticed today that it does notwork currently for some reason.

Reproducible: Always

Steps to Reproduce:
1.I can pair phone through wifi with the pair button on either phone or desktop
2.I open dolphin file manager to see phone listed as a drive
3.Click on phone and get this message every time

Actual Results:  
Could not mount device.
The reported error was:
Could not mount device filesystem

Expected Results:  
Should open android filesystem to browse phones folders
Comment 1 UncleTB 2016-06-05 06:06:31 UTC
The same here!
- Samsung Galaxy Nexus
- KDE Frameworks 5.18.0
- Qt 5.5.1 (built against 5.5.1)
- The xcb windowing system
Comment 2 Mark Unger 2016-06-06 14:21:13 UTC
I have the same issue:
- Samsung Galaxy Note II
- KDE Frameworks 5.22.0 
- KDE Plasma Version: 5.6.4
- Qt 5.6.0
- Manjaro Operating System 4.6.1
Comment 3 Gauthier 2016-06-07 01:18:50 UTC
Same here:
- Manjaro
- Samsung Galaxy S II
- KDE Frameworks 5.22.0 
- KDE Plasma Version: 5.6.4
- Qt 5.6.0
Comment 4 Gauthier 2016-06-07 01:20:27 UTC
I have removed the config folder ~/.config/kdeconnect and then re-paired my device and stilll the same problem.
Comment 5 Dominik Straub 2016-06-07 18:54:44 UTC
I am having the same problem:

-Kubuntu
-KDE Plasma Version 5.5.5
-Qt 5.5.1
-Motorola Moto X (2013)
Comment 6 Erik Quaeghebeur 2016-06-08 08:03:30 UTC
Did this problem appear after the android app was upgraded to version 1.0?

Duplicate of Bug 363907?
Comment 7 Albert Vaca Cintora 2016-06-08 09:22:36 UTC
*** Bug 364084 has been marked as a duplicate of this bug. ***
Comment 8 Albert Vaca Cintora 2016-06-08 09:22:39 UTC
*** Bug 363907 has been marked as a duplicate of this bug. ***
Comment 9 Albert Vaca Cintora 2016-06-08 09:22:43 UTC
*** Bug 364072 has been marked as a duplicate of this bug. ***
Comment 10 Albert Vaca Cintora 2016-06-08 09:25:28 UTC
To implement this feature we use sshfs, which has made some changes that broke us. The version 1.0 of the desktop client for KDE Connect will fix this.
Comment 11 Philippe ROUBACH 2016-06-08 11:25:54 UTC
with opensuse 13.1 we will never get 1 version because they stop updating kdeconnect desktop for 13.1 at 0.8b for kde4. the following versions are supplied only for plasma 5.

is there a way to get kdeconnect desktop 1 version for opensuse 13.1 and kde4?
Comment 12 Kerr Avon 2016-06-08 11:40:26 UTC
Is there an interrim release date for version 1.0 of the desktop client for KDE Connect or do we have to wait for the next Plasma applications framework release?
Comment 13 Philippe ROUBACH 2016-06-09 10:27:45 UTC
a workaround:

i uninstalled android kdeconnect 1.0 (from playstore) then i installed kdeconnect 0.9g from f-droid repo.
i asked for f-droid not updating the 0.9g.

i can again access to the smartphone file system.
Comment 14 Albert Vaca Cintora 2016-06-09 10:59:44 UTC
What's the desktop version of KDE Connect you are using? That might be key to fixing this bug, and there is no mention about that in any of the comments.
Comment 15 Mark Unger 2016-06-09 11:03:05 UTC
The workaround works. I have kdeconnect-cli 0.9 and the android app with version 0.9g.
Comment 16 Philippe ROUBACH 2016-06-09 11:11:17 UTC
see my bug report
https://bugs.kde.org/show_bug.cgi?id=364084
Comment 17 Albert Vaca Cintora 2016-06-09 11:16:27 UTC
So is this only happening on desktops running 0.8?
Comment 18 Simone Gaiarin 2016-06-09 11:24:53 UTC
I have the same problem and my desktop version is 0.9.g. Android version is 1.0.

Error reported by dolphin:

"Could not mount device.
The reported error was:
Could not mount device filesystem"
Comment 19 Erik Quaeghebeur 2016-06-09 11:30:02 UTC
(In reply to Simone Gaiarin from comment #18)
> I have the same problem and my desktop version is 0.9.g. Android version is
> 1.0.

Same config here. Problem appeared after android app update to 1.0.
Comment 20 Albert Vaca Cintora 2016-06-09 12:37:20 UTC
Can you run kdeconnectd from the console (should be in /usr/lib/kdeconnectd or something like that, make sure to kill the existing process before starting the new one) and tell me if there is any error message in the console when you try to mount the device?
Comment 21 Simone Gaiarin 2016-06-09 13:59:08 UTC
Here:

kdeconnect.core: KdeConnect daemon starting
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: KdeConnect daemon started
"Google Nexus 4" - warning, device uses a different protocol version 6 expected 5
kdeconnect.core: Loaded plugin: "kdeconnect_notifications"
kdeconnect.core: Loaded plugin: "kdeconnect_battery"
kdeconnect.core: Loaded plugin: "kdeconnect_ping"
kdeconnect.plugin.mpris: Mpris addPlayer "org.mpris.MediaPlayer2.vlc" -> "VLC media player"
kdeconnect.core: Loaded plugin: "kdeconnect_mpriscontrol"
kdeconnect.plugin.sftp: add to dolphin
kdeconnect.plugin.sftp: Created device: "Google Nexus 4"
kdeconnect.core: Loaded plugin: "kdeconnect_sftp"
kdeconnect.core: Loaded plugin: "kdeconnect_clipboard"
kdeconnect.core: Loaded plugin: "kdeconnect_share"
kdeconnect.core: Loaded plugin: "kdeconnect_telephony"
kdeconnect.core: Loaded plugin: "kdeconnect_pausemusic"
kdeconnect.core: Loaded plugin: "kdeconnect_mousepad"
kdeconnect.core: Device "Google Nexus 4" status changed. Reachable: true . Paired:  true
kdeconnect.plugin.notification: removeNotification "com.lucid_dreaming.awoken::1"
kdeconnect.plugin.notification: removeNotification "com.splunchy.android.alarmclock::2131623957"
kdeconnect.plugin.notification: removeNotification "com.lucid_dreaming.awoken::1"
kdeconnect.plugin.notification: removeNotification "com.splunchy.android.alarmclock::2131623957"
"Google Nexus 4" - warning, device uses a different protocol version 6 expected 5
"Google Nexus 4" - warning, device uses a different protocol version 6 expected 5
kdeconnect.plugin.sftp: Mount device: "Google Nexus 4"
kdeconnect.plugin.sftp: Created mounter
kdeconnect.plugin.sftp: Starting loop to wait for mount
kdeconnect.plugin.sftp: Timeout: device not responding
kdeconnect.plugin.sftp: Destroy mounter
kdeconnect.plugin.sftp: Unmount QObject(0x0)
Comment 22 Albert Vaca Cintora 2016-06-09 14:10:37 UTC
Pushing an update to the Play Store, that I hope will fix this bug. 

I'm not pushing it to F-Droid yet, because F-Droid only keeps the last 3 APKs, so if I start publishing new versions you won't be able to download 0.9 from there.
Comment 23 Simone Gaiarin 2016-06-09 14:49:41 UTC
I've updated the android app and now it's working flawlessy. I haven't tested  it extensively though.
Comment 24 Mark Unger 2016-06-09 14:53:27 UTC
Yes! It works now with the updated android app! Thank you very much!
Comment 25 Philippe ROUBACH 2016-06-09 15:48:54 UTC
no more pb with android kdeconnect 1 and kde kdeconnect 0.8b
Comment 26 Albert Vaca Cintora 2016-06-09 15:55:44 UTC
Cool, thanks you all :D
Comment 27 Carlos 2016-06-15 11:13:39 UTC
Hi,
I still cant mount the device.

kubuntu 16.04
kdeconnect Version: 0.8-0ubuntu5
Android cli: 1.0.2

Dolphin error:
Internal Error
Please send a full bug report at http://bugs.kde.org
Invalid object path: /modules/kdeconnect/devices/249.94.10.38/sftp

kdeconnectd log:

~$ /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
kdeconnect.core: KdeConnect daemon starting
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: KdeConnect daemon started
kdeconnect.core: Sending onNetworkChange to  1  LinkProviders
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: Sending onNetworkChange to  1  LinkProviders
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: Sending onNetworkChange to  1  LinkProviders
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: "OnePlus" - warning, device uses a different protocol version 6 expected 5
kdeconnect.core: device "OnePlus" not paired, ignoring package "kdeconnect.mpris"
kdeconnect.core: device "OnePlus" not paired, ignoring package "kdeconnect.battery"
kdeconnect.core: device "OnePlus" not paired, ignoring package "kdeconnect.runcommand"
kdeconnect.core: device "OnePlus" not paired, ignoring package "kdeconnect.notification"
kdeconnect.core: device "OnePlus" not paired, ignoring package "kdeconnect.notification"
kdeconnect.core: "OnePlus" - warning, device uses a different protocol version 6 expected 5
kdeconnect.core: "OnePlus" - warning, device uses a different protocol version 6 expected 5
kdeconnect.core: Pair answer
kdeconnect.plugin.sftp: add to dolphin
kdeconnect.plugin.sftp: Created device: "OnePlus"
kdeconnect.plugin.notification: Registered notifications listener for device "OnePlus"
kdeconnect.plugin.notification: removeNotification "0|com.google.android.gm|-1659672058|null|10041"
kdeconnect.plugin.notification: removeNotification "0|com.google.android.gm|-1659672058|null|10041"
kdeconnect.plugin.ping: sendPing: true
kdeconnect.plugin.sftp: Mount device: "OnePlus"
kdeconnect.plugin.sftp: Created mounter
kdeconnect.plugin.sftp: Starting loop to wait for mount
kdeconnect.plugin.sftp: Unmount QObject(0x0)
kdeconnect.plugin.sftp: Starting process:  "sshfs kdeconnect@192.168.1.122:/ /home/m80189/.config/kdeconnect/15f5369c24074e38/kdeconnect_sftp/15f5369c24074e38 -p 1739 -f -o IdentityFile=/home/m80189/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=ssh-dss"
QDBusAbstractAdaptor: Cannot relay signal SftpPlugin::packageReceived(NetworkPackage): Unregistered input type in parameter list: NetworkPackage
kdeconnect.plugin.sftp: Process started
kdeconnect.plugin.sftp: "OnePlus" "Remote filesystem mounted at /home/m80189/.config/kdeconnect/15f5369c24074e38/kdeconnect_sftp/15f5369c24074e38"
kdeconnect.plugin.sftp: stdout: "Warning: Permanently added '[192.168.1.122]:1739' (DSA) to the list of known hosts.\r\n"
Comment 28 Tomasz Chmielewski 2019-03-24 14:25:38 UTC
Please reopen.

I'm not able to browse the filesystem on a Google Pixel 2 phone. Other actions like ringing work fine.

Error reported is: "Failed to mount filesystem: device not responding".


Output from kdeconnect:

$ /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
kdeconnect.core: KdeConnect daemon starting
kdeconnect.core: onStart
kdeconnect.core: KdeConnect daemon started
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
kdeconnect.core: Socket successfully established an SSL connection
kdeconnect.core: It is a known device "google"
kdeconnect.plugin.sftp: add to dolphin
kdeconnect.plugin.sftp: Created device: "google"
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
kdeconnect.core: Socket successfully established an SSL connection
kdeconnect.core: It is a known device "google"
kdeconnect.plugin.sftp: Mount device: "google"
kdeconnect.plugin.sftp: Created mounter
kdeconnect.plugin.sftp: Starting loop to wait for mount
kdeconnect.plugin.sftp: Timeout: device not responding
kdeconnect.plugin.sftp: Destroy mounter
kdeconnect.plugin.sftp: Unmount QObject(0x0)



Running kdeconnect 1.3.3 on Kubuntu 18.10, and the newest kdeconnect version on Android installed from Google Play (as of 2019-Mar-24).

"ss -tpna" output (192.168.1.3 - Google Pixel 2 phone; 192.168.1.5 - Kubuntu 18.10):


# ss -tpna|grep 192.168.1.3
ESTAB       0        0                             [::ffff:192.168.1.5]:48438                                         [::ffff:192.168.1.3]:1716                  users:(("kdeconnectd",pid=13368,fd=21))     



"tcpdump" shows some packets are exchanged on port 1716, but not sure how to debug this further.

The same kdeconnect on Kubuntu browses the files on an ASUS phone just fine.
Comment 29 Erik Duisters 2019-03-25 11:01:13 UTC
Hi Tomasz,

What is the exact version number of kdeconnect on android also what version of Android are you running on your pixel 2?
Comment 30 Tomasz Chmielewski 2019-03-25 11:05:18 UTC
On Android (Google Pixel 2 XL):

- kdeconnect 1.12.6 ("last updated Mar 23, 2019")

- Android 9, security patch level: March 5, 2019
Comment 31 Erik Duisters 2019-03-25 11:38:27 UTC
Did you configure any storage locations for the filesystem expose plugin?

Open the options menu and select Plugin settings. Then click the settings icon to the right of "Filesystem expose" and configure at least 1 storage location (eg "Internal Storage" or "SD card")

Version 1.3.4 of the desktop code which is about to be released will include provide better error message for this situation
Comment 32 Tomasz Chmielewski 2019-03-25 12:40:09 UTC
In the "Settings" menu in kdeconnect on Android, I can see "More settings", which says

  Per-device settings can be found under 'Plugin settings' from within a device.

But where exactly can I find "Plugin settings"?
Comment 33 Tomasz Chmielewski 2019-03-25 12:43:32 UTC
Never mind - found it, it's the device running KDE. The wording could be improved there (and it's not called "plugin settings").

Also - I agree that the error message could be better.

Thanks for your help, accessing files works for me now!