Doesn't follow XDG_CACHE_HOME

Bug #762306 reported by Diego Algara
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: file-roller

I haven't figured out where does it extract "normal" files, but when I open a big file ~700Mb it uses $HOME instead of $XDG_CACHE_HOME.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in file-roller (Ubuntu):
status: New → Confirmed
Revision history for this message
Lars Behrens (lars-behrens-u) wrote :

file-roller should use $XDG_CACHE_HOME or have an option to select a different directory for caching.

When users' home directories are on a remote machine and mounted via NFS, then file-rollers' habit of creating ~/.fr-* directories, extracting there and moving back the result creates huge i/o-loads.

If $XDG_CACHE_HOME would be used, one could direct ~/.cache to some local directory (which we already did).

If that's not possible maybe there is a possibility to define a different extracting directory, e.g. by start variable or in the menu.

Revision history for this message
Sebastien Bacher (seb128) wrote :

The issue should be reported upstream on https://gitlab.gnome.org/GNOME/file-roller/issues

Changed in file-roller (Ubuntu):
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.