[kde] [Bug 489511] New: Using KDE Connect - cannot open android phone folders in Dolphin on Kubutntu
Jaz-z
bugzilla_noreply at kde.org
Sun Jun 30 19:40:51 BST 2024
https://bugs.kde.org/show_bug.cgi?id=489511
Bug ID: 489511
Summary: Using KDE Connect - cannot open android phone folders
in Dolphin on Kubutntu
Classification: I don't know
Product: kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: shr at getgoogleoff.me
Target Milestone: ---
SUMMARY
Previously KDE connect allowed opening of phone folders in dolphin on desktop
with Murena 2 android phone.
Now phone folder in Dolphin shows a lock on it and does not open.
Desktop Error notification:
" Error when accessing filesystem. sshfs finished with exit code 1 "
This is probably due to updates either in e/os or on Kubuntu;
KDE connect folder share function is working on an old Samsung phone android
version 5.1
STEPS TO REPRODUCE
1. Open KDE and request pairing with phone
2. accept pairing on phone
3. open dolphin to access phone folder
OBSERVED RESULT
Opening Phone folder in dolphin shows a folder icon named internal shared
storage with a lock on it.
Error notification goes in to loop and produces endless notifications while the
phone tab is open in dolphin.
Error notification states: " Error when accessing filesystem. sshfs finished
with exit code 1 "
When dolphin tab is closed, notifications stop.
EXPECTED RESULT
Show phone folders and documents in dolphin.
SOFTWARE/OS VERSIONS
Desktop:
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-112-generic (64-bit)
Android phone: Murena 2:
/e/OS version: 2.1-t-20240603406607-stable-two
on Desktop
KDE Connect version: 21.12.3-0ubuntu1
source: manual:ubuntu-jammy-universe (ubuntu 22.04.4 LTS)
on Murena 2
KDE Connect version: 1.31.1
ADDITIONAL INFORMATION
also reported: https://gitlab.e.foundation/e/backlog/-/issues/8078
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list