Bug 405778 - KDEconnect can not connect to the desktop
Summary: KDEconnect can not connect to the desktop
Status: RESOLVED FIXED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 1.3.3
Platform: Debian testing Linux
: NOR major
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-23 10:16 UTC by bluelupo
Modified: 2020-11-22 02:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bluelupo 2019-03-23 10:16:08 UTC
SUMMARY
When I access my smartphone (Oneplus 3T) via KDEconnect in the file manager Dolphin, the following error message appears in German:
"The drive can not be unmounted.
The error message is:
File system of the device can not be integrated."

STEPS TO REPRODUCE
1. Click on the mobile device on the left in the "Devices" window in the file manager
2. Error message as described above in the file window
3. Always reproducible

OBSERVED RESULT
No access to the file system of the Android device

EXPECTED RESULT
Access to the file system of the Android device

SOFTWARE/OS VERSIONS
KDEconnect  : 1.3.3-0xneon+18.04+bionic+build10
Kernel      : 4.18.0-16-generic
Plasma      : 5.15.3.2
Qt          : 5.12.0
KF          : 5.56.1
Distribution: KDE Neon Useredition

ADDITIONAL INFORMATION
Mobil device Hardware   : Oneplus 3T
Mobil device OS         : LineageOS 16.0
Mobil KDEconnect version: 1.12
Comment 1 Erik Duisters 2019-03-24 09:37:04 UTC
Hi,

Can you please try with v1.12.6 of the android app?
Comment 2 bluelupo 2019-03-24 09:53:55 UTC
Hi Erik,
I have the latest version from the F-Droid Appstore installed. This is version 1.12 (11200, 2019-03-10). Version 1.12.6 is already available on the Google Playstore, but I can not access it because I do not use goggle apps on my smartphone.

Do you know when version 1.12.6 will be available in F-Droid?

Greetings
Michael
Comment 3 Bug Janitor Service 2019-04-08 04:33:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2019-04-23 04:33:26 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 5 Dr. Michael Hälsig 2019-08-20 13:51:32 UTC
I observe the same symptoms as described by bluelupo. In addition, when I click in the KDEconnect submenu the icon 'search filesystem of device' I get the the same error message: 'Filesystem cannot be integrated: device does not answer'.  

My current software version:
Debian Testing: KDEconnect 1.3.3-2
Kernel        : 4.19.0-5-amd64
Plasma        : 5.14.5.1

Mobile: Samsung Galaxy S4 LineageOS 14.1
KDEConnect    : 1.12.93
Comment 6 Justin Zobel 2020-11-21 04:38:23 UTC
I've just tested this on the latest KDEconnect and I can't replicate the issue.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 7 bluelupo 2020-11-21 16:04:10 UTC
Hi Justin,

you can be marked as resolved. The error no longer occurs.

Thanks
Michael