Version-Release number of selected component: xorg-x11-server-Xwayland-22.1.9-2.fc38 Additional info: reporter: libreport-2.17.11 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=0f7adb8ebe5e452caac82ba7b2d7754f;i=154f7e;b=07af4d6994604129807bf007e1ee7c2d;m=50ab02534;t=601de7a6f2859;x=9db1849103a65b8d executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.1AYZ81 -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.6-200.fc38.x86_64 package: xorg-x11-server-Xwayland-22.1.9-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: xwl_give_up Truncated backtrace: Thread no. 1 (6 frames) #13 xwl_give_up at ../hw/xwayland/xwayland-screen.c:81 #14 xwl_read_events at ../hw/xwayland/xwayland-screen.c:483 #15 ospoll_wait at ../os/ospoll.c:657 #16 WaitForSomething at ../os/WaitFor.c:208 #17 Dispatch at ../dix/dispatch.c:492 #18 dix_main at ../dix/main.c:271
Created attachment 1981147 [details] File: proc_pid_status
Created attachment 1981148 [details] File: maps
Created attachment 1981149 [details] File: limits
Created attachment 1981150 [details] File: environ
Created attachment 1981151 [details] File: open_fds
Created attachment 1981152 [details] File: mountinfo
Created attachment 1981153 [details] File: os_info
Created attachment 1981154 [details] File: cpuinfo
Created attachment 1981155 [details] File: core_backtrace
Created attachment 1981156 [details] File: dso_list
Created attachment 1981157 [details] File: var_log_messages
Created attachment 1981158 [details] File: backtrace
From attachment 1981157 [details]: (EE) failed to read Wayland events: Connection reset by peer This is a compositor issue, not Xwayland doing. Can you please check in the journalctl logs whether GNOME SHell dies prior to this message?
The Gnome Video movie looking reporter: libreport-2.17.11 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=47c6206f2b1a44fcb3b8a7659859b34a;i=19a4f;b=c49fb8c5248048ba89741c77612bf95d;m=210e242f8;t=60233419edf37;x=d12e82e8c6781634 executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.DA4281 -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.7-200.fc38.x86_64 package: xorg-x11-server-Xwayland-22.1.9-2.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: xwl_give_up comment: The Gnome Video movie looking
(In reply to Axel Wintermann from comment #14) > The Gnome Video movie looking > […] > crash_function: xwl_give_up That ^^^ means that the communication with the Wayland compositor was lost, most likely because the Wayland compositor has crashed or vanished, meaning this is unlikely a bug in Xwayland. Same as comment 13, can you please check (and attach) the journalctl logs to see whether GNOME Shell died prior to this message?
Computer was idle, unlocked screen and left monitor was unresponsive - began closing applications down with intent to reboot when it crashed on it's own. reporter: libreport-2.17.11 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=5b6a5f7706c9420392ba1f87adfa305f;i=57e65;b=7ad4fefe032c4e9eb8621d5fc64d928b;m=2c2a567545;t=6051c6035fc92;x=153a4b8972efd1ff executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.EJVWA2 -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.14-200.fc38.x86_64 package: xorg-x11-server-Xwayland-22.1.9-2.fc38 runlevel: N 5 dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-22.1.9-2.fc38.x86_64 (Fedora Project) 1692211917 backtrace_rating: 4 crash_function: xwl_give_up comment: Computer was idle, unlocked screen and left monitor was unresponsive - began closing applications down with intent to reboot when it crashed on it's own.
Well, same as comment 13 and comment 15, please check (and attach) the journalctl logs to see whether GNOME Shell died prior to this message.
wake the system from sleep and it exploded reporter: libreport-2.17.11 type: CCpp reason: Xwayland killed by SIGABRT journald_cursor: s=e63723997a7d4641ac6b506972136111;i=129e1;b=5d3fe40ac6f34ca285faa4fe21140f48;m=2ec931b56;t=60823693f3f9d;x=9bb6f29d83da3a6d executable: /usr/bin/Xwayland cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.N0H2C2 -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.7-200.fc38.x86_64 package: xorg-x11-server-Xwayland-22.1.9-2.fc38 runlevel: N 5 dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-22.1.9-2.fc38.x86_64 (Fedora Project) 1697556010 backtrace_rating: 4 crash_function: xwl_give_up comment: wake the system from sleep and it exploded
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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days