Bug 1318056

Summary: [abrt] file-roller: egg_tree_multi_drag_button_release_event(): file-roller killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Giulio 'juliuxpigface' <juliux.pigface>
Component: file-rollerAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: andreas.stoeckel, jfrieben, mclasen, ross, wiesen-edx
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/beffe58491686c19de5e2d9b269de1d19274e01c
Whiteboard: abrt_hash:df0a38ac89ae806bd3d716a175c393e9eb0565fd;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 13:08:03 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 Giulio 'juliuxpigface' 2016-03-15 21:55:30 UTC
Description of problem:
I've tried to open a subdirectory of an archive, with file-roller

Version-Release number of selected component:
file-roller-3.19.90-2.fc24

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        file-roller /home/giulio/Scaricati/linux-4.5.tar.xz
crash_function: egg_tree_multi_drag_button_release_event
executable:     /usr/bin/file-roller
global_pid:     4119
kernel:         4.5.0-0.rc7.git0.2.fc24.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:7704
 #7 propagate_event_up at gtkmain.c:2522
 #8 propagate_event at gtkmain.c:2624
 #9 gtk_main_do_event at gtkmain.c:1855
 #14 g_main_context_iteration at gmain.c:3901
 #15 g_application_run at gapplication.c:2381

Potential duplicate: bug 1292978

Comment 1 Giulio 'juliuxpigface' 2016-03-15 21:55:34 UTC
Created attachment 1136768 [details]
File: backtrace

Comment 2 Giulio 'juliuxpigface' 2016-03-15 21:55:36 UTC
Created attachment 1136769 [details]
File: cgroup

Comment 3 Giulio 'juliuxpigface' 2016-03-15 21:55:37 UTC
Created attachment 1136770 [details]
File: core_backtrace

Comment 4 Giulio 'juliuxpigface' 2016-03-15 21:55:39 UTC
Created attachment 1136771 [details]
File: dso_list

Comment 5 Giulio 'juliuxpigface' 2016-03-15 21:55:41 UTC
Created attachment 1136772 [details]
File: environ

Comment 6 Giulio 'juliuxpigface' 2016-03-15 21:55:42 UTC
Created attachment 1136773 [details]
File: exploitable

Comment 7 Giulio 'juliuxpigface' 2016-03-15 21:55:44 UTC
Created attachment 1136774 [details]
File: limits

Comment 8 Giulio 'juliuxpigface' 2016-03-15 21:55:47 UTC
Created attachment 1136775 [details]
File: maps

Comment 9 Giulio 'juliuxpigface' 2016-03-15 21:55:49 UTC
Created attachment 1136776 [details]
File: mountinfo

Comment 10 Giulio 'juliuxpigface' 2016-03-15 21:55:50 UTC
Created attachment 1136777 [details]
File: namespaces

Comment 11 Giulio 'juliuxpigface' 2016-03-15 21:55:51 UTC
Created attachment 1136778 [details]
File: open_fds

Comment 12 Giulio 'juliuxpigface' 2016-03-15 21:55:53 UTC
Created attachment 1136779 [details]
File: proc_pid_status

Comment 13 Giulio 'juliuxpigface' 2016-03-15 21:55:54 UTC
Created attachment 1136780 [details]
File: var_log_messages

Comment 14 Ross Lagerwall 2016-07-21 08:01:13 UTC
Similar problem has been detected:

I opened an archive (.zip).

I double clicked on a directory entry, which worked,
then double clicked on a directory entry and it immediately segfaulted.

This has happened many times before, including on previous versions of Fedora.

reporter:       libreport-2.7.1
backtrace_rating: 4
cmdline:        file-roller /home/ross/Downloads/xen_169.254.0.1_13Jul2016_11_38_52.tar.bz2
crash_function: egg_tree_multi_drag_button_release_event
executable:     /usr/bin/file-roller
global_pid:     17841
kernel:         4.5.7-300.fc24.x86_64
package:        file-roller-3.20.2-1.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         file-roller killed by SIGSEGV
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Mark 2016-09-09 21:34:44 UTC
*** Bug 1374859 has been marked as a duplicate of this bug. ***

Comment 16 Fedora End Of Life 2017-07-25 20:20:11 UTC
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.

Comment 17 Fedora End Of Life 2017-08-08 13:08:03 UTC
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.