File Roller temp files and directories are created in non-optimal place
Bug #883628 reported by
Bob Bib
This bug report is a duplicate of:
Bug #245716: file-roller puts temporary files in the home dir instead of /tmp.
Edit
Remove
This bug affects 10 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| File Roller |
New
|
Medium
|
|||
| file-roller (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
File Roller (including the latest version, 3.2.1) uses the ~/.cache directory for its temporary files directories, e. g.:
~/.cache/.fr-a12bc3
It creates these temporary folders with files when a user looks through the archive and double-clicks on any file inside to view it.
If File Roller exits unexpectedly, these temp files can only be removed manually.
As it can be learned from bug #245716, some times ago File Roller was even more ugly and created its temp directories directly in user home directory.
It would be much more effective to use /tmp directory for ALL the temp files and folders for two reasons:
1) /tmp directory gets cleaned on every reboot;
2) some people use tmpfs for /tmp directory, so it can be much faster.
| description: | updated |
| summary: |
- File Roller temp directory is not optimal + File Roller temp directories are not optimal |
| description: | updated |
| description: | updated |
| description: | updated |
| summary: |
- File Roller temp directories are not optimal + File Roller temp directories are created in not optimal place |
| summary: |
- File Roller temp directories are created in not optimal place + File Roller temp files and directories are created in non-optimal place |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in file-roller (Ubuntu): | |
| status: | New → Confirmed |
| Changed in file-roller: | |
| importance: | Unknown → Medium |
| status: | Unknown → New |
| Changed in file-roller (Ubuntu): | |
| importance: | Undecided → Low |
| status: | Confirmed → Triaged |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.