A bug was filed downstream which indicates that the "move" function of Ktorrekt does not work properly on SMB directories: ################################################## Description of problem: Ktorrent offers the option of moving a downloaded set of torrent files to a new location once the download is completed. Although this function works fine on a local drive, it isn't working with SMB / CIFS. Version-Release number of selected component (if applicable): 4.3.1-11.fc20 How reproducible: every time. Steps to Reproduce: 1. Configure ktorrent to move completed torrent downloads to a specified folder. 2. Observe successful move when folder is on local device 3. Observe failure to move when folder is on an SMB/ CIFS share. Actual results: Failure to move files Expected results: Success in moving files Additional info: The failure seems to occur under both of these conditions: 1. when the address of the drive is added to the ktorrent configuration using a network address. example: smb://sharename/path/ 2. When the SMB/CIFS share is mounted locally, so that the drive/folder should appear to be local. This doesn't appear to be a permissions problem -- the same user running ktorrent on the local machine is the same user owning the destination path on the CIFS share. Additionally, the CIFS share is exported with promiscuous permissions (777) which allows any connected user has read/write/execute privileges. Dragging and dropping the files using Dolphin works just fine, it's just that Ktorrent isn't providing similar functionality. ################################################## The further analysis of the reporter does suggest that this is not a problem with the CIFS share, but a problem with Ktorrekt move function itself, it seems to not access CIFS at all.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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!
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!