Bug 357013 - crash on copying to ssh FUSE fs
Summary: crash on copying to ssh FUSE fs
Status: RESOLVED WORKSFORME
Alias: None
Product: krusader
Classification: Applications
Component: net-connection (show other bugs)
Version: Git
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Krusader Bugs Distribution List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-12-21 18:47 UTC by Andrew Gaydenko
Modified: 2018-10-29 02:14 UTC (History)
2 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 Andrew Gaydenko 2015-12-21 18:47:25 UTC
After copying a file to ssh FUSE filesystem Krusader shows error that it can not to change file permissions and exits. sshfs 2.5 is in use.

Reproducible: Always
Comment 1 Davide Gianforte 2016-01-10 11:58:55 UTC
Which are the sshfs mount permissions/user? What are local and remote folder permissions/users?

I can't reproduce it, as I use the same user on both machines, but I think it is related to a KIO problem (after the move/copy, it can't change file permissions, leading to a crash).
Comment 2 Andrew Gaydenko 2016-01-10 12:34:44 UTC
644 for file here and 755 for FUSE mounted folder with the same user - as it is mounted with sshfs. Original remote folder belongs to another user (that is having another unix name).

The same operation doesn't result in error with, say, sunrise commander (emacs two panel file manager).

Can it be KIO tries to chown to local user name instead of leaving all intact?
Comment 3 Andrew Crouthamel 2018-09-28 03:18: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 set the bug status 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 Andrew Crouthamel 2018-10-29 02:14:30 UTC
Dear Bug Submitter,

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!