Bug 2144215

Summary: [abrt] gnome-shell: meta_onscreen_native_notify_frame_complete(): gnome-shell killed by SIGABRT
Product: [Fedora] Fedora Reporter: Dave Hatton <bugzilla>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: adscvr, fmuellner, gnome-sig, jadahl, komusubi, otaylor, philip.wyett, ttys3.rust
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fc8c2797b5c4e10e2fe047b5073cc5b49f49e979
Whiteboard: abrt_hash:3952a2c0b23aa50a994b02245d37da02bad91782;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-24 21:46:13 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: core_backtrace
none
File: cpuinfo
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Dave Hatton 2022-11-19 23:14:35 UTC 
Description of problem:
Simple failed after a screen lock

Version-Release number of selected component:
gnome-shell-43.1-3.fc37

Additional info:
reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
crash_function: meta_onscreen_native_notify_frame_complete
dso_list:       /usr/bin/gnome-shell gnome-shell-43.1-3.fc37.x86_64 (Fedora Project) 1668791243
executable:     /usr/bin/gnome-shell
journald_cursor: s=a2053637b17647df80c5c687163b094d;i=1a1b9;b=e4ce5f0510164c1194b6d4256446b65c;m=54730db7d;t=5edd876038a17;x=55e7f4d8b7a71c73
kernel:         6.0.9-300.fc37.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Potential duplicate: bug 2062939
Comment 1 Dave Hatton 2022-11-19 23:14:38 UTC 
Created attachment 1925782 [details]
File: backtrace
Comment 2 Dave Hatton 2022-11-19 23:14:39 UTC 
Created attachment 1925783 [details]
File: core_backtrace
Comment 3 Dave Hatton 2022-11-19 23:14:40 UTC 
Created attachment 1925784 [details]
File: cpuinfo
Comment 4 Dave Hatton 2022-11-19 23:14:42 UTC 
Created attachment 1925785 [details]
File: environ
Comment 5 Dave Hatton 2022-11-19 23:14:43 UTC 
Created attachment 1925786 [details]
File: limits
Comment 6 Dave Hatton 2022-11-19 23:14:44 UTC 
Created attachment 1925787 [details]
File: maps
Comment 7 Dave Hatton 2022-11-19 23:14:45 UTC 
Created attachment 1925788 [details]
File: mountinfo
Comment 8 Dave Hatton 2022-11-19 23:14:46 UTC 
Created attachment 1925789 [details]
File: open_fds
Comment 9 Dave Hatton 2022-11-19 23:14:47 UTC 
Created attachment 1925790 [details]
File: proc_pid_status
Comment 10 Dave Hatton 2022-11-19 23:14:49 UTC 
Created attachment 1925791 [details]
File: var_log_messages
Comment 11 Lieuwe Rooijakkers 2023-01-11 20:31:35 UTC 
Similar problem has been detected:

I switched to tty6 with ctrl-alt-f6 while having a gnome session open.
Then suddenly I was thrown back to (I think tty1) and I saw the GDM login screen and my gnome session was destroyed.

reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
crash_function: meta_onscreen_native_notify_frame_complete
dso_list:       /usr/bin/gnome-shell gnome-shell-43.2-1.fc37.x86_64 (Fedora Project) 1671042440
executable:     /usr/bin/gnome-shell
journald_cursor: s=6c0bcf0b991744378133fdfa8faf9b8e;i=20b437;b=3f2b7f839b384ed28169659f119c9e72;m=b2bbd6663a;t=5f1fffc8ce095;x=263b1d4c421d3135
kernel:         6.0.15-300.fc37.x86_64
package:        gnome-shell-43.2-1.fc37
reason:         gnome-shell killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 12 richards.dustinb 2023-01-17 17:49:21 UTC 
Similar problem has been detected:

Unknown, unfortunately. Computer crashed overnight.

reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
crash_function: meta_onscreen_native_notify_frame_complete
dso_list:       /usr/bin/gnome-shell gnome-shell-43.2-1.fc37.x86_64 (Fedora Project) 1671184825
executable:     /usr/bin/gnome-shell
journald_cursor: s=a1493878cc944b1197f62c815ca1fc82;i=692c;b=1ab6ca146a7a4dd6ba2158351fa42706;m=e6d06539f;t=5f27784040dd4;x=90b96a150224cb54
kernel:         6.1.5-200.fc37.x86_64
package:        gnome-shell-43.2-1.fc37
reason:         gnome-shell killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 ttyS3 2023-02-14 13:48:54 UTC 
*** Bug 2169723 has been marked as a duplicate of this bug. ***
Comment 14 ttyS3 2023-02-24 11:02:00 UTC 
every day happens

```
gnome-shell[422828]: Failed to lock front buffer on /dev/dri/card0: gbm_surface_lock_front_buffer failed
gnome-shell[422828]: Failed to lock front buffer on /dev/dri/card0: gbm_surface_lock_front_buffer failed
gnome-shell[422828]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
gnome-shell[422828]: Page flip discarded: drmModeAtomicCommit: Invalid argument
gnome-shell[422828]: **
gnome-shell[422828]: libmutter:ERROR:../src/backends/native/meta-onscreen-native.c:208:meta_onscreen_native_notify_frame_complete: assertion failed: (!cogl_onscreen_peek_head_frame_info (onscreen))
gnome-shell[422828]: Bail out! libmutter:ERROR:../src/backends/native/meta-onscreen-native.c:208:meta_onscreen_native_notify_frame_complete: assertion failed: (!cogl_onscreen_peek_head_frame_info (onscreen))
gnome-shell[422828]: == Stack trace for context 0x55da85d0f4a0 ==
```
Comment 15 ttyS3 2023-02-24 15:30:50 UTC 

                Stack trace of thread 2988:
                #0  0x00007f73dceafe5c __pthread_kill_implementation (libc.so.6 + 0x8ce5c)
                #1  0x00007f73dce5fa76 raise (libc.so.6 + 0x3ca76)
                #2  0x0000558e213af432 dump_gjs_stack_on_signal_handler (gnome-shell + 0x3432)
                #3  0x00007f73dce5fb20 __restore_rt (libc.so.6 + 0x3cb20)
                #4  0x00007f73dceafe5c __pthread_kill_implementation (libc.so.6 + 0x8ce5c)
                #5  0x00007f73dce5fa76 raise (libc.so.6 + 0x3ca76)
                #6  0x00007f73dce497fc abort (libc.so.6 + 0x267fc)
                #7  0x00007f73ddf01ef8 g_assertion_message.cold (libglib-2.0.so.0 + 0x1fef8)
                #8  0x00007f73ddf628ae g_assertion_message_expr (libglib-2.0.so.0 + 0x808ae)
                #9  0x00007f73dd1859f4 meta_onscreen_native_notify_frame_complete (libmutter-11.so.0 + 0x1859f4)
                #10 0x00007f73dd189059 notify_view_crtc_presented (libmutter-11.so.0 + 0x189059)
                #11 0x00007f73dd17a881 meta_kms_page_flip_data_flipped (libmutter-11.so.0 + 0x17a881)
                #12 0x00007f73dd19ef0d flush_callbacks.isra.0 (libmutter-11.so.0 + 0x19ef0d)
                #13 0x00007f73dd18574d callback_idle.lto_priv.0 (libmutter-11.so.0 + 0x18574d)
                #14 0x00007f73ddf37cb2 g_idle_dispatch (libglib-2.0.so.0 + 0x55cb2)
                #15 0x00007f73ddf38cbf g_main_context_dispatch (libglib-2.0.so.0 + 0x56cbf)
                #16 0x00007f73ddf8e598 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xac598)
                #17 0x00007f73ddf3828f g_main_loop_run (libglib-2.0.so.0 + 0x5628f)
                #18 0x00007f73dd0d0e19 meta_context_run_main_loop (libmutter-11.so.0 + 0xd0e19)
                #19 0x0000558e213aee09 main (gnome-shell + 0x2e09)
                #20 0x00007f73dce4a510 __libc_start_call_main (libc.so.6 + 0x27510)
                #21 0x00007f73dce4a5c9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x275c9)
                #22 0x0000558e213af075 _start (gnome-shell + 0x3075)
Comment 16 Jonas Ådahl 2023-02-24 21:46:13 UTC 

*** This bug has been marked as a duplicate of bug 2148275 ***