Bug 1298884

Summary: [abrt] libreport-gtk: _gtk_gesture_get_pointer_emulating_sequence(): report-gtk killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Robin Green <greenrd>
Component: libreportAssignee: abrt <abrt-devel-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: abrt-devel-list, dry.embdev, dvlasenk, jberan, mhabrnal, michal.toman, mmilata, phelia
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/cba02bc12e11dedbcbd7098bb149cd7fc560dea1
Whiteboard: abrt_hash:7f8d7affebb9421f8dedf046355fec34077eb5e3;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 17:55:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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 Robin Green 2016-01-15 11:08:25 UTC
Description of problem:
I accidentally selected "no" to not download debuginfo when reporting another bug using abrt, and then scrolled down to where it said something about not knowing what to do (no report action defined for bugzilla or something like that) and then abrt crashed.

Version-Release number of selected component:
libreport-gtk-2.6.3-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        report-gtk -- /var/spool/abrt/ccpp-2016-01-15-10:54:08-3693
crash_function: _gtk_gesture_get_pointer_emulating_sequence
executable:     /usr/bin/report-gtk
global_pid:     3179
kernel:         4.3.3-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 _gtk_gesture_get_pointer_emulating_sequence at gtkgesture.c:1796
 #1 _gtk_widget_get_emulating_sequence at gtkwidget.c:4133
 #2 _gtk_widget_set_sequence_state_internal at gtkwidget.c:4195
 #3 event_controller_sequence_state_changed at gtkwidget.c:17098
 #4 ffi_call_unix64 at ../src/x86/unix64.S:76
 #5 ffi_call at ../src/x86/ffi64.c:525

Comment 1 Robin Green 2016-01-15 11:08:33 UTC
Created attachment 1115088 [details]
File: backtrace

Comment 2 Robin Green 2016-01-15 11:08:35 UTC
Created attachment 1115089 [details]
File: cgroup

Comment 3 Robin Green 2016-01-15 11:08:37 UTC
Created attachment 1115090 [details]
File: core_backtrace

Comment 4 Robin Green 2016-01-15 11:08:39 UTC
Created attachment 1115091 [details]
File: dso_list

Comment 5 Robin Green 2016-01-15 11:08:40 UTC
Created attachment 1115092 [details]
File: environ

Comment 6 Robin Green 2016-01-15 11:08:42 UTC
Created attachment 1115093 [details]
File: exploitable

Comment 7 Robin Green 2016-01-15 11:08:44 UTC
Created attachment 1115094 [details]
File: limits

Comment 8 Robin Green 2016-01-15 11:08:46 UTC
Created attachment 1115095 [details]
File: maps

Comment 9 Robin Green 2016-01-15 11:08:48 UTC
Created attachment 1115096 [details]
File: mountinfo

Comment 10 Robin Green 2016-01-15 11:08:49 UTC
Created attachment 1115097 [details]
File: namespaces

Comment 11 Robin Green 2016-01-15 11:08:51 UTC
Created attachment 1115098 [details]
File: open_fds

Comment 12 Robin Green 2016-01-15 11:08:53 UTC
Created attachment 1115099 [details]
File: proc_pid_status

Comment 13 Robin Green 2016-01-15 11:08:55 UTC
Created attachment 1115100 [details]
File: var_log_messages

Comment 14 D.RY 2016-06-24 20:17:34 UTC
Similar problem has been detected:

i dragged or click the report window somehow wrong ..

reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        report-gtk -- /var/spool/abrt/ccpp-2016-06-24-21:51:59-24642
crash_function: _gtk_gesture_get_pointer_emulating_sequence
executable:     /usr/bin/report-gtk
global_pid:     24699
kernel:         4.5.7-200.fc23.i686
package:        libreport-gtk-2.6.4-2.fc23
reason:         report-gtk killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Fedora End Of Life 2016-11-24 14:58:06 UTC
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.

Comment 16 Fedora End Of Life 2016-12-20 17:55:09 UTC
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.