Bug 1379319

Summary: [abrt] gnome-shell: _g_log_abort(): gnome-shell killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Jonathan Gazeley <bugzilla>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: fmuellner, marcos, otaylor, vorburger
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7d8ad88db68d30aec95ab20eb5e07c5077a4966c
Whiteboard: abrt_hash:0af24e9c786ae20a2bb9b91afd1a73fde40c2464;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 17:38:33 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: 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 Jonathan Gazeley 2016-09-26 11:16:21 UTC
Version-Release number of selected component:
gnome-shell-3.20.4-1.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 3
cmdline:        /usr/bin/gnome-shell
crash_function: _g_log_abort
executable:     /usr/bin/gnome-shell
global_pid:     4579
kernel:         4.6.4-301.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _g_log_abort at gmessages.c:325
 #9 XIGetClientPointer at XGetCPtr.c:59
 #10 gdk_x11_display_get_default_seat at gdkdisplay-x11.c:2886
 #11 get_pointer_position_gdk at backends/meta-cursor-tracker.c:375
 #12 meta_cursor_tracker_get_pointer at backends/meta-cursor-tracker.c:420
 #13 shell_global_get_pointer at shell-global.c:1448
 #14 shell_global_sync_pointer at shell-global.c:1468
 #15 ffi_call_unix64 at ../src/x86/unix64.S:76
 #16 ffi_call at ../src/x86/ffi64.c:525
 #17 gjs_invoke_c_function at gi/function.cpp:999

Comment 1 Jonathan Gazeley 2016-09-26 11:16:27 UTC
Created attachment 1204796 [details]
File: backtrace

Comment 2 Jonathan Gazeley 2016-09-26 11:16:29 UTC
Created attachment 1204797 [details]
File: cgroup

Comment 3 Jonathan Gazeley 2016-09-26 11:16:30 UTC
Created attachment 1204798 [details]
File: core_backtrace

Comment 4 Jonathan Gazeley 2016-09-26 11:16:32 UTC
Created attachment 1204799 [details]
File: dso_list

Comment 5 Jonathan Gazeley 2016-09-26 11:16:34 UTC
Created attachment 1204800 [details]
File: environ

Comment 6 Jonathan Gazeley 2016-09-26 11:16:35 UTC
Created attachment 1204801 [details]
File: limits

Comment 7 Jonathan Gazeley 2016-09-26 11:16:37 UTC
Created attachment 1204802 [details]
File: maps

Comment 8 Jonathan Gazeley 2016-09-26 11:16:39 UTC
Created attachment 1204803 [details]
File: mountinfo

Comment 9 Jonathan Gazeley 2016-09-26 11:16:40 UTC
Created attachment 1204804 [details]
File: namespaces

Comment 10 Jonathan Gazeley 2016-09-26 11:16:42 UTC
Created attachment 1204805 [details]
File: open_fds

Comment 11 Jonathan Gazeley 2016-09-26 11:16:43 UTC
Created attachment 1204806 [details]
File: proc_pid_status

Comment 12 Jonathan Gazeley 2016-09-26 11:16:45 UTC
Created attachment 1204807 [details]
File: var_log_messages

Comment 13 Marcos R Oliveira 2017-01-11 02:39:40 UTC
*** Bug 1412032 has been marked as a duplicate of this bug. ***

Comment 14 Michael Vorburger 2017-03-31 10:04:30 UTC
Similar problem has been detected:

I was using "Displays" to activate a 3rd connected monitor at the time this crash occured; but not 100% sure it's related.

reporter:       libreport-2.7.2
backtrace_rating: 3
cmdline:        /usr/bin/gnome-shell
crash_function: _g_log_abort
executable:     /usr/bin/gnome-shell
global_pid:     28774
kernel:         4.9.13-101.fc24.x86_64
package:        gnome-shell-3.20.4-3.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         gnome-shell killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Fedora End Of Life 2017-07-25 23:15:07 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 16 Fedora End Of Life 2017-08-08 17:38:33 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.