Version-Release number of selected component: xorg-x11-server-Xwayland-24.1.6-1.fc41 Additional info: reporter: libreport-2.17.15 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=df8ca9def3c6476cb2455ab1eb40a130;i=251c468f;b=d2ea9967ac5f42db8f3f106e9c5d856f;m=3c613057;t=62f79498dc01e;x=c6b0d4741fa5d481 executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.6UV622 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients -enable-ei-portal 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: xorg-x11-server-Xwayland-24.1.6-1.fc41 runlevel: N 5 dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-24.1.6-1.fc41.x86_64 (Fedora Project) 1740781246 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status Truncated backtrace: Thread no. 1 (5 frames) #14 amdgpu_ctx_set_sw_reset_status at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:474 #15 amdgpu_cs_submit_ib<(queue_type)0> at ../src/gallium/winsys/amdgpu/drm/amdgpu_cs.cpp:1995 #16 util_queue_thread_func at ../src/util/u_queue.c:294 #17 impl_thrd_routine at ../src/c11/impl/threads_posix.c:43 #19 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Created attachment 2078802 [details] File: proc_pid_status
Created attachment 2078803 [details] File: maps
Created attachment 2078804 [details] File: limits
Created attachment 2078805 [details] File: environ
Created attachment 2078806 [details] File: open_fds
Created attachment 2078807 [details] File: mountinfo
Created attachment 2078808 [details] File: os_info
Created attachment 2078809 [details] File: cpuinfo
Created attachment 2078810 [details] File: core_backtrace
Created attachment 2078811 [details] File: var_log_messages
Created attachment 2078812 [details] File: backtrace
Some combination og IntelliJ and Librewolf made the session unresponsive reporter: libreport-2.17.15 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=2976431ac20b49a395dfc774c05561cb;i=2d347d;b=401bae5203054661ba0d22b882e44107;m=21a16052d;t=630a1126aaff3;x=2cec75711230b740 executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.S9TL32 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients -enable-ei-portal 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: xorg-x11-server-Xwayland-24.1.6-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: Some combination og IntelliJ and Librewolf made the session unresponsive
It's a GPU reset, moving to Mesa.
*** Bug 2354282 has been marked as a duplicate of this bug. ***
It's impossible to use the system. The interface hangs all the time and returns to the login screen after killing all processes.
I was running a modded fabric Minecraft server and playing on it. Since Minecraft currently runs using Xwayland, I imagine some bug caused Xwayland to crash, which took down all the graphics with it, since all I saw after the crash was a black screen. Pressing ctrl+alt+3 did not work. Not sure if this is easily reproducable, but Xwayland crashing shouldn't take down the whole system. reporter: libreport-2.17.15 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=d429228ed71c48e289756be732583f36;i=5791697;b=657fb1f63b96485c8801ee7849fd0f55;m=703ce98e4;t=6315afc18d9cb;x=6bdd49bf18fc918c executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.0TKY32 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients -enable-ei-portal cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.13.8-200.fc41.x86_64 package: xorg-x11-server-Xwayland-24.1.6-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: I was running a modded fabric Minecraft server and playing on it. Since Minecraft currently runs using Xwayland, I imagine some bug caused Xwayland to crash, which took down all the graphics with it, since all I saw after the crash was a black screen. Pressing ctrl+alt+3 did not work. Not sure if this is easily reproducable, but Xwayland crashing shouldn't take down the whole system.
I just resumed from suspend sleep, and boum, this happened. reporter: libreport-2.17.15 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=9a91fb5ce5c64a989f6889b18ee4a8c7;i=28b0c5;b=8a967031afda4d49bc5c52d1d44dc563;m=189defed9e;t=631a75b4f3fda;x=bec7b6e1fd4916af executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.RD6532 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients -enable-ei-portal cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.13.8-200.fc41.x86_64 package: xorg-x11-server-Xwayland-24.1.6-1.fc41 runlevel: N 5 dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-24.1.6-1.fc41.x86_64 (Fedora Project) 1740754382 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: I just resumed from suspend sleep, and boum, this happened.
i dont know reporter: libreport-2.17.15 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=f3389081908447e3a716dd8eaa914e71;i=13905;b=e90b3928a05f4f728e04833fa238f121;m=2579e9cb0;t=630f089a7748e;x=903f2cc32e631dc3 executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.XI9P32 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients -enable-ei-portal cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.13.7-200.fc41.x86_64 package: xorg-x11-server-Xwayland-24.1.6-1.fc41 runlevel: N 5 dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-24.1.6-1.fc41.x86_64 (Fedora Project) 1742578913 backtrace_rating: 4 crash_function: amdgpu_ctx_set_sw_reset_status comment: i dont know
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.