The problem is not entirely that files are not created in /tmp, but rather that nothing cleans them up in the event of a crashed or killed process. I also see these files in the current directory as well as tmp and .cache
As these directories are prefixed with a dot, less technical users will probably not see them as the default in the file manager is to hide them. I found over 2.5GB of these files on my system, which means they are also taking up backup space and resources, too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/245716 Title: file-roller puts temporary files in the home dir instead of /tmp Status in File Roller: Confirmed Status in file-roller package in Ubuntu: Triaged Status in file-roller package in Arch Linux: New Bug description: 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy file-roller file-roller: Installed: 3.12.2-0ubuntu1 Candidate: 3.12.2-0ubuntu1 Version table: *** 3.12.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one opens a tarball with file- roller, and without extracting the file, open it (ex. open PDF file with evince) the file-roller utilizes /tmp for this. 4) What happens instead is file-roller utilizes a directory ~/.cache/.fr-* , where * is a changing folder name. If one logs out, or kills the file-roller process via: kill PID the temp files are left behind. To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/245716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
