Bug 194181 - When copying files from another computer in the network, and get a disk full space pop up window, dolphin left the temporary copied files in a persistent fashion at /home/username/.kde4/tmp-hostname, leaving the disk full without letting the user know ab
Summary: When copying files from another computer in the network, and get a disk full ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: SVN
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2009-05-26 18:16 UTC by José Oramas M.
Modified: 2018-10-28 03:18 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description José Oramas M. 2009-05-26 18:16:01 UTC
Version:           dolphin version 1.2.80 installed on 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 126" openSUSE (using Devel)
Compiler:          gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) 
OS:                Linux
Installed from:    Compiled sources


KDE Version:4.2.86

Steps to reproduce the bug

1- Have your home/root partition with low space

2- Connect to another computer in the network using dolphin with smb protocol

3- Copy from the remote computer to your computer a file with more space than the one available at your home/root partition.

4- A low disk space pop up window will appear

5- Delete the amount of the file that was successfully copied on the target directory

6- If you free some more space (still not enough) from the target  directory and try to do the copy operation again, the full disk pop up will appear again.

7- Go to /home/username/.kde4/tmp-hostname the copied files are still there (I found there like 5GB of useless .part files from dolphin)
Comment 1 José Oramas M. 2009-05-26 18:19:20 UTC
Good luck with it !!!

thanks for the hard work and such a good desktop environment
Comment 2 José Oramas M. 2009-05-26 21:05:27 UTC
Brief Description: (it didn't appeared as i expected)

When copying files from another computer in the network, and get a disk full space pop up window, dolphin left the temporary copied files in a persistent fashion at /home/username/.kde4/tmp-hostname, leaving the disk full without letting the user know about it
Comment 3 Pierre Buard 2009-08-15 23:30:37 UTC
Version:           dolphin version 1.3 installed on KDE 4.3.0
OS:                Arch Linux
Installed from:    Arch Linux repositories

I can confirm this except that it happens on my small /tmp partition (i.e. /tmp/kde-user). Here are the outputs of 'df -h' during the transfer of a 300 odd megabytes file:

At the beginning of the transfer:
/dev/sda6             942M  136M  759M  16% /tmp      

While the transfer was at ~50%, it peaked at:
/dev/sda6             942M  895M   40K 100% /tmp

The situation is the same after copying the file. A closer examination reveals that the user kde tmp folder is filled with dolphin*.tmp and dolphin*.tmp.part.

After clearing them manually ('rm -f dolphin*'):
/dev/sda6             942M   48M  847M   6% /tmp
Comment 4 FiNeX 2009-11-07 10:31:18 UTC
I've had a similar issue using KDE 4.3.3:
I was copying some big files from a smb share. Dolphin leaved a .part copy on my /tmp/kde-<username> directory. Plasma crashed, and I've had to CTRL+ALT+CANC (!!!) for the logout dialog :-p

Logging in again stopped on the third icon of the splash screen, clicking with the mouse the splash disappeared and a "disk full" warning has appeared (it is another bug already reported: warning should be on top of the splash screen). So I've switched to /tmp and I've found the .part of the file I were copying and two other big files (~2Gb each) which filled my / partition.

I don't understand why a .part copy should be write on /tmp... could it be related to the video thumbnail preview? (It was all video files).
Comment 5 FiNeX 2009-11-07 10:38:11 UTC
Just for reference: the "disk full" message is bug# 205630 .
Comment 6 FiNeX 2009-11-08 15:51:12 UTC
I've experienced this bug again. It happens with thumbnail actived. the thumbnail process probably create the files on /tmp/kde-<username> for creating the thumbnail of the video file.

The problem is that it continues to create files probably because the destination file size changes (it is written, so the file grows until the copy/move process is not finished).

I've found on /tmp/kde-<username> the video duplicated in a lot of partial files, one with the first 5MB, another a bit bigger, 50M, another 100M, another 400M and another 2Gb... all relative to the same file (the file sizes are only examples, I've already deleted them).
Comment 7 Dennis Gnad 2010-09-30 20:56:01 UTC
I also have this, for me with /tmp, when copying files from some sftp:/ location to something local.

Some facts about this bug:

I have my storage mounted separately, so I copy the data to /mnt/storage - but anyway, Dolphin uses /tmp to store temporary data - this is unnecessary I/O from one disk to another if one has no tmpfs on /tmp.

The fun thing is, Dolphin puts data in /tmp until I have no more available space, but it DOES GO ON COPYING with SUCCESS! So /tmp is just used as a (uneccessary?) buffer?

Dolphin makes another .part file at the location I copy to (/mnt/storage), so I wonder why the extra other temporary file is needed in root, especially when Dolphin can still keep on copying if there is no space left on the device anymore?

Thanks for solving this!

KDE 4.4.5
Dolphin 1.4
Comment 8 Dawit Alemayehu 2013-06-16 22:39:03 UTC
I cannot reproduce this with KDE v4.10.3. Does anyone here still have this problem with the latest version?
Comment 9 Andrew Crouthamel 2018-09-28 02:27:18 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 10 Andrew Crouthamel 2018-10-28 03:18:51 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!