Reproducible: Always Steps to Reproduce: 1. open file from network location via dolphin in other program i.e. Libre Office 2. program does not realize, that file is opened from network ressource, since dolphin creates a local copy with random name under ub directory of /tmp, which is than handed over to application program 3. when closing program (e.g. Libre Office) files get's saved back into /tmp subdirectory from where dolphin tries to synchronize it with network folder 4. since network folder is disconnected, dolphin just returns a timeout message 5. since file under /tmp can't get synchronized but is also no longer opened by any program it just get's discarded by dolphin (in case there were several tmp-files, they will all get cleared at latest with next reboot, because with "modern" (aka current) linux versions the whole /tmp directory get's cleared with every reboot) Actual Results: file lost Expected Results: file preserved e.g. in ~/.tmp or ~/kde/tmp directory at least as temporary copy which can be recovered it used to work flawlessly already more than ten years ago. ;(
Thanks for the bug report! To my knowledge, the creation of the local copy of the file is handled by KIO -> I'll reassign this report.
I just looked at the code that handles this and the temporary file created is not going to be deleted when the application does not exit properly or the process of updating the remote server fails ; so something else must be going on here. I can try to replicate this problem but I need to know which protocol you used to connect to the remote server (ftp, sftp, smb) and what kind of file you opened in LibreOffice?
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!
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!