Bug 1295832

Summary: [abrt] gjs: gdk_wayland_device_get_focus(): gjs-console killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Petr Schindler <pschindl>
Component: gjsAssignee: Colin Walters <walters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: marcelo.barbosa, marekdolezel, otaylor, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f6a4ff87e1017d8b61339a1f5db65089336a8ad1
Whiteboard: abrt_hash:9cd22580363e19995fc9cec563a00a5cd85ff708;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 12:37:18 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 Petr Schindler 2016-01-05 15:05:27 UTC
Description of problem:
This occured when I clicked on + button in polari and then I tried to select another connection (another network). When I clicked on the selection the polari crashed.

Version-Release number of selected component:
gjs-1.45.3-1.fc24

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/gjs-console /usr/bin/polari --gapplication-service
crash_function: gdk_wayland_device_get_focus
executable:     /usr/bin/gjs-console
global_pid:     3443
kernel:         4.4.0-0.rc6.git1.1.fc24.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gdk_wayland_device_get_focus at gdkdevice-wayland.c:491
 #1 gdk_wayland_seat_grab at gdkdevice-wayland.c:2466
 #2 popup_grab_on_window at gtkmenu.c:1509
 #3 gtk_menu_popup_for_device at gtkmenu.c:1686
 #4 gtk_menu_popup at gtkmenu.c:1838
 #5 gtk_combo_box_menu_popup at gtkcombobox.c:2151
 #6 gtk_combo_box_menu_button_press at gtkcombobox.c:2880
 #7 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
 #12 gtk_widget_event_internal at gtkwidget.c:7821
 #13 propagate_event_up at gtkmain.c:2517

Comment 1 Petr Schindler 2016-01-05 15:05:34 UTC
Created attachment 1111847 [details]
File: backtrace

Comment 2 Petr Schindler 2016-01-05 15:05:35 UTC
Created attachment 1111848 [details]
File: cgroup

Comment 3 Petr Schindler 2016-01-05 15:05:37 UTC
Created attachment 1111849 [details]
File: core_backtrace

Comment 4 Petr Schindler 2016-01-05 15:05:39 UTC
Created attachment 1111851 [details]
File: dso_list

Comment 5 Petr Schindler 2016-01-05 15:05:40 UTC
Created attachment 1111852 [details]
File: environ

Comment 6 Petr Schindler 2016-01-05 15:05:42 UTC
Created attachment 1111853 [details]
File: exploitable

Comment 7 Petr Schindler 2016-01-05 15:05:43 UTC
Created attachment 1111854 [details]
File: limits

Comment 8 Petr Schindler 2016-01-05 15:05:45 UTC
Created attachment 1111855 [details]
File: maps

Comment 9 Petr Schindler 2016-01-05 15:05:47 UTC
Created attachment 1111856 [details]
File: mountinfo

Comment 10 Petr Schindler 2016-01-05 15:05:48 UTC
Created attachment 1111857 [details]
File: namespaces

Comment 11 Petr Schindler 2016-01-05 15:05:50 UTC
Created attachment 1111858 [details]
File: open_fds

Comment 12 Petr Schindler 2016-01-05 15:05:51 UTC
Created attachment 1111859 [details]
File: proc_pid_status

Comment 13 Petr Schindler 2016-01-05 15:05:53 UTC
Created attachment 1111860 [details]
File: var_log_messages

Comment 14 Marek Doležel 2016-01-12 13:54:27 UTC
Should be fixed by gtk3-3.19.6-1.fc24.

Comment 15 Jan Kurik 2016-02-24 14:13:40 UTC
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

Comment 16 Matthias Clasen 2016-03-28 14:31:59 UTC
*** Bug 1296411 has been marked as a duplicate of this bug. ***

Comment 17 Fedora End Of Life 2017-07-25 19:43:18 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 18 Fedora End Of Life 2017-08-08 12:37:18 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.