Version-Release number of selected component: file-roller-3.16.4-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: file-roller /tmp/8mbgmpat.zip crash_function: egg_tree_multi_drag_button_release_event executable: /usr/bin/file-roller global_pid: 25110 kernel: 4.2.6-libre.301.fc23.gnu.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 egg_tree_multi_drag_button_release_event at eggtreemultidnd.c:183 #1 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #6 gtk_widget_event_internal at gtkwidget.c:7692 #7 propagate_event_up at gtkmain.c:2517 #8 propagate_event at gtkmain.c:2619 #9 gtk_main_do_event at gtkmain.c:1850 #14 g_main_context_iteration at gmain.c:3901 #15 g_application_run at gapplication.c:2311 Potential duplicate: bug 881979
Created attachment 1107488 [details] File: backtrace
Created attachment 1107489 [details] File: cgroup
Created attachment 1107490 [details] File: core_backtrace
Created attachment 1107491 [details] File: dso_list
Created attachment 1107492 [details] File: environ
Created attachment 1107493 [details] File: exploitable
Created attachment 1107494 [details] File: limits
Created attachment 1107495 [details] File: maps
Created attachment 1107496 [details] File: mountinfo
Created attachment 1107497 [details] File: namespaces
Created attachment 1107498 [details] File: open_fds
Created attachment 1107499 [details] File: proc_pid_status
Created attachment 1107500 [details] File: var_log_messages
Similar problem has been detected: I opened a 800 MiB zip file and was browsing around the file structure. Specifically this file: http://opensource.dell.com/releases/ThinClient/Echo/4.0/sources-echo4.zip reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: file-roller /home/ossman/Downloads/sources-echo4.zip crash_function: egg_tree_multi_drag_button_release_event executable: /usr/bin/file-roller global_pid: 6558 kernel: 4.3.5-300.fc23.x86_64 package: file-roller-3.16.4-1.fc23 reason: file-roller killed by SIGSEGV runlevel: N 5 type: CCpp uid: 210
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.