Description of problem: while running open suse repo's signal desktop I clicked to read an unread text. GUI all got messed up and creashed the entire gnome shell Version-Release number of selected component: gnome-shell-47.4-1.fc41 Additional info: reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=cdc53c26a65e4c9a85ad690e0c709ee4;i=dab1e;b=ef1f9f5643384de7aedb96d103cfc845;m=a969d5d9;t=62f43c18394e9;x=c2ff4414d4090b36 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.13.5-200.fc41.x86_64 package: gnome-shell-47.4-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status Truncated backtrace: Thread no. 1 (5 frames) #9 amdgpu_ctx_set_sw_reset_status at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:474 #10 amdgpu_cs_submit_ib<(queue_type)0> at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:1998 #11 util_queue_thread_func at ../src/util/u_queue.c:294 #12 impl_thrd_routine at ../src/c11/impl/threads_posix.c:43 #14 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Created attachment 2078326 [details] File: proc_pid_status
Created attachment 2078327 [details] File: maps
Created attachment 2078328 [details] File: limits
Created attachment 2078329 [details] File: environ
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!
Created attachment 2078330 [details] File: open_fds
Created attachment 2078331 [details] File: mountinfo
Created attachment 2078332 [details] File: os_info
Created attachment 2078333 [details] File: cpuinfo
Created attachment 2078334 [details] File: core_backtrace
Created attachment 2078335 [details] File: dso_list
Created attachment 2078336 [details] File: var_log_messages
Created attachment 2078337 [details] File: backtrace
crashed while I was typing something on gnome-terminal was open 3 apps open, signal-desktop chrome text editor reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=cdc53c26a65e4c9a85ad690e0c709ee4;i=dab1e;b=ef1f9f5643384de7aedb96d103cfc845;m=a969d5d9;t=62f43c18394e9;x=c2ff4414d4090b36 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.13.5-200.fc41.x86_64 package: gnome-shell-47.4-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status
crashed while doing nothing, chrome was active app 3 apps open, signal-desktop chrome text editor reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=cdc53c26a65e4c9a85ad690e0c709ee4;i=dab1e;b=ef1f9f5643384de7aedb96d103cfc845;m=a969d5d9;t=62f43c18394e9;x=c2ff4414d4090b36 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.13.5-200.fc41.x86_64 package: gnome-shell-47.4-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status
I was watching a YouTube video with LibreWolf when the system froze and I got kicked back to the login screen. reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=c4f697c207294097a033a12347a8a79c;i=83c91;b=ab2e7cfcce2b4c55a8e827f99ca787dd;m=7b8f6a785;t=62f9de1806c64;x=8c772481d47c8cb1 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.13.5-200.fc41.x86_64 package: gnome-shell-47.4-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: I was watching a YouTube video with LibreWolf when the system froze and I got kicked back to the login screen.
Opened the Vivaldi browser reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=c4f697c207294097a033a12347a8a79c;i=8f805;b=b1c84bd2cd1e4662b7372289a3e4a583;m=1c809be39;t=62fbececbe3e6;x=a67a23e15279ad3f 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.13.5-200.fc41.x86_64 package: gnome-shell-47.4-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: Opened the Vivaldi browser
crashed while switching windows (of multiple apps), chrome was active app 3 apps open, - chrome - text editor - ptyxis reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=cdc53c26a65e4c9a85ad690e0c709ee4;i=dab1e;b=ef1f9f5643384de7aedb96d103cfc845;m=a969d5d9;t=62f43c18394e9;x=c2ff4414d4090b36 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.13.5-200.fc41.x86_64 package: gnome-shell-47.4-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status
I was watching a YouTube livestream and playing a Steam game at the same time. Slowly, over time there were some glitchy squares and I quitted the game. The glitches continued and the audio got glitchy as well. Then the shell stuttered and crashed. reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=c4f697c207294097a033a12347a8a79c;i=e45b6;b=448405ff9abf4f82841d74d391d20cc6;m=1f9bc9aed;t=63052fefd5834;x=54ff57946fcfd6e6 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.13.6-200.fc41.x86_64 package: gnome-shell-47.4-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: I was watching a YouTube livestream and playing a Steam game at the same time. Slowly, over time there were some glitchy squares and I quitted the game. The glitches continued and the audio got glitchy as well. Then the shell stuttered and crashed.
Probably a consequence of Xwayland crashing reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=2976431ac20b49a395dfc774c05561cb;i=2d3df4;b=401bae5203054661ba0d22b882e44107;m=28812267a;t=630a18066d13f;x=7f13ad79360bebbb 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.13.6-200.fc41.x86_64 package: gnome-shell-47.4-1.fc41 runlevel: N 5 dso_list: /usr/bin/gnome-shell gnome-shell-47.4-1.fc41.x86_64 (Fedora Project) 1739006766 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: Probably a consequence of Xwayland crashing
crashed after pressing the screenshot button while taking screenshot selection amdgpu page fault on process gnome-shell reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=cdc53c26a65e4c9a85ad690e0c709ee4;i=dab1e;b=ef1f9f5643384de7aedb96d103cfc845;m=a969d5d9;t=62f43c18394e9;x=c2ff4414d4090b36 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.13.5-200.fc41.x86_64 package: gnome-shell-47.4-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status
crashed after pressing the super key button which usually brings thumbnail list of running applications and a search button on top no menu nothing appeared, screen/display just froze and gnome-shell crashed / page faulted badly! gnome-shell restarted after GPU reset but that killed all existing GUI apps and a minute later I am back to login screen! amdgpu page fault on process gnome-shell reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=cdc53c26a65e4c9a85ad690e0c709ee4;i=dab1e;b=ef1f9f5643384de7aedb96d103cfc845;m=a969d5d9;t=62f43c18394e9;x=c2ff4414d4090b36 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.13.5-200.fc41.x86_64 package: gnome-shell-47.4-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status
This message is a reminder that Fedora Linux 41 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15. 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 '41'. 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 41 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.
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15. Fedora Linux 41 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.