Bug 1371177

Summary: [abrt] file-roller: propagate_event(): file-roller killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Michal Schmidt <mschmidt>
Component: file-rollerAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: mclasen, olivier.crete, youssef.m.sourani
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8d7b9619b813d3bd4b15186a9a07bec308872075
Whiteboard: abrt_hash:b2e318c299b469db2f16149f9b4e76968a99a94d;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:23:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Michal Schmidt 2016-08-29 13:47:17 UTC
Description of problem:
Trying to browse into a tar.bz2 contained within a src.rpm.

Version-Release number of selected component:
file-roller-3.21.90-1.fc25

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        file-roller /tmp/mozilla_michich0/kernel-source-4.8.rc3-1.1.gc0d2ef5.src.rpm
crash_function: propagate_event
executable:     /usr/bin/file-roller
global_pid:     7841
kernel:         4.8.0-0.rc3.git2.1.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            501

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 propagate_event at gtkmain.c:2618
 #1 gtk_propagate_event at gtkmain.c:2683
 #2 egg_tree_multi_drag_button_release_event at eggtreemultidnd.c:183
 #3 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
 #8 gtk_widget_event_internal at gtkwidget.c:7729
 #9 propagate_event_up at gtkmain.c:2546
 #10 propagate_event at gtkmain.c:2648
 #11 gtk_main_do_event at gtkmain.c:1879
 #12 _gdk_event_emit at gdkevents.c:73
 #18 gtk_clipboard_wait_for_contents at gtkclipboard.c:1429

Potential duplicate: bug 1017778

Comment 1 Michal Schmidt 2016-08-29 13:47:22 UTC
Created attachment 1195391 [details]
File: backtrace

Comment 2 Michal Schmidt 2016-08-29 13:47:24 UTC
Created attachment 1195392 [details]
File: cgroup

Comment 3 Michal Schmidt 2016-08-29 13:47:26 UTC
Created attachment 1195393 [details]
File: core_backtrace

Comment 4 Michal Schmidt 2016-08-29 13:47:27 UTC
Created attachment 1195394 [details]
File: dso_list

Comment 5 Michal Schmidt 2016-08-29 13:47:29 UTC
Created attachment 1195395 [details]
File: environ

Comment 6 Michal Schmidt 2016-08-29 13:47:30 UTC
Created attachment 1195396 [details]
File: exploitable

Comment 7 Michal Schmidt 2016-08-29 13:47:31 UTC
Created attachment 1195397 [details]
File: limits

Comment 8 Michal Schmidt 2016-08-29 13:47:33 UTC
Created attachment 1195398 [details]
File: maps

Comment 9 Michal Schmidt 2016-08-29 13:47:35 UTC
Created attachment 1195399 [details]
File: mountinfo

Comment 10 Michal Schmidt 2016-08-29 13:47:36 UTC
Created attachment 1195400 [details]
File: namespaces

Comment 11 Michal Schmidt 2016-08-29 13:47:38 UTC
Created attachment 1195401 [details]
File: open_fds

Comment 12 Michal Schmidt 2016-08-29 13:47:39 UTC
Created attachment 1195402 [details]
File: proc_pid_status

Comment 13 Michal Schmidt 2016-08-29 13:47:41 UTC
Created attachment 1195403 [details]
File: var_log_messages

Comment 14 Olivier CrĂȘte 2017-01-12 21:05:14 UTC
Similar problem has been detected:

opening a specific subdirectory inside a tar.gz file by double-clicking

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        file-roller /home/ocrete/Downloads/VCU%20IP%20Package.zip
crash_function: propagate_event
executable:     /usr/bin/file-roller
global_pid:     22123
kernel:         4.8.8-300.fc25.x86_64
package:        file-roller-3.22.2-1.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         file-roller killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            500

Comment 15 Olivier CrĂȘte 2017-01-12 21:05:41 UTC
This looks like a GTK+ bug...

Comment 16 Fedora End Of Life 2017-11-16 14:20:06 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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.

Comment 17 Fedora End Of Life 2017-12-12 10:23:22 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.