Description of problem: The root of the zip file contained a folder named "." which I tried to extract, and then the app crashed. Version-Release number of selected component: file-roller-3.10.2.1-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: file-roller /home/ariel/com.github.eclipsecolortheme.themes_1.0.0.201207121019.zip crash_function: sanitize_filename executable: /usr/bin/file-roller kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 sanitize_filename at glib-utils.c:1040 #1 _g_path_get_relative_basename_safe at glib-utils.c:1065 #2 _fr_window_ask_overwrite_dialog at fr-window.c:6662 #3 query_info_ready_for_overwrite_dialog_cb at fr-window.c:6603 #4 g_task_return_now at gtask.c:1108 #5 complete_in_idle_cb at gtask.c:1117 #9 g_main_context_iteration at gmain.c:3774 #10 g_application_run at gapplication.c:1635 Potential duplicate: bug 1009633
Created attachment 847952 [details] File: backtrace
Created attachment 847953 [details] File: cgroup
Created attachment 847954 [details] File: core_backtrace
Created attachment 847955 [details] File: dso_list
Created attachment 847956 [details] File: environ
Created attachment 847957 [details] File: exploitable
Created attachment 847958 [details] File: limits
Created attachment 847959 [details] File: maps
Created attachment 847960 [details] File: open_fds
Created attachment 847961 [details] File: proc_pid_status
Created attachment 847962 [details] File: var_log_messages
Another user experienced a similar problem: 1. Pressed Ctrl + A to select all files in the ISO file 2. Dragged file selection to folder to extract reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: file-roller /home/johann/tmp/mso/mso2007.iso crash_function: sanitize_filename executable: /usr/bin/file-roller kernel: 3.14.3-200.fc20.x86_64 package: file-roller-3.10.2.1-1.fc20 reason: file-roller killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: try to extract contents of an .iso (fedora installer) cd iso image. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: file-roller /home/infrastructure/software/linux/fedora/22/Fedora-Workstation-netinst-x86_64-22_Beta_TC7.iso crash_function: sanitize_filename executable: /usr/bin/file-roller kernel: 3.18.9-100.fc20.x86_64 package: file-roller-3.10.2.1-1.fc20 reason: file-roller killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.