Description of problem: It happend several times. Approx. 30 minutes after session start. Version-Release number of selected component: gnome-shell-49.1-2.fc43 Additional info: reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=d67121b8c51349cb9fb53f21cfa0f7b8;i=14ae9;b=34b4ceb9c7e244cb9b78ce969ddb8140;m=85f4b508;t=6433a3ea09007;x=2a56d52cc5294939 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.17.7-300.fc43.x86_64 package: gnome-shell-49.1-2.fc43 runlevel: /bin/sh: řádek 1: runlevel: příkaz nenalezen comment: It happend several times. Approx. 30 minutes after session start. backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status Truncated backtrace: Thread no. 0 (5 frames) #1 amdgpu_ctx_set_sw_reset_status at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:463 #2 amdgpu_cs_submit_ib<(queue_type)0> at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:1993 #3 util_queue_thread_func at ../src/util/u_queue.c:294 #4 impl_thrd_routine at ../src/c11/impl/threads_posix.c:43 #6 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Potential duplicate: bug 2349142
Created attachment 2113667 [details] File: proc_pid_status
Created attachment 2113668 [details] File: maps
Created attachment 2113669 [details] File: limits
Created attachment 2113670 [details] File: environ
Created attachment 2113671 [details] File: open_fds
Created attachment 2113672 [details] File: mountinfo
Created attachment 2113673 [details] File: os_info
Created attachment 2113674 [details] File: cpuinfo
Created attachment 2113675 [details] File: core_backtrace
Created attachment 2113676 [details] File: dso_list
Created attachment 2113677 [details] File: var_log_messages
Created attachment 2113678 [details] File: backtrace
Bug reports for this component on Red Hat Bugzilla are not actively monitored. Please consider reporting your issue directly to GNOME at https://gitlab.gnome.org/GNOME/ to improve the chances that your issue will be resolved. 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!
It happened randomly while browsing within Brave. No specific trigger. Therefore it's not reproducible. reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=82f756a24eee4dceadb8fffb3ad2f025;i=4784e3;b=2f0f9c7bc15543f9ba696bfc6f0742d3;m=c258556ed;t=642c5dc6b55fe;x=1188038ef8f767f 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.17.6-300.fc43.x86_64 package: gnome-shell-49.1-2.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: It happened randomly while browsing within Brave. No specific trigger. Therefore it's not reproducible.
Openned a program and the whole system froze, then crashed reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=52a5e8ddc577432c85f665ba72f0dca4;i=34af09;b=2616d706abc14a719675b0a838e13d2b;m=4b3e073;t=643deb5c44ab7;x=6d82389b9d9fee65 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.17.7-300.fc43.x86_64 package: gnome-shell-49.1-2.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: Openned a program and the whole system froze, then crashed
As far as I remeber just browsing the web with firefox and gnome crashed reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=6ab39759fa6e4b8ca3e9fab9b41762ae;i=1651fb;b=6247a459a57f4273b5a14160b3e5e7f4;m=1dcf01125;t=6442bcca8e6f8;x=5f369a62d25714f2 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1001.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1001 kernel: 6.17.8-300.fc43.x86_64 package: gnome-shell-49.1-2.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: As far as I remeber just browsing the web with firefox and gnome crashed
This gnome-shell crash seems to happen while I am using the Signal desktop app. It's been happening across multiple versions of Gnome 49. reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=5f622d2c23374edca462dced004cc9a2;i=5cdb0;b=c805647cf3db4f81a27bf05727604769;m=34205ebb11;t=6444cc902a354;x=c9bd301e0609bfe9 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.17.7-300.fc43.x86_64 package: gnome-shell-49.1-2.fc43 runlevel: /bin/sh: line 1: runlevel: command not found comment: This gnome-shell crash seems to happen while I am using the Signal desktop app. It's been happening across multiple versions of Gnome 49. backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status
Same problem using Brave, BrowserOS, and so on. Every chrome based browser crashes in some pages (latest crash when I visited a release page from a github project)
It actually happens on pages with a video (mp4) - for example the latest release page of BrowserOS contains a video. When I visit it, Gnome crashes, computer freezes and I must hard reset.
I think this is caused by PSR i am using amd igpu 780m and just encountered this only in gnome DEs it usually triggers when I leave the screen on for more than 5 minutes without any activity but if i set the screen timeout to 1 minute it does not happen. also there is an issue with the suspend wher sometimes if I wake it from suspend it would not detect the touchpad reporter: libreport-2.17.15 uid: 1000 runlevel: /bin/sh: line 1: runlevel: command not found package: gnome-shell-49.2-2.fc43 cmdline: /usr/bin/gnome-shell reason: gnome-shell killed by SIGABRT rootdir: / journald_cursor: s=55e537d0565e4e16a519ff99b314fd51;i=15461e;b=7d21a51169aa403295189e61073198b5;m=9880bc4d;t=6469bc1714702;x=76b92f66754478b8 executable: /usr/bin/gnome-shell backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell crash_function: amdgpu_ctx_set_sw_reset_status comment: I think this is caused by PSR i am using amd igpu 780m and just encountered this only in gnome DEs it usually triggers when I leave the screen on for more than 5 minutes without any activity but if i set the screen timeout to 1 minute it does not happen. also there is an issue with the suspend wher sometimes if I wake it from suspend it would not detect the touchpad type: CCpp kernel: 6.17.12-300.fc43.x86_64
The crash happened during video playback in the native-installed Firefox browser. The root cause appears to be the AMDGPU firmware. reporter: libreport-2.17.15 uid: 1000 rootdir: / cmdline: /usr/bin/gnome-shell backtrace_rating: 4 kernel: 6.17.12-300.fc43.x86_64 journald_cursor: s=d492bc7171544ab2829303e50bc93a52;i=7161;b=dcb0b484738244ab883d6e13c54acae4;m=c748f37;t=6471cdcd57805;x=242d3f5c0c579124 runlevel: /bin/sh: line 1: runlevel: command not found comment: The crash happened during video playback in the native-installed Firefox browser. The root cause appears to be the AMDGPU firmware. type: CCpp cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell package: gnome-shell-49.2-2.fc43 reason: gnome-shell killed by SIGABRT crash_function: amdgpu_ctx_set_sw_reset_status executable: /usr/bin/gnome-shell
Compressing mp4 and pdf files to zip archive in local ~/Documents to ~/Documents folder. Zip file has no damage or missing files. Was connected to a SMB, but not involved. Had zen brower, listening to pandora, terminal and steam open. 10 min before had installed jar with openjava 25 reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=8278800853954682bff85de5c67e607b;i=9e17a;b=3c3c815d3e8f436192acd72dc2b77be3;m=73403cc1;t=6474222026f95;x=96f84c34a078680 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.17.11-300.fc43.x86_64 package: gnome-shell-49.2-2.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status
1. Open Vivaldi browser 2. Goto komoot bike route https://www.komoot.com/de-de/tour/2706901801/zoom 3. Zoom into map and click on parts of the route. Sometimes the whole UI freezes for ~10 seconds, sometimes it crashes (like this) reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=473aa7f73686402b9b5929c925b64d19;i=ab0b1;b=0b330d8b6b6a46c6a471d45f24a8ab12;m=2a603adba;t=647840973fbd1;x=80b7dc4ee3f8b972 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.17.12-300.fc43.x86_64 package: gnome-shell-49.2-2.fc43 runlevel: /bin/sh: Zeile 1: runlevel: Kommando nicht gefunden backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status
What was happening at the time: 1. Typical Forza Horizon 5 gameplay using Proton-GE 10.29 with vesktop audio call on second monitor 2. Both screens froze with voice call audio still playing 3. Screens blacked out 4. I was thrown to login screen logged out This problem happened to me only once, no wonder what caused that. How to reproduce: 1. Start system 2. Log in to regular user 3. Start vesktop 4. Join voice call 5. Start steam 6. Start Forza Horizon 5 7. Play some time. Additional info: I noticed that gnome is crashing sometimes after changing from Radeon RX 6600 XT to Radeon RX 7800 XT. It never crashed with old GPU. reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=73e4f50d50f743c6a8d5d1789d73719a;i=dfd0fc;b=d26c1f6c2e654b2e9bd895d86ca567d1;m=9052b0721;t=649a02bd623aa;x=228ddc0175fb338e 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.18.7-200.fc43.x86_64 package: gnome-shell-49.3-2.fc43 runlevel: /bin/sh: linia 1: runlevel: nie znaleziono polecenia backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status
Start a Google Meet video meeting via "Ungoogled Chromium" with external USB camera + mic. Within a few seconds of starting the call, the desktop froze completely (while the in-call audio was still working - video froze). After some time in that state, the desktop session crashed. reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGABRT journald_cursor: s=1e886a5d9565462395955e4a672f7323;i=65f456;b=fac4068748154585a966b704ed896a21;m=f2c447b2;t=64a7559823839;x=e872ede27ebf23ee 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.18.8-200.fc43.x86_64 package: gnome-shell-49.3-2.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: Start a Google Meet video meeting via "Ungoogled Chromium" with external USB camera + mic. Within a few seconds of starting the call, the desktop froze completely (while the in-call audio was still working - video froze). After some time in that state, the desktop session crashed.
I have to admit that these repeated crashes are really starting to ruin the experience I've had with Fedora for the past 15 years. Just having a video on a web page makes me afraid of a crash happening, regardless of the browser. I understand that this kind of bug is difficult to deal with, and I don't know how else to help you. If there's anything I can do to help fix or test solutions, I'm here.