GNOME Bugzilla – Bug 561717
cancelling file-roller in mid operation does not kill the process and does not remove temp hidden subdir
Last modified: 2020-11-11 19:14:56 UTC
Please describe the problem: when fileroller is in the process of creating a *.tar.bz2 archive. when the user stops the archiving, the generated hidden subdirectory at the target location is not removed. Because this file is usually hidden, it could end up taking harddrive real-estate. this generated hidden subdirectory should be place in /tmp. Also noticed that when fileroller is terminated by pressing the 'cancel' button, the file-roller process and the bzip2 process is still present. They should be killed. Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
I reported on Launchpad a bug https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/481006 that seems to be similar to this one and the bug status there was set to "triaged", with an upstream link to this bug 561717 here on Bugzilla. I'm not sure whether it was set correctly as the problem I described is a bit different - cancel doesn't work only while adding files or directories to an existing archive, besides, in version 2.28.1 I didn't notice being unable to cancel the process of creating a *.tar.bz2 archive, so maybe a new bug should be reported here?
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use file-roller and if you still see this bug / want this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/file-roller/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (volunteer workforce and time is limited).