Bug 446362 - Failed to start sshfs
Summary: Failed to start sshfs
Status: RESOLVED FIXED
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (show other bugs)
Version: unspecified
Platform: Arch Linux Android 8.x
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-02 09:19 UTC by fansi
Modified: 2021-12-12 15:44 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description fansi 2021-12-02 09:19:10 UTC 
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. start kdt connect
2. View your phone files
3. Failed to start sshfs

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Paul Worrall 2021-12-02 09:29:14 UTC 
Does waking-up the phone and unlocking it make any difference?
Comment 2 fansi 2021-12-11 13:48:02 UTC 
(In reply to Paul Worrall from comment #1)
> Does waking-up the phone and unlocking it make any difference?

It has been solved. I haven't downloaded the sshfs package(In reply to Paul Worrall from comment #1)
> Does waking-up the phone and unlocking it make any difference?