Version-Release number of selected component: gnome-shell-45.0-1.fc39 Additional info: reporter: libreport-2.17.11 cmdline: /usr/bin/gnome-shell type: CCpp cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell crash_function: meta_kms_impl_device_hold_fd package: gnome-shell-45.0-1.fc39 rootdir: / runlevel: N 5 reason: gnome-shell killed by SIGABRT dso_list: /usr/bin/gnome-shell gnome-shell-45.0-1.fc39.x86_64 (Fedora Project) 1695667781 uid: 1000 kernel: 6.5.5-300.fc39.x86_64 journald_cursor: s=4b8fdc72259943cfb6c2b367ede33f99;i=26b9bb;b=46665d5727044212a15a0ad9b4520319;m=926c3f93;t=606a5373a1f5f;x=d0a32bce47b1e86f backtrace_rating: 4 executable: /usr/bin/gnome-shell Truncated backtrace: Thread no. 0 (15 frames) #11 meta_kms_impl_device_hold_fd at ../src/backends/native/meta-kms-impl-device.c:1698 #12 meta_kms_update_realize at ../src/backends/native/meta-kms-update.c:1077 #13 maybe_update_cursor_plane.constprop.0 at ../src/backends/native/meta-kms-cursor-manager.c:365 #14 update_filter_cb at ../src/backends/native/meta-kms-cursor-manager.c:496 #15 meta_kms_impl_filter_update at ../src/backends/native/meta-kms-impl.c:130 #16 do_process at ../src/backends/native/meta-kms-impl-device.c:1213 #17 crtc_frame_deadline_dispatch at /usr/include/glib-2.0/glib/gmem.h:242 #18 dispatch_task_func at ../src/backends/native/meta-thread-impl.c:419 #19 meta_thread_impl_fd_source_dispatch at ../src/backends/native/meta-thread-impl.c:435 #21 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284 #22 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349 #24 meta_thread_impl_run at ../src/backends/native/meta-thread-impl.c:586 #25 thread_impl_func at ../src/backends/native/meta-thread.c:328 #26 g_thread_proxy at ../glib/gthread.c:831 #28 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Created attachment 1991442 [details] File: mountinfo
Created attachment 1991443 [details] File: cpuinfo
Created attachment 1991444 [details] File: var_log_messages
Created attachment 1991445 [details] File: os_info
Created attachment 1991446 [details] File: core_backtrace
Created attachment 1991447 [details] File: proc_pid_status
Created attachment 1991448 [details] File: backtrace
Created attachment 1991449 [details] File: environ
Created attachment 1991450 [details] File: open_fds
Created attachment 1991451 [details] File: maps
Created attachment 1991452 [details] File: limits
gnome session crashes on suspend. the computer suspends normally, you can only see it crashed on resume. I attached my journalctl from when the suspend process happened tomorrow night to the resume time. reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=70d77ba157e1411e9c4eee9b14bdc277;i=1b347;b=a9e469c5ac3643b5ac2bd6378bc4d9d6;m=11cfc847b;t=60b025688f95f;x=5c534fd904c4b80a 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.5.12-300.fc39.x86_64 package: gnome-shell-45.1-1.fc39 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-45.1-1.fc39.x86_64 (Fedora Project) 1700513769 backtrace_rating: 4 crash_function: meta_kms_impl_device_hold_fd comment: gnome session crashes on suspend. the computer suspends normally, you can only see it crashed on resume. I attached my journalctl from when the suspend process happened tomorrow night to the resume time.
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!
The machine was idle, I was away frfom the computer on both times when the crash happened. System and user logs do not show anything right before that could explain why the device_file (which should have been set before) is now null. The only thing that happened on both cases is that right before the crash, rtkit decided to change the priority of the process. reporter: libreport-2.17.11 crash_function: meta_kms_impl_device_hold_fd executable: /usr/bin/gnome-shell reason: gnome-shell killed by SIGABRT cmdline: /usr/bin/gnome-shell type: CCpp cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell uid: 1000 kernel: 6.6.3-200.fc39.x86_64 runlevel: N 5 package: gnome-shell-45.2-1.fc39 journald_cursor: s=6b1f0152bc5d4978bdac46f538f1c1d4;i=37bb0aa;b=3050bd48434040839a31f274e07e5346;m=5044e119d;t=60dff302d2241;x=363d7b54bff9ca61 rootdir: / backtrace_rating: 4
(btw my session is set to not suspend when idle when the power source is connected, and the logs do not mention any syspend or wakeup event around the time the issue happened)
No obvious reason, happened when screen was locked. May have happened while having networking issues, because was connected to multiple ethernet and wireless interfaces with failing internet connection or screen lock because of inactivity. reporter: libreport-2.17.11 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=518a30d2ee5e455e954ee520b1d05969;i=407d2ae;b=436a1f309a4d4d3296c03feb6a1b2a57;m=6265f4668;t=60e710b876305;x=baa0faf89584dce8 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell rootdir: / uid: 1000 kernel: 6.6.8-200.fc39.x86_64 package: gnome-shell-45.2-1.fc39 runlevel: N 5 backtrace_rating: 4 crash_function: meta_kms_impl_device_hold_fd comment: No obvious reason, happened when screen was locked. May have happened while having networking issues, because was connected to multiple ethernet and wireless interfaces with failing internet connection or screen lock because of inactivity.