Description of problem: I could not find the root of the problem. This happens occasionally, mostly when using multiple apps at the same time. My guess is that it has something to do with RAM management. Version-Release number of selected component: xorg-x11-server-Xwayland-22.1.9-1.fc38 Additional info: reporter: libreport-2.17.9 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=cf671a8b68e64a38a553fbf1e458c7cf;i=4b035;b=c16c66db34834219a4a1d91e7d40ef54;m=532e5a5d5;t=5fa6a552695c7;x=4b0bfb81e1fd5e39 executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.2MAO31 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.2.12-300.fc38.x86_64 package: xorg-x11-server-Xwayland-22.1.9-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: nouveau_pushbuf_data Truncated backtrace: Thread no. 1 (29 frames) #16 nouveau_pushbuf_data at ../nouveau/pushbuf.c:730 #18 pushbuf_submit at ../nouveau/pushbuf.c:331 #19 pushbuf_flush at ../nouveau/pushbuf.c:408 #20 nouveau_pushbuf_kick at ../nouveau/pushbuf.c:782 #21 PUSH_KICK at ../src/gallium/drivers/nouveau/nouveau_winsys.h:98 #22 nvc0_flush at ../src/gallium/drivers/nouveau/nvc0/nvc0_context.c:88 #23 st_flush at ../src/mesa/state_tracker/st_cb_flush.c:60 #24 st_glFlush at ../src/mesa/state_tracker/st_cb_flush.c:94 #25 glamor_flush at ../glamor/glamor_utils.h:683 #27 glamor_block_handler at ../glamor/glamor.c:274 #28 xwl_present_flush at ../hw/xwayland/xwayland-present.c:559 #29 present_execute_copy at ../present/present_execute.c:88 #30 xwl_present_execute at ../hw/xwayland/xwayland-present.c:831 #31 xwl_present_msc_bump at ../hw/xwayland/xwayland-present.c:427 #32 xwl_present_frame_callback at ../hw/xwayland/xwayland-present.c:455 #33 frame_callback at ../hw/xwayland/xwayland-window.c:831 #35 ffi_call_unix64 at ../src/x86/unix64.S:104 #36 ffi_call_int at ../src/x86/ffi64.c:673 #37 ffi_call at ../src/x86/ffi64.c:710 #38 wl_closure_invoke at ../src/connection.c:1025 #39 dispatch_event at ../src/wayland-client.c:1631 #40 dispatch_queue at ../src/wayland-client.c:1777 #41 wl_display_dispatch_queue_pending at ../src/wayland-client.c:2019 #42 wl_display_dispatch_pending at ../src/wayland-client.c:2082 #43 xwl_read_events at ../hw/xwayland/xwayland-screen.c:487 #45 ospoll_wait at ../os/ospoll.c:657 #46 WaitForSomething at ../os/WaitFor.c:208 #47 Dispatch at ../dix/dispatch.c:492 #48 dix_main at ../dix/main.c:271 Potential duplicate: bug 2120512
Created attachment 1960886 [details] File: proc_pid_status
Created attachment 1960887 [details] File: maps
Created attachment 1960888 [details] File: limits
Created attachment 1960889 [details] File: environ
Created attachment 1960890 [details] File: open_fds
Created attachment 1960891 [details] File: mountinfo
Created attachment 1960892 [details] File: os_info
Created attachment 1960893 [details] File: cpuinfo
Created attachment 1960894 [details] File: core_backtrace
Created attachment 1960895 [details] File: dso_list
Created attachment 1960896 [details] File: var_log_messages
Created attachment 1960897 [details] File: backtrace
Waking computer up from sleep. reporter: libreport-2.17.9 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=567ea76ef93a4791a07ec13e3ab4d49b;i=6d2a3;b=59ced5e64f1741039df4bdcc7f2024a3;m=3f80d50ef;t=5fb30866884e0;x=f3eefb839a84a485 executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -auth /run/user/1000/xauth_CRdULX -listen 48 -listen 49 -displayfd 40 -rootless -wm 43 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-kwin_wayland.service rootdir: / uid: 1000 kernel: 6.2.14-300.fc38.x86_64 package: xorg-x11-server-Xwayland-22.1.9-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: nouveau_pushbuf_data comment: Waking computer up from sleep.
I also just experienced this crash - not after system sleep but after waking from blank/off screen due to inactivity. It looks like something that is happening a lot: https://retrace.fedoraproject.org/faf/reports/691141/
Log in to Plasma (Wayland) on Fedora 38 reporter: libreport-2.17.11 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=35a32a55cb304495b98884c519428d30;i=17ce7;b=6edd626d48ea469eb3827323fc853c91;m=112ce63fe;t=6011368d0e759;x=484de1214104e968 executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -auth /run/user/1000/xauth_YCHQcS -listen 53 -listen 54 -displayfd 45 -rootless -wm 48 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-kwin_wayland.service rootdir: / uid: 1000 kernel: 6.3.12-200.fc38.x86_64 package: xorg-x11-server-Xwayland-22.1.9-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: nouveau_pushbuf_data comment: Log in to Plasma (Wayland) on Fedora 38
Switched between applications - from Chrome to IntelliJ IDEA reporter: libreport-2.17.11 package: xorg-x11-server-Xwayland-22.1.9-2.fc38 backtrace_rating: 4 reason: Xwayland killed by SIGABRT kernel: 6.4.6-200.fc38.x86_64 rootdir: / runlevel: N 5 executable: /usr/bin/Xwayland crash_function: nouveau_pushbuf_data journald_cursor: s=1ebfeb05b15f4a3f90c193bc07855763;i=cf6b9;b=2a23e3b80f6a448c84ec82c011db1775;m=27f2bec4a1;t=601deb3cd6c0a;x=b094f087e02b6529 type: CCpp comment: Switched between applications - from Chrome to IntelliJ IDEA cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.513R81 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients uid: 1000
I've just clicked on Steam Launcher. No other action has been done. reporter: libreport-2.17.11 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=2199a9a89cc840f984e666ef5ddc4f3b;i=11e2b8;b=e16305c21d1244e4a17bbefa1c688ea0;m=282b9af86b;t=603d77e13a8fd;x=77ff57bfbf8bada1 executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.29K691 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.4.11-200.fc38.x86_64 package: xorg-x11-server-Xwayland-22.1.9-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: nouveau_pushbuf_data comment: I've just clicked on Steam Launcher. No other action has been done.
Running skype (video call) and firefox simultaneously. I don't know if either was related. reporter: libreport-2.17.11 reason: Xwayland killed by SIGABRT kernel: 6.4.15-200.fc38.x86_64 runlevel: N 5 uid: 1000 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-kwin_wayland.service package: xorg-x11-server-Xwayland-22.1.9-2.fc38 executable: /usr/bin/Xwayland journald_cursor: s=551fab192432425e98198379181a989e;i=767f8c;b=c8d30f33925246a8b9c84bf671400465;m=9902870b;t=606097ffaf189;x=aaa52c33c97acc7 cmdline: /usr/bin/Xwayland :0 -auth /run/user/1000/xauth_HQctXb -listen 49 -listen 50 -displayfd 41 -rootless -wm 44 crash_function: nouveau_pushbuf_data type: CCpp rootdir: / backtrace_rating: 4 comment: Running skype (video call) and firefox simultaneously. I don't know if either was related.
Crashed during a Zoom conference. Gnome-shell also crashed and reset to the login screen. reporter: libreport-2.17.11 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=cc7686649d86449e9138a6dac9d7b888;i=acb0;b=209cacf555014109b8ca969706738be6;m=5081939a36;t=606d063b14497;x=649d41541c81ec00 executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.JSBZB2 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.5.5-200.fc38.x86_64 package: xorg-x11-server-Xwayland-22.1.9-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: nouveau_pushbuf_data comment: Crashed during a Zoom conference. Gnome-shell also crashed and reset to the login screen.
I was working until happend reporter: libreport-2.17.11 rootdir: / cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.FU32D2 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients backtrace_rating: 4 package: xorg-x11-server-Xwayland-22.1.9-3.fc38 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell crash_function: nouveau_pushbuf_data type: CCpp uid: 1000 runlevel: N 5 reason: Xwayland killed by SIGABRT kernel: 6.5.9-200.fc38.x86_64 executable: /usr/bin/Xwayland journald_cursor: s=965c71f6951a4d28a35d431ba7b7594b;i=930c;b=55058a40353e45eebe2f754c84614689;m=232d5747a;t=6096c3a0f37e2;x=4d76824364fcfb8e comment: I was working until happend
the vs code be closed of surprised reporter: libreport-2.17.11 rootdir: / cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.YSEWG2 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 -byteswappedclients backtrace_rating: 4 package: xorg-x11-server-Xwayland-22.1.9-3.fc38 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell crash_function: nouveau_pushbuf_data type: CCpp uid: 1000 runlevel: N 5 reason: Xwayland killed by SIGABRT kernel: 6.6.7-100.fc38.x86_64 executable: /usr/bin/Xwayland journald_cursor: s=a8ced1556ae54d24b60e9682fd0571bb;i=92335;b=c95f12b6829942a587c5036ccec4641d;m=405ec5991;t=60e270f13bf6e;x=b6d83e1b5091de3 comment: the vs code be closed of surprised
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. 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 '38'. 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 38 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 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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.