run file-roller. Create a new archive and write e.g. /tmp/test as filename. It crashes with the following error: (file-roller:6529): GLib-GIO-CRITICAL **: 11:11:25.269: g_file_get_child: assertion '!g_path_is_absolute (name)' failed Segmentation fault (core dumped) Before mga9 this worked perfect.
using relative filenames works... but it is quite common to just enter a full path...
Could you report this issue upstream at https://gitlab.gnome.org/GNOME/file-roller/-/issues ?
CC: (none) => geiger.david68210
grrr. just the next account and bugtracker: "Signing in using your GitHub account without a pre-existing GitLab account is not allowed. Create a GitLab account first, and then connect it to your GitHub account."
I reproduce this easily on a Cauldron system, but I see why it has not surfaced before: On starting file-roller, empty window. Click the schematic menu icon, choose 'New Archive'. The dialogue it pops comprises two fields: - a filename for the archive - a location for that file, default HOME A filename is not a pathname. Clearly the usage of this thing for Marc's example requires: - a filename of 'test' (it adds a suitable suffix) - choose location '/tmp' The crash happens if you give an absolute pathname for the archive file (which makes the following location field redundant) on clicking 'create', regardless of 'location'; although if you were able to specify an absolute pathname for the archive, you would have to choose 'Filesystem' for its location. True, the crash should not happen, rather an error message. As for posting the bug upstream, a search for 'file-roller' issues shows little activity on them... (In reply to Marc Krämer from comment #1) > it is quite common to just enter a full path... Given the file-roller user interface, which clearly separates *filename* from its *location*, this cannot be true for this particular application. For others, perhaps.
CC: (none) => lewyssmithKeywords: (none) => FOR_ERRATA9, UPSTREAM
@Lewis: e.g. in mate almost every file dialog has a chooser for directories, favorites and so on. It always worked, just to write an absolute filename to it. But in any case, you're right - it should not just crash.
CC: (none) => friStatus comment: (none) => To be reported/commented upstream
@Marc If you do persevere with an upstream bug report, please put that URL in this bug URL field. This may have to remain open even though there is nothing we can do about it - until & if upstream fix it. I suppose it could/should be closed 'wontfix' meaning 'cannot fix'; not for us to decide. In Errata it will be found. Assigning to Gnome despite this; no point in it remaining with Bugsquad. CC'ing Olave who has mostly updated file-roller; and Thierry who has also touched it recently. DavidG has already commented. Over to one of you.
Assignee: bugsquad => gnomeCC: lewyssmith => olav, thierry.vignaud
Keywords: FOR_ERRATA9 => IN_ERRATA9