Version-Release number of selected component: file-roller-3.16.4-1.fc24 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: file-roller /home/admin/Pulpit/recup_dir.7/f4202424_aus.zip crash_function: g_type_check_instance_cast executable: /usr/bin/file-roller global_pid: 16605 kernel: 4.3.0-0.rc0.git14.1.fc24.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 g_type_check_instance_cast at gtype.c:4060 #1 send_delete_event at gtkwindow.c:1314 #6 g_main_context_iteration at gmain.c:3901 #7 g_application_run at gapplication.c:2311
Created attachment 1073947 [details] File: backtrace
Created attachment 1073948 [details] File: cgroup
Created attachment 1073949 [details] File: core_backtrace
Created attachment 1073950 [details] File: dso_list
Created attachment 1073951 [details] File: environ
Created attachment 1073952 [details] File: exploitable
Created attachment 1073953 [details] File: limits
Created attachment 1073954 [details] File: maps
Created attachment 1073955 [details] File: mountinfo
Created attachment 1073956 [details] File: namespaces
Created attachment 1073957 [details] File: open_fds
Created attachment 1073958 [details] File: proc_pid_status
Created attachment 1073959 [details] File: var_log_messages
Another user experienced a similar problem: Description of the problem: I'm running Fedora 24 Rawhide (Xfce). file-roller crashes when closing it from the title bar (the "X" button). How reproducible: Always Steps to reproduce: 1. Open an archive with file-roller (in my case, it was a version of Joomla) 2. Close file-roller from the appropriate button of the title bar Actual behavior: 1. The window seems to freeze and remains opened. 2. Closing the software with a right click on Xfce's panel works. 3. However, abrt catches the crash. Expected crash: 1/2: Both closing methods should work. 3. No crashes should occur reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: file-roller /home/giulio/Programmazione/crashdiet/requirements/Joomla_3.4.5_ita-Stable.zip crash_function: g_type_check_instance_cast executable: /usr/bin/file-roller global_pid: 6291 kernel: 4.4.0-0.rc8.git3.1.fc24.i686+PAE package: file-roller-3.16.4-1.fc24 reason: file-roller killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.