Bug 2188645

Summary: [abrt] gnome-shell: clutter_stage_get_device_coords(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: meyo
Component: gnome-shellAssignee: GNOME SIG Unassigned <gnome-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: adscvr, fmuellner, gnome-sig, jadahl, meyo, otaylor, philip.wyett, redhat, yann
Target Milestone: ---Keywords: AutomationTriaged
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e1e9d82f4f7b2b3ecff7d2b29d2b9358cc092c9
Whiteboard: abrt_hash:23fa33cce0efaa687d6b84e9970db9a748f72b00;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-21 14:41:07 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: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: exploitable
none
File: var_log_messages
none
File: backtrace none

Description meyo 2023-04-21 13:59:56 UTC
Description of problem:
this results in one monitor randomly freezing. no more mouse movement, frame just does not change anymore. This bug report should be caused by me restarting gdm to fix it

can be fixed by restarting gdm, or changing display layout via gnome settings > display -  on a monitor that is not frozen.

Version-Release number of selected component:
gnome-shell-44.0-4.fc38

Additional info:
reporter:       libreport-2.17.9
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=2f8e0e7b4c1147988bd0eabdec826050;i=41073e;b=a492b89752964005a7f716a277432c8e;m=4c6ba899;t=5f9d8d31fd9eb;x=3df4da993f643718
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.2.11-300.fc38.x86_64
package:        gnome-shell-44.0-4.fc38
runlevel:       N 5
dso_list:       /usr/bin/gnome-shell gnome-shell-44.0-4.fc38.x86_64 (Fedora Project) 1681974494
backtrace_rating: 4
crash_function: clutter_stage_get_device_coords

Truncated backtrace:
Thread no. 1 (50 frames)
 #0 clutter_stage_get_device_coords at ../clutter/clutter/clutter-stage.c:3374
 #1 clutter_stage_repick_device at ../clutter/clutter/clutter-stage.c:3775
 #2 ffi_call_unix64 at ../src/x86/unix64.S:104
 #3 ffi_call_int at ../src/x86/ffi64.c:673
 #4 ffi_call at ../src/x86/ffi64.c:710
 #5 Gjs::Function::invoke at ../gi/function.cpp:995
 #6 Gjs::Function::call at ../gi/function.cpp:1175
 #7 CallJSNative at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:420
 #8 js::InternalCallOrConstruct at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:493
 #9 InternalCall at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:574
 #10 js::CallFromStack at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:578
 #11 Interpret at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:3314
 #12 js::RunScript at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:389
 #13 js::InternalCallOrConstruct at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:539
 #14 InternalCall at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:574
 #15 js::Call at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:605
 #16 JS_CallFunctionValue at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/CallAndConstruct.cpp:53
 #17 JS::Call at /usr/include/mozjs-102/js/CallAndConstruct.h:92
 #18 Gjs::Closure::invoke at ../gi/closure.cpp:184
 #19 Gjs::Closure::marshal at /usr/include/mozjs-102/js/RootingAPI.h:613
 #21 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3802
 #24 transition_closure_free at ../clutter/clutter/clutter-actor.c:16966
 #25 iter_remove_or_steal at ../glib/ghash.c:1237
 #26 g_hash_table_iter_remove at ../glib/ghash.c:1273
 #27 _clutter_actor_stop_transitions at ../clutter/clutter/clutter-actor.c:4061
 #28 clear_stage_views_cb at ../clutter/clutter/clutter-actor.c:15265
 #29 _clutter_actor_traverse_depth at ../clutter/clutter/clutter-actor.c:15914
 #31 _clutter_actor_traverse at ../clutter/clutter/clutter-actor.c:15975
 #33 clutter_actor_clear_stage_views_recursive at ../clutter/clutter/clutter-actor.c:15295
 #34 clutter_actor_remove_child_internal at ../clutter/clutter/clutter-actor.c:4209
 #35 ffi_call_unix64 at ../src/x86/unix64.S:104
 #36 ffi_call_int at ../src/x86/ffi64.c:673
 #37 ffi_call at ../src/x86/ffi64.c:710
 #38 Gjs::Function::invoke at ../gi/function.cpp:995
 #39 Gjs::Function::call at ../gi/function.cpp:1175
 #40 CallJSNative at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:420
 #41 js::InternalCallOrConstruct at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:493
 #42 InternalCall at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:574
 #43 js::CallFromStack at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:578
 #44 Interpret at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:3314
 #45 js::RunScript at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:389
 #46 js::InternalCallOrConstruct at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:539
 #47 InternalCall at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:574
 #48 js::Call at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/Interpreter.cpp:605
 #49 JS_CallFunctionValue at /usr/src/debug/mozjs102-102.9.0-1.fc38.x86_64/vm/CallAndConstruct.cpp:53
 #50 JS::Call at /usr/include/mozjs-102/js/CallAndConstruct.h:92
 #51 Gjs::Closure::invoke at ../gi/closure.cpp:184
 #52 Gjs::Closure::marshal at /usr/include/mozjs-102/js/RootingAPI.h:613
 #54 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3802
 #57 _shell_global_notify_shutdown at ../src/shell-global.c:1916

Comment 1 meyo 2023-04-21 14:00:00 UTC
Created attachment 1958807 [details]
File: proc_pid_status

Comment 2 meyo 2023-04-21 14:00:01 UTC
Created attachment 1958808 [details]
File: maps

Comment 3 meyo 2023-04-21 14:00:02 UTC
Created attachment 1958809 [details]
File: limits

Comment 4 meyo 2023-04-21 14:00:03 UTC
Created attachment 1958810 [details]
File: environ

Comment 5 meyo 2023-04-21 14:00:05 UTC
Created attachment 1958811 [details]
File: open_fds

Comment 6 meyo 2023-04-21 14:00:07 UTC
Created attachment 1958812 [details]
File: mountinfo

Comment 7 meyo 2023-04-21 14:00:08 UTC
Created attachment 1958813 [details]
File: os_info

Comment 8 meyo 2023-04-21 14:00:10 UTC
Created attachment 1958814 [details]
File: cpuinfo

Comment 9 meyo 2023-04-21 14:00:12 UTC
Created attachment 1958815 [details]
File: core_backtrace

Comment 10 meyo 2023-04-21 14:00:13 UTC
Created attachment 1958816 [details]
File: exploitable

Comment 11 meyo 2023-04-21 14:00:14 UTC
Created attachment 1958817 [details]
File: var_log_messages

Comment 12 meyo 2023-04-21 14:00:16 UTC
Created attachment 1958818 [details]
File: backtrace

Comment 13 Charlie Bergren 2023-04-22 22:49:45 UTC
My older XPS 13 9350 has been unsuccesful since later F37 updates in waking from sleep.


reporter:       libreport-2.17.9
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=20f02611496944eebb45d574f1a449dd;i=c1a2;b=e03896197c1c4558bbe2abededf94eda;m=4e27234d;t=5f9f4561b10c7;x=18e37cbcad9d7f92
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.2.11-300.fc38.x86_64
package:        gnome-shell-44.0-4.fc38
runlevel:       N 5
dso_list:       /usr/bin/gnome-shell gnome-shell-44.0-4.fc38.x86_64 (Fedora Project) 1682195818
backtrace_rating: 4
crash_function: clutter_stage_get_device_coords
comment:        My older XPS 13 9350 has been unsuccesful since later F37 updates in waking from sleep.

Comment 14 pwbcommerce 2023-05-05 21:57:57 UTC
Logging into my environment.


reporter:       libreport-2.17.9
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=b6bba940fa474bf38255d52a1c039f1d;i=3c2eb5;b=60526b08c438464fb7c2f6b4ddeb0ecf;m=1936024e;t=5faf95886d0b0;x=c1ce5ab8abf3a23
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.2.14-300.fc38.x86_64
package:        gnome-shell-44.1-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: clutter_stage_get_device_coords
comment:        Logging into my environment.

Comment 15 sreilly24@protonmail.com 2023-05-21 01:32:49 UTC
just restarted my computer


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=3595e83368f544ab9c0d963d4fd77c81;i=20d916;b=cd9542b12b584896bd264b998e48252c;m=cebe8107;t=5fc2a0cc2ee38;x=7c66ee5e4717ddde
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
rootdir:        /
uid:            1000
kernel:         6.2.15-300.fc38.x86_64
package:        gnome-shell-44.1-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: clutter_stage_get_device_coords
comment:        just restarted my computer

Comment 16 pwbcommerce 2023-05-29 03:26:39 UTC
Logging in, switching from X11 to Wayland.


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=b6bba940fa474bf38255d52a1c039f1d;i=3f5d10;b=6c3b0aa0b24d4886b3834980eff94072;m=d3b76115;t=5fcb8e54fde94;x=7c984a334058f322
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.2.15-300.fc38.x86_64
package:        gnome-shell-44.1-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: clutter_stage_get_device_coords
comment:        Logging in, switching from X11 to Wayland.

Comment 17 Sam J. 2023-06-22 07:17:15 UTC
Happened when pressing the windows key. The amount of crashes on Fedora 28 has already been reduced by a lot, still it happens ~1/100.


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=c2a168449c6947d2b3cdc94e8d616571;i=1423c3;b=9aba3f44ca2245a0bac548365654e5d1;m=8ef1e794;t=5fe908dc59f4a;x=849bae2b7278b8ee
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.3.5-200.fc38.x86_64
package:        gnome-shell-44.1-1.fc38
runlevel:       N 5
dso_list:       /usr/bin/gnome-shell gnome-shell-44.1-1.fc38.x86_64 (Fedora Project) 1686058117
backtrace_rating: 4
crash_function: clutter_stage_get_device_coords
comment:        Happened when pressing the windows key. The amount of crashes on Fedora 28 has already been reduced by a lot, still it happens ~1/100.

Comment 18 denis.revin 2023-06-29 14:39:51 UTC
Just started the wayland gnome session after installed NVIDIA drivers from RPMFusion


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=4614715d3f9a46f3b28ca66f52258791;i=1819cd;b=f5a43208a3e840c3a9505d5641d69f07;m=635037b;t=5ff45789b23c7;x=cd57a8c1f426c280
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.3.8-200.fc38.x86_64
package:        gnome-shell-44.2-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: clutter_stage_get_device_coords
comment:        Just started the wayland gnome session after installed NVIDIA drivers from RPMFusion

Comment 19 Peter Larsen 2023-08-03 14:36:30 UTC
Logged out and or logged in. Just running a browser when logging out - cannot pinpoint activity that caused the failure. 


reporter:       libreport-2.17.11
crash_function: clutter_stage_get_device_coords
cgroup:         0::/user.slice/user-1601400001.slice/user/session.slice/org.gnome.Shell
runlevel:       N 5
journald_cursor: s=0919bf1d997742f1843efc01e2ae6ca5;i=210a4c8;b=3f0095ddbb45479ab6b534339a95afd3;m=4e616ec2;t=60205889ef827;x=319a4b682698a14a
reason:         gnome-shell killed by SIGSEGV
package:        gnome-shell-44.3-1.fc38
cmdline:        /usr/bin/gnome-shell
backtrace_rating: 4
comment:        Logged out and or logged in. Just running a browser when logging out - cannot pinpoint activity that caused the failure. 
type:           CCpp
kernel:         6.4.7-200.fc38.x86_64
dso_list:       /usr/bin/gnome-shell gnome-shell-44.3-1.fc38.x86_64 (Fedora Project) 1689943774
rootdir:        /
executable:     /usr/bin/gnome-shell
uid:            1601400001

Comment 20 Warren Hughes 2023-08-16 21:19:00 UTC
every time I logoff this happens - hard hang, black screen with corrupted gigabyte motherboard boot logo

requires power off to recover


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=023fe81aa9bd416fa8a718243384cf32;i=800d;b=3d808f94b16d444483c92de17b56b5c8;m=9f19547;t=6031070d9a85c;x=a711decb5b8946de
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.4.10-200.fc38.x86_64
package:        gnome-shell-44.3-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: clutter_stage_get_device_coords

Comment 21 sreilly24@protonmail.com 2023-09-05 01:39:51 UTC
I logged out of my gnome session and immediately logged back in. It seemed to occur when I logged in.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=ab62157d39c34ab980f6e49647d94ac1;i=c83078;b=4411b5a2d45746f08a13777df862fbf6;m=398a9d3e1;t=60492a6894a5a;x=3542713e7c431acb
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
rootdir:        /
uid:            1000
kernel:         6.4.13-200.fc38.x86_64
package:        gnome-shell-44.4-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: clutter_stage_get_device_coords
comment:        I logged out of my gnome session and immediately logged back in. It seemed to occur when I logged in.

Comment 22 Jelly Bean 2023-09-12 21:16:28 UTC
I tried using Sway as Window manager for my Fedora Workstation but it didnt work. When I try to login using Login page icon where the Desktop environments can be switched, I selected sway there and it just kept on crashing.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=9a6619c2043f408db3dcca4c2c21d21a;i=7c91d;b=4caf90762a764dccbc2c35d08b819361;m=9a685aa;t=6052f760e689b;x=239307ef90418cd2
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.4.14-200.fc38.x86_64
package:        gnome-shell-44.4-1.fc38
runlevel:       N 5
dso_list:       /usr/bin/gnome-shell gnome-shell-44.4-1.fc38.x86_64 (Fedora Project) 1693207652
backtrace_rating: 4
crash_function: clutter_stage_get_device_coords
comment:        I tried using Sway as Window manager for my Fedora Workstation but it didnt work. When I try to login using Login page icon where the Desktop environments can be switched, I selected sway there and it just kept on crashing.

Comment 23 Fedora Admin user for bugzilla script actions 2023-12-06 08:22:45 UTC
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/.

This issue should only be kept open if it:

1. Relates to Fedora packaging or integration with other Fedora components
2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions

If this issue isn't needed for either of these two reasons, please:

 * create an issue with GNOME
 * add a link to the GNOME issue here
 * close this issue as CLOSED/UPSTREAM

Thank you!

Comment 24 Aoife Moloney 2024-05-07 16:08:53 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
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
'version' of '38'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 38 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 25 Aoife Moloney 2024-05-21 14:41:07 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.