Bug 106606 - fish:/ kioslave should check for write permissions first
Summary: fish:/ kioslave should check for write permissions first
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2005-06-01 16:37 UTC by Erik Meusel
Modified: 2018-10-29 02:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented 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 Erik Meusel 2005-06-01 16:37:08 UTC 
Version:            (using KDE KDE 3.4.0)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Hi,

when I copy files via kio_fish, konqueror should check for a writable destination location, first. A few minutes ago, I copied a real huge folder with files and subfolders from one location to another via kio_fish. Konqueror started, summed the files and directories up, calculated the transfer size and time, and then it failed, because the destination was not writable. Perhaps this test could be done earlier?


lg
Erik
Comment 1 Nate Graham 2018-04-23 18:37:53 UTC 
Works for me in KDE Frameworks 5.45.
Comment 2 Nate Graham 2018-04-23 18:38:37 UTC 
Actually I missed that this was for fish:/.
Comment 3 Nate Graham 2018-04-23 18:38:44 UTC 
Is this still relevant or applicable with KDE Frameworks 5.45?
Comment 4 Andrew Crouthamel 2018-09-28 03:20:07 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 5 Andrew Crouthamel 2018-10-29 02:19:20 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!