Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Random crashes periodically occuring while working in Clion and Firefox opened at the same time. Version-Release number of selected component: xorg-x11-server-Xwayland-21.1.0-1.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 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.12VA10 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 crash_function: xwl_log_handler executable: /usr/bin/Xwayland journald_cursor: s=735b7d5a591540d0bad3600df4195cc2;i=c8b3;b=6637cf8179c04975b5424c50c8d11b79;m=db9f4e5f;t=5be99f5c698b5;x=33e9abcc40ba7286 kernel: 5.11.9-300.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1767128 [details] File: backtrace
Created attachment 1767129 [details] File: core_backtrace
Created attachment 1767130 [details] File: cpuinfo
Created attachment 1767131 [details] File: dso_list
Created attachment 1767132 [details] File: environ
Created attachment 1767133 [details] File: limits
Created attachment 1767134 [details] File: maps
Created attachment 1767135 [details] File: mountinfo
Created attachment 1767136 [details] File: open_fds
Created attachment 1767137 [details] File: proc_pid_status
Created attachment 1767138 [details] File: var_log_messages
It's an abort resulting from Wayland error, apparently related to glamor according to attachment 1767138 [details]: -- Mar 28 17:55:45 fedora gnome-shell[2765]: (EE) glamor0: GL error: GL_INVALID_OPERATION error generated. Mar 28 17:55:45 fedora gnome-shell[2765]: (EE) glamor0: GL error: GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete. Mar 28 17:55:45 fedora gnome-shell[2765]: (EE) Mar 28 17:55:45 fedora gnome-shell[2765]: Fatal server error: Mar 28 17:55:45 fedora gnome-shell[2765]: (EE) wl_surface@56: error 2: Failed to attach buffer to surface 56: Unknown buffer type Mar 28 17:55:45 fedora gnome-shell[2765]: (EE) -- Could it be Mesa?
> Could it be Mesa? Humm, according to attachment 1767136 [details] this is actually NVidia: -- 10:/dev/nvidiactl 11:/dev/nvidia0 17:/dev/nvidia-modeset […] --
I'm using nvidia rtx 2080 with rpmfusion proprietary driver.
I have no idea if that would improve things, it's a complete shot in the dark, but you may try this scratch build and report if that helps: https://koji.fedoraproject.org/koji/taskinfo?taskID=64787408
Or better, that one: https://koji.fedoraproject.org/koji/taskinfo?taskID=64834163 (This also adds a backtrace in case of GL error, that won't solve the problem but might give a hint at what glamor does that the NVidia driver doesn't like, so when the issue reoccurs, please make sure to capture and attach the output of journalctl at the time of the issue which should show the “(EE) glamor0: GL error: […[” with -hopefully- a backtrace)
Created attachment 1767757 [details] patched xwayland logs error starts on line 14020 >> Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) glamor0: GL error: GL_INVALID_OPERATION error generated.
Also with xorg-x11-server-Xwayland-debugsource-21.1.0-1.2test.fc34.x86_64 system is not able to recover (restart session, while system was able to recover before patched version), and there is "ibus-x11 killed by SIGEGV" in report app, but it is not been able to report it.
This looks like my retrace https://retrace.fedoraproject.org/faf/reports/113600/
Thanks @Mark, that's a very good start. Unfortunately, there is no debugging symbols installed on your system, so the logs don't show the actual functions involved (just the addresses). May I ask you to install the debuginfo symbols (from the test package) as well, and redo the test? https://kojipkgs.fedoraproject.org//work/tasks/4241/64834241/xorg-x11-server-Xwayland-debuginfo-21.1.0-1.2test.fc34.x86_64.rpm https://kojipkgs.fedoraproject.org//work/tasks/4241/64834241/xorg-x11-server-Xwayland-debugsource-21.1.0-1.2test.fc34.x86_64.rpm (ibus is another issue, if Xwayland crashes, ibus-x11 will die)
I'm pretty sure i've installed them ``` dnf history info 32 Transaction ID : 32 Begin time : Tue 30 Mar 2021 06:44:42 PM MSK Begin rpmdb : 1827:495defda1c18db89cd55a6e519b7e362540322fd End time : Tue 30 Mar 2021 06:44:43 PM MSK (1 seconds) End rpmdb : 1830:1acddf77a8061f828d7ec9dd81b17586a8ac1220 User : Mark Nefedov <marknefedov> Return-Code : Success Releasever : 34 Command Line : install xorg-x11-server-Xwayland-21.1.0-1.2test.fc34.x86_64.rpm xorg-x11-server-Xwayland-debuginfo-21.1.0-1.2test.fc34.x86_64.rpm xorg-x11-server-Xwayland-debugsource-21.1.0-1.2test.fc34.x86_64.rpm xorg-x11-server-Xwayland-devel-21.1.0-1.2test.fc34.x86_64.rpm Comment : Packages Altered: Install xorg-x11-server-Xwayland-debuginfo-21.1.0-1.2test.fc34.x86_64 @@commandline Install xorg-x11-server-Xwayland-debugsource-21.1.0-1.2test.fc34.x86_64 @@commandline Install xorg-x11-server-Xwayland-devel-21.1.0-1.2test.fc34.x86_64 @@commandline Upgrade xorg-x11-server-Xwayland-21.1.0-1.2test.fc34.x86_64 @@commandline Upgraded xorg-x11-server-Xwayland-21.1.0-1.fc34.x86_64 @@System ```
Humm weird, the logs do not show the symbols, from attachment 1767757 [details]: ``` Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) glamor0: GL error: GL_INVALID_OPERATION error generated. Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) Backtrace: Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 0: /usr/bin/Xwayland (0x55739dc7f000+0x164db9) [0x55739dde3db9] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 1: /lib64/libnvidia-eglcore.so.460.67 (0x7f948e6ee000+0xa4562d) [0x7f948f13362d] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 2: /lib64/libnvidia-eglcore.so.460.67 (0x7f948e6ee000+0xa45744) [0x7f948f133744] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 3: /lib64/libnvidia-eglcore.so.460.67 (0x7f948e6ee000+0xa46dfc) [0x7f948f134dfc] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 4: /usr/bin/Xwayland (0x55739dc7f000+0x4dcef) [0x55739dccccef] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 5: /usr/bin/Xwayland (0x55739dc7f000+0x3f9a0) [0x55739dcbe9a0] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 6: /usr/bin/Xwayland (0x55739dc7f000+0xa42b6) [0x55739dd232b6] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 7: /usr/bin/Xwayland (0x55739dc7f000+0x36e39) [0x55739dcb5e39] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 8: /lib64/libc.so.6 (__libc_start_main+0xd5) [0x7f94913ecb75] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 9: /usr/bin/Xwayland (0x55739dc7f000+0x3857e) [0x55739dcb757e] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) glamor0: GL error: GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete. Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) Backtrace: Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 0: /usr/bin/Xwayland (0x55739dc7f000+0x164db9) [0x55739dde3db9] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 1: /lib64/libnvidia-eglcore.so.460.67 (0x7f948e6ee000+0xa4562d) [0x7f948f13362d] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 2: /lib64/libnvidia-eglcore.so.460.67 (0x7f948e6ee000+0xa45801) [0x7f948f133801] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 3: /lib64/libnvidia-eglcore.so.460.67 (0x7f948e6ee000+0xa459d7) [0x7f948f1339d7] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 4: /lib64/libnvidia-eglcore.so.460.67 (0x7f948e6ee000+0xb43130) [0x7f948f231130] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 5: /usr/bin/Xwayland (0x55739dc7f000+0x4dd01) [0x55739dcccd01] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 6: /usr/bin/Xwayland (0x55739dc7f000+0x3f9a0) [0x55739dcbe9a0] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 7: /usr/bin/Xwayland (0x55739dc7f000+0xa42b6) [0x55739dd232b6] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 8: /usr/bin/Xwayland (0x55739dc7f000+0x36e39) [0x55739dcb5e39] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xd5) [0x7f94913ecb75] Mar 30 19:45:53 fedora gnome-shell[2487]: (EE) 10: /usr/bin/Xwayland (0x55739dc7f000+0x3857e) [0x55739dcb757e] ```
I'll try to see if I can match the symbols manually, tomorrow.
This is probably the most i'm able to obtain. ``` Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) glamor0: GL error: GL_INVALID_OPERATION error generated. Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) Backtrace: Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 0: /usr/bin/Xwayland (0x562e80b1c000+0x164db9) [0x562e80c80db9] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 1: /lib64/libnvidia-eglcore.so.460.67 (0x7fa331ce9000+0xa4562d) [0x7fa33272e62d] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 2: /lib64/libnvidia-eglcore.so.460.67 (0x7fa331ce9000+0xa45744) [0x7fa33272e744] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 3: /lib64/libnvidia-eglcore.so.460.67 (0x7fa331ce9000+0xa46dfc) [0x7fa33272fdfc] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 4: /usr/bin/Xwayland (0x562e80b1c000+0x4dcef) [0x562e80b69cef] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 5: /usr/bin/Xwayland (0x562e80b1c000+0x3f9a0) [0x562e80b5b9a0] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 6: /usr/bin/Xwayland (0x562e80b1c000+0xa42b6) [0x562e80bc02b6] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 7: /usr/bin/Xwayland (0x562e80b1c000+0x36e39) [0x562e80b52e39] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 8: /lib64/libc.so.6 (__libc_start_main+0xd5) [0x7fa3349e7b75] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 9: /usr/bin/Xwayland (0x562e80b1c000+0x3857e) [0x562e80b5457e] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) glamor0: GL error: GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete. Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) Backtrace: Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 0: /usr/bin/Xwayland (0x562e80b1c000+0x164db9) [0x562e80c80db9] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 1: /lib64/libnvidia-eglcore.so.460.67 (0x7fa331ce9000+0xa4562d) [0x7fa33272e62d] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 2: /lib64/libnvidia-eglcore.so.460.67 (0x7fa331ce9000+0xa45801) [0x7fa33272e801] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 3: /lib64/libnvidia-eglcore.so.460.67 (0x7fa331ce9000+0xa459d7) [0x7fa33272e9d7] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 4: /lib64/libnvidia-eglcore.so.460.67 (0x7fa331ce9000+0xb43130) [0x7fa33282c130] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 5: /usr/bin/Xwayland (0x562e80b1c000+0x4dd01) [0x562e80b69d01] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 6: /usr/bin/Xwayland (0x562e80b1c000+0x3f9a0) [0x562e80b5b9a0] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 7: /usr/bin/Xwayland (0x562e80b1c000+0xa42b6) [0x562e80bc02b6] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 8: /usr/bin/Xwayland (0x562e80b1c000+0x36e39) [0x562e80b52e39] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xd5) [0x7fa3349e7b75] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) 10: /usr/bin/Xwayland (0x562e80b1c000+0x3857e) [0x562e80b5457e] Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) Mar 30 21:08:04 fedora audit[3124]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=3124 comm="Xwayland" exe="/usr/bin/Xwayland" sig=6 res=1 Mar 30 21:08:04 fedora gnome-shell[1877]: Could not import pending buffer: Unknown buffer type Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) Mar 30 21:08:04 fedora gnome-shell[3124]: Fatal server error: Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) wl_surface@35: error 2: Failed to attach buffer to surface 35: Unknown buffer type Mar 30 21:08:04 fedora gnome-shell[3124]: (EE) Mar 30 21:08:04 fedora gnome-shell[1877]: WL: error in client communication (pid 1877) Mar 30 21:08:04 fedora systemd[1]: Created slice system-systemd\x2dcoredump.slice. Mar 30 21:08:04 fedora audit: BPF prog-id=57 op=LOAD Mar 30 21:08:04 fedora audit: BPF prog-id=58 op=LOAD Mar 30 21:08:04 fedora audit: BPF prog-id=59 op=LOAD Mar 30 21:08:04 fedora systemd[1]: Started Process Core Dump (PID 7918/UID 0). Mar 30 21:08:04 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-7918-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 30 21:08:05 fedora systemd-coredump[7919]: Process 3124 (Xwayland) of user 1000 dumped core. Stack trace of thread 3124: #0 0x00007fa3349fd292 raise (libc.so.6 + 0x3d292) #1 0x00007fa3349e68a4 abort (libc.so.6 + 0x268a4) #2 0x0000562e80c8997c OsAbort (Xwayland + 0x16d97c) #3 0x0000562e80c89c5c FatalError (Xwayland + 0x16dc5c) #4 0x0000562e80b54f40 xwl_log_handler (Xwayland + 0x38f40) #5 0x00007fa3351edcca wl_log (libwayland-client.so.0 + 0x5cca) #6 0x00007fa3351ee1cb display_handle_error (libwayland-client.so.0 + 0x61cb) #7 0x00007fa334810c04 ffi_call_unix64 (libffi.so.6 + 0x6c04) #8 0x00007fa334810107 ffi_call (libffi.so.6 + 0x6107) #9 0x00007fa3351eed10 wl_closure_invoke.constprop.0 (libwayland-client.so.0 + 0x6d10) #10 0x00007fa3351ef42b dispatch_event.isra.0 (libwayland-client.so.0 + 0x742b) #11 0x00007fa3351ef5ef wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x75ef) #12 0x0000562e80b5b56b xwl_read_events (Xwayland + 0x3f56b) #13 0x0000562e80c89501 ospoll_wait (Xwayland + 0x16d501) #14 0x0000562e80bc0700 Dispatch (Xwayland + 0xa4700) #15 0x0000562e80b52e39 main (Xwayland + 0x36e39) #16 0x00007fa3349e7b75 __libc_start_main (libc.so.6 + 0x27b75) #17 0x0000562e80b5457e _start (Xwayland + 0x3857e) Stack trace of thread 3401: #0 0x00007fa334ac1b5c recv (libc.so.6 + 0x101b5c) #1 0x00007fa333d5ae63 n/a (libEGL_nvidia.so.0 + 0x78e63) #2 0x00007fa333d5bc14 n/a (libEGL_nvidia.so.0 + 0x79c14) #3 0x00007fa333d50e05 n/a (libEGL_nvidia.so.0 + 0x6ee05) #4 0x00007fa333d9dcce n/a (libEGL_nvidia.so.0 + 0xbbcce) #5 0x00007fa33481e299 start_thread (libpthread.so.0 + 0x9299) #6 0x00007fa334ac06a3 __clone (libc.so.6 + 0x1006a3) Mar 30 21:08:05 fedora gnome-shell[1877]: Connection to xwayland lost Mar 30 21:08:05 fedora gnome-shell[1877]: Xwayland just died, attempting to recover ```
So, trying to match the addresses with the source in gdb (for some reason addr2line is being uncooperative here) gives: (gdb) info line *0x164db9 Line 130 of "../os/backtrace.c" starts at address 0x164db9 <xorg_backtrace+137> and ends at 0x164dd0 <xorg_backtrace+160>. (gdb) info line *0x4dcef Line 625 of "../hw/xwayland/xwayland-glamor-eglstream.c" starts at address 0x4dcef <xwl_glamor_eglstream_post_damage+431> and ends at 0x4dd01 <xwl_glamor_eglstream_post_damage+449>. 583 static void 584 xwl_glamor_eglstream_post_damage(struct xwl_window *xwl_window, 585 PixmapPtr pixmap, RegionPtr region) 586 { [...] 613 /* Setup our GL state */ 614 glUseProgram(xwl_eglstream->blit_prog); 615 glViewport(0, 0, pixmap->drawable.width, pixmap->drawable.height); 616 glActiveTexture(GL_TEXTURE0); 617 glBindVertexArray(xwl_eglstream->blit_vao); 618 glBindTexture(GL_TEXTURE_2D, glamor_get_pixmap_texture(pixmap)); 619 620 glUniform1i(xwl_eglstream->blit_is_rgba_pos, 621 pixmap->drawable.depth >= 32); 622 623 /* Blit rendered image into EGLStream surface */ 624 glDrawBuffer(GL_BACK); 625 glDrawArrays(GL_TRIANGLE_FAN, 0, 4); <--- The GL error comes from here 626 [...] 639 } (gdb) info line *0x3f9a0 Line 3701 of "/usr/include/wayland-client-protocol.h" starts at address 0x3f9a0 <block_handler+400> and ends at 0x3f9b8 <block_handler+424>. (gdb) info line *0xa42b6 Line 386 of "../dix/dixutils.c" starts at address 0xa42b6 <Dispatch+582> and ends at 0xa42ba <Dispatch+586>. (gdb) info line *0x36e39 Line 1116 of "../dix/devices.c" starts at address 0x36e39 <main+6409> and ends at 0x36e40 <main+6416>.
I have spawned a new scratch build with an additional fix, can you please give this a try and let me know how that goes: https://koji.fedoraproject.org/koji/taskinfo?taskID=64903573
Created attachment 1768055 [details] File: journalctl_dump_xorg-x11-server-Xwayland-21.1.0-1.3test.fc34
Humm, that gets rid of the GL error, but not of the invalid buffer…
@Mark, thanks a lot for your help, this is very much appreciated! Alright, based on the finding, I think (hope?) this should improve things: https://koji.fedoraproject.org/koji/taskinfo?taskID=64915328 Can you please try this new build, if this is not too much to ask?
Created attachment 1768086 [details] File: journalctl_dump_xorg-x11-server-Xwayland-21.1.0-1.4test
Humm, I'm confused now, can you please double check this is really the right package from https://koji.fedoraproject.org/koji/taskinfo?taskID=64915328 being installed and running at the time of the issue? Reason I ask is because the logs in attachment 1768086 [details] show: ``` Mar 31 15:50:00 fedora gnome-shell[23552]: (EE) glamor0: GL error: GL_INVALID_OPERATION error generated. Mar 31 15:50:00 fedora gnome-shell[23552]: (EE) glamor0: GL error: GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete. Mar 31 15:50:00 fedora gnome-shell[19512]: Could not import pending buffer: Unknown buffer type ``` But the patches in xorg-x11-server-Xwayland-21.1.0-1.4test should 1. avoid the GL error by checking the framebuffer status (as seen in comment 27) and 2. if a GL error occurs a backtrace will be generated, and there's none in attachment 1768086 [details].
Created attachment 1768089 [details] Overview glitch I'll reboot and try to reproduce crash again, also there is funny glitch going on, there is 2 Clion windows and one JbToolbox, but it looks like all windows share render target in overview. ``` sudo dnf list installed "xorg*" [sudo] password for marknefedov: Installed Packages xorg-x11-drv-amdgpu.x86_64 19.1.0-6.fc34 @anaconda xorg-x11-drv-ati.x86_64 19.1.0-5.fc34 @updates-testing xorg-x11-drv-evdev.x86_64 2.10.6-9.fc34 @anaconda xorg-x11-drv-fbdev.x86_64 0.5.0-8.fc34 @anaconda xorg-x11-drv-intel.x86_64 2.99.917-50.20200205.fc34 @anaconda xorg-x11-drv-libinput.x86_64 0.30.0-5.fc34 @anaconda xorg-x11-drv-nouveau.x86_64 1:1.0.15-11.fc34 @anaconda xorg-x11-drv-nvidia.x86_64 3:460.67-1.fc34 @rpmfusion-nonfree xorg-x11-drv-nvidia-kmodsrc.x86_64 3:460.67-1.fc34 @rpmfusion-nonfree xorg-x11-drv-nvidia-libs.x86_64 3:460.67-1.fc34 @rpmfusion-nonfree xorg-x11-drv-openchrome.x86_64 0.6.400-1.20210215git5dbad06.fc34 @updates-testing xorg-x11-drv-qxl.x86_64 0.1.5-19.fc34 @anaconda xorg-x11-drv-vesa.x86_64 2.4.0-11.fc34 @anaconda xorg-x11-drv-vmware.x86_64 13.2.1-15.fc34 @anaconda xorg-x11-drv-wacom.x86_64 0.40.0-1.fc34 @anaconda xorg-x11-drv-wacom-serial-support.x86_64 0.40.0-1.fc34 @anaconda xorg-x11-server-Xorg.x86_64 1.20.10-5.fc34 @anaconda xorg-x11-server-Xwayland.x86_64 21.1.0-1.4test.fc34 @@commandline xorg-x11-server-Xwayland-debuginfo.x86_64 21.1.0-1.4test.fc34 @@commandline xorg-x11-server-Xwayland-debugsource.x86_64 21.1.0-1.4test.fc34 @@commandline xorg-x11-server-Xwayland-devel.x86_64 21.1.0-1.4test.fc34 @@commandline xorg-x11-server-common.x86_64 1.20.10-5.fc34 @anaconda xorg-x11-utils.x86_64 7.5-37.fc34 @anaconda xorg-x11-xauth.x86_64 1:1.1-8.fc34 @anaconda xorg-x11-xinit.x86_64 1.4.0-9.fc34 @anaconda ```
Yes, the "glitches" are related - When the error occurs, the damage is not posted and the buffer not attached. I suspect the patches might be trying to work around a more serious problem.
Looks like, I've forgot to reboot. I've been running fine for some time, and looks like there is no more crashes. ``` ar 31 16:35:20 fedora gnome-shell[1863]: Over 50 separate programs have been generated which is very unusual, so something is probably wrong! Mar 31 16:35:44 fedora pipewire-pulse[1995]: pulse-server 0x55c469353360: [Firefox] UNDERFLOW channel:3 offset:71510208 underrun:1880 Mar 31 16:36:24 fedora rtkit-daemon[911]: Supervising 11 threads of 8 processes of 1 users. Mar 31 16:36:24 fedora rtkit-daemon[911]: Supervising 11 threads of 8 processes of 1 users. Mar 31 16:38:49 fedora pipewire-pulse[1995]: pulse-server 0x55c469353360: [Firefox] UNDERFLOW channel:0 offset:449030144 underrun:2048 Mar 31 16:39:58 fedora gnome-shell[3937]: EGLStream: Framebuffer incomplete 33305, not posting damage Mar 31 16:39:58 fedora gnome-shell[3937]: glamor: Failed to post damage Mar 31 16:40:15 fedora pipewire-pulse[1995]: 1 events suppressed Mar 31 16:40:15 fedora pipewire-pulse[1995]: pulse-server 0x55c469353360: [Firefox] UNDERFLOW channel:3 offset:95256000 underrun:1880 Mar 31 16:40:43 fedora gnome-shell[3937]: EGLStream: Framebuffer incomplete 33305, not posting damage Mar 31 16:40:43 fedora gnome-shell[3937]: glamor: Failed to post damage Mar 31 16:44:35 fedora pipewire-pulse[1995]: pulse-server 0x55c469353360: [Firefox] UNDERFLOW channel:4 offset:366912 underrun:1880 Mar 31 16:44:57 fedora pipewire-pulse[1995]: pulse-server 0x55c469353360: [Firefox] UNDERFLOW channel:4 offset:366912 underrun:1880 ```
Yes, those messages: ``` Mar 31 16:39:58 fedora gnome-shell[3937]: EGLStream: Framebuffer incomplete 33305, not posting damage Mar 31 16:39:58 fedora gnome-shell[3937]: glamor: Failed to post damage ``` Are exactly what I was expecting to see with the patches. Do you still see the glitches as well?
Created attachment 1768095 [details] overview 2 Yep, but now they are blinking between X windows like crazy :), and occasionally going black.
Yes, we don't crash anymore because we don't try to attach an invalid buffer anymore, yet that doesn't solve the original problem that leads to a GL_FRAMEBUFFER_UNDEFINED.
@Mark, mind giving this new build a try: https://koji.fedoraproject.org/koji/taskinfo?taskID=64951010 It's unlikely to solve the issue, but it will add some more error checking that could give a hint as to why we end up with the problem. Those messages will be found in the journaltcl logs as usual.
Created attachment 1768299 [details] File: journalctl_xorg-x11-server-Xwayland-21.1.0-1.5test
Ok, I think that's useful: eglstream: Failed to create EGLSurface for pixmap size [542x560], error 0x321C 0x321C is EGL_BAD_STATE_KHR. - EGL_BAD_STATE_KHR is generated if <stream> is not in state EGL_STREAM_STATE_CONNECTING_KHR. Next step will be to find out what the state is then…
Can you please redo the same with this new build: https://koji.fedoraproject.org/koji/taskinfo?taskID=65011837 This will log the error and the state as well in plain text. Thanks again for your help!
Apr 02 14:16:45 fedora pipewire-pulse[2010]: pulse-server 0x55aac5d19470: [Firefox] UNDERFLOW channel:3 offset:165151792 underrun:1880 Apr 02 14:17:33 fedora gnome-shell[1877]: Window manager warning: WM_TRANSIENT_FOR window 0x1204b90 for 0x1204ba0 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120390d. Apr 02 14:18:16 fedora gnome-shell[2634]: eglstream: Failed to create EGLSurface for pixmap Apr 02 14:18:16 fedora gnome-shell[2634]: eglstream: error 0x321C: EGL_BAD_STATE_KHR Apr 02 14:18:16 fedora gnome-shell[2634]: eglstream: stream state 0x321A: EGL_STREAM_STATE_DISCONNECTED_KHR Apr 02 14:18:26 fedora gnome-shell[1877]: Window manager warning: WM_TRANSIENT_FOR window 0x1204bfe for 0x1204c07 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120390d. Apr 02 14:18:27 fedora gnome-shell[1877]: Window manager warning: WM_TRANSIENT_FOR window 0x1204bfe for 0x1204c13 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120390d. Apr 02 14:19:24 fedora pipewire-pulse[2010]: pulse-server 0x55aac5d19470: [Firefox] UNDERFLOW channel:3 offset:55753688 underrun:1880 Apr 02 14:19:57 fedora gnome-shell[2634]: eglstream: Failed to create EGLSurface for pixmap Apr 02 14:19:57 fedora gnome-shell[2634]: eglstream: error 0x321C: EGL_BAD_STATE_KHR Apr 02 14:19:57 fedora gnome-shell[2634]: eglstream: stream state 0x321A: EGL_STREAM_STATE_DISCONNECTED_KHR Apr 02 14:20:58 fedora gnome-shell[1877]: Window manager warning: WM_TRANSIENT_FOR window 0x1205364 for 0x120537f window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120390d.
There it is… eglstream: Failed to create EGLSurface for pixmap eglstream: error 0x321C: EGL_BAD_STATE_KHR eglstream: stream state 0x321A: EGL_STREAM_STATE_DISCONNECTED_KHR https://www.khronos.org/registry/EGL/extensions/KHR/EGL_KHR_stream.txt EGL_STREAM_STATE_DISCONNECTED_KHR - either the producer or the consumer (or both) are no longer connected to the EGLStream (e.g. because they have been destroyed). Once the EGLStream is in this state it will remain in this state until the EGLStream is destroyed. In this state only eglQueryStreamKHR and eglDestroyStreamKHR are valid operations. […] EGL_STREAM_STATE_DISCONNECTED_KHR Occurs when the producer or consumer is destroyed or is otherwise unable to function normally. […] Once an EGLStream is connected to a producer it will remain connected to the same producer until the EGLStream is destroyed. If the producer is destroyed then the EGLStream's state will become EGL_STREAM_STATE_DISCONNECTED_KHR (refer to "3.10.4.3 EGL_STREAM_STATE_KHR Attribute").
Hi, I've posted a new build here: https://koji.fedoraproject.org/koji/taskinfo?taskID=65032761 This is complete shot in the dark, please let me know if that helps (or it could as well makes things a lot worse…)
*** Bug 1945961 has been marked as a duplicate of this bug. ***
Well... Not much changed. Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Failed to create EGLSurface for pixmap Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: error 0x321C: EGL_BAD_STATE_KHR Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: stream state 0x3215: EGL_STREAM_STATE_CREATED_KHR Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover... Apr 03 16:28:16 fedora gnome-shell[7963]: eglstream: Stream disconnected, trying to recover...
*** Bug 1954413 has been marked as a duplicate of this bug. ***
*** Bug 1955497 has been marked as a duplicate of this bug. ***
This test build should fix the crash and help with rendering issues: https://koji.fedoraproject.org/koji/taskinfo?taskID=67142225
Similar problem has been detected: Running GNOME with Wayland, using nvidia proprietary driver. Start VLC with a MP4. Must be longer than 1 minute. Pick a time further away from 'now' on the time line. Succeeded to reproduce with jumps >= 60 seconds. --> wayland crashes and vlc crashes with it xorg-x11-server-Xwayland-21.1.1-1.fc34.x86_64.rpm vlc-3.0.12.1-9.fc34.x86_64.rpm vlc-core-3.0.12.1-9.fc34.x86_64.rpm akmod-nvidia-465.27-1.fc34.x86_64.rpm (summary: latest F34 as of May, 2nd, 2021) reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1014.slice/user/session.slice/org.gnome.Shell cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1014/.mutter-Xwaylandauth.ZBV120 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 crash_function: xwl_log_handler executable: /usr/bin/Xwayland journald_cursor: s=5c859fa8898c448da78168d54a6a8095;i=bd0a8;b=68a21d455ed948acb4d9fd7f57255dbf;m=9ce2cbda2;t=5c16fcdf60031;x=2efe23f398e734ae kernel: 5.11.17-300.fc34.x86_64 package: xorg-x11-server-Xwayland-21.1.1-1.fc34 reason: Xwayland killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1014
*** Bug 1956612 has been marked as a duplicate of this bug. ***
*** Bug 1957148 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Starting Gnome 40 with NVIDIA drivers and using Wayland. X-Server seems to be fine and running... however I notice hang of whole graphical session. reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-42.slice/session-c3.scope cmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth /run/user/42/.mutter-Xwaylandauth.AGF720 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 crash_function: xwl_log_handler executable: /usr/bin/Xwayland journald_cursor: s=06dfdcb0428248c291be069809acce61;i=159c;b=05a0ee564cf44509822e4128d93ea5b8;m=2a5f34c9;t=5c19b8edddc93;x=28b0873a892312d2 kernel: 5.11.17-300.fc34.x86_64 package: xorg-x11-server-Xwayland-21.1.1-1.fc34 reason: Xwayland killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 42
(In reply to Johannes Rest from comment #53) > Starting Gnome 40 with NVIDIA drivers and using Wayland. X-Server seems to > be fine and running... however I notice hang of whole graphical session. If Xwayland runs fine and the whole session hangs then it's definitely not a dupe of this bug.
Similar problem has been detected: It crashed probably when I touched the docking, trying to disconnect reconnect the DP cable. reporter: libreport-2.14.0 backtrace_rating: 4 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.0DJW20 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 crash_function: xwl_log_handler dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-21.1.1-1.fc34.x86_64 (Fedora Project) 1619621868 executable: /usr/bin/Xwayland journald_cursor: s=dee5ed14f9984f16a1ad57f6533e9eef;i=5189c2;b=73250447bd594344a9d3253d22424840;m=afeb462e4;t=5c18f7df9d1b1;x=ae07acc6d84fdef0 kernel: 5.11.17-300.fc34.x86_64 package: xorg-x11-server-Xwayland-21.1.1-1.fc34 reason: Xwayland killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Important: Please, do not mark all bugs pointing at an abort in `xwl_log_handler()` as a duplicate of this bug without tangible data showing this is the same issue. This issue here is about a very specific issue with the NVidia closed source driver described in comment 12 which finds its roots in a bug in egl-wayland. `xwl_log_handler()` is a function that gets called every time either a protocol or a communcation error occurred with the Wayland compositor, just a backtrace pointing at `xwl_log_handler()` does not mean this is the same issue, you need to check the actual journalctl logs for the the actual error.
(In reply to Olivier Fourdan from comment #56) > Important: > > Please, do not mark all bugs pointing at an abort in `xwl_log_handler()` as > a duplicate of this bug without tangible data showing this is the same issue. > > This issue here is about a very specific issue with the NVidia closed source > driver described in comment 12 which finds its roots in a bug in egl-wayland. > > `xwl_log_handler()` is a function that gets called every time either a > protocol or a communcation error occurred with the Wayland compositor, just > a backtrace pointing at `xwl_log_handler()` does not mean this is the same > issue, you need to check the actual journalctl logs for the the actual error. Thanks for your input! In my case it's the bug reporting tool who said that (after some struggles, unable to generate strace, downloading about 4GB of packages to generate the strace locally, failing to upload...). See some extract: ... Missing debuginfo file: /usr/lib/.build-id/1e/0c79b50f3a5f0b4b055854f4826458fbda3c58.debug Generating backtrace Backtrace is generated and saved, 60194 bytes --- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla Duplicate bugzilla bug '#1943936' was found Searching for updates No updates for this package found --- Running report_Bugzilla --- Logging into Bugzilla at https://bugzilla.redhat.com Checking for duplicates Bug is already reported: 1955497 Bug 1955497 is a duplicate, using parent bug 1943936 ... I will check carefully next times.
Precisely, the backtrace is not very useful there, please check your journalctl logs at the time of the issue and look for the actual errors (see comment 12).
FEDORA-2021-d204e31fb5 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d204e31fb5
Similar problem has been detected: Al instalar actualizaciones desde la app de software reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-42.slice/session-c1.scope cmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth /run/user/42/.mutter-Xwaylandauth.U7ZF30 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 crash_function: xwl_log_handler executable: /usr/bin/Xwayland journald_cursor: s=f7a82618ca8f44aa91c7124d59132237;i=20c71;b=c41dd8d212804fd9aa06be62f69f5d66;m=518feb5;t=5c1c28ed6b3ed;x=94ddc91ceb74405c kernel: 5.11.17-300.fc34.x86_64 package: xorg-x11-server-Xwayland-21.1.1-1.fc34 reason: Xwayland killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 42
FEDORA-2021-d204e31fb5 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d204e31fb5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d204e31fb5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Similar problem has been detected: Al instalar por consola actualizaciones(rpmfusion) para activar el wifi y se corrgiera el problema del bluetooh, que siguieron igual sin funcionar reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-42.slice/session-c1.scope cmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth /run/user/42/.mutter-Xwaylandauth.H4U020 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 crash_function: xwl_log_handler executable: /usr/bin/Xwayland journald_cursor: s=f7a82618ca8f44aa91c7124d59132237;i=23121;b=5246b8f1d6124ae392b039ac815200a4;m=40b438d;t=5c1d5aa572002;x=e5cbf9c66612808 kernel: 5.11.17-300.fc34.x86_64 package: xorg-x11-server-Xwayland-21.1.1-1.fc34 reason: Xwayland killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 42
FEDORA-2021-d204e31fb5 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
Similar problem has been detected: probably connecting a Dell USB-C Dock with 2 Daisychained DisplayPort Monitors reporter: libreport-2.15.2 backtrace_rating: 4 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.1UES70 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 crash_function: xwl_log_handler dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-21.1.2-1.fc34.x86_64 (Fedora Project) 1626104196 executable: /usr/bin/Xwayland journald_cursor: s=dff16b14fb4040829f89f16f2e793fa1;i=a1a8d;b=7301b816acfc4536bf2b1e8dad6cc454;m=21e4be70c;t=5c8596de17e70;x=3c5815843084d5fd kernel: 5.13.5-200.fc34.x86_64 package: xorg-x11-server-Xwayland-21.1.2-1.fc34 reason: Xwayland killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Baseus CAHUB-I0G Enjoy Series USB-C / Type-C to HDMI x 2 + PD HD Intelligent HUB Adapter connected CAHUB-I0G With two hdmi displays connected [ 4450.290055] usb 1-2: New USB device found, idVendor=2109, idProduct=0102, bcdDevice=12.24 [ 4450.290077] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 reporter: libreport-2.15.2 backtrace_rating: 4 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.COMW80 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 crash_function: xwl_log_handler dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-21.1.2-1.fc34.x86_64 (Fedora Project) 1628591143 executable: /usr/bin/Xwayland journald_cursor: s=a387a8e756ca463390524bb3de69049c;i=1158c;b=dbf26e7451914b168514fdd0ab9d5c57;m=c6a7881b;t=5cab10b92cda6;x=274904bb28c0220a kernel: 5.11.12-300.fc34.x86_64 package: xorg-x11-server-Xwayland-21.1.2-1.fc34 reason: Xwayland killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1998887 has been marked as a duplicate of this bug. ***
*** Bug 2004258 has been marked as a duplicate of this bug. ***
*** Bug 2005171 has been marked as a duplicate of this bug. ***
*** Bug 2010249 has been marked as a duplicate of this bug. ***
*** Bug 2011766 has been marked as a duplicate of this bug. ***
*** Bug 2016011 has been marked as a duplicate of this bug. ***
*** Bug 2016819 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Error occours while notebook Lenovo Thinkpad X11 carbon 20KH is connected to its Thinkpad ultra docking station (model 40AJ). This morning I noticed no audio auput from the ell monitor connected via DP to the docking station, just a few minutes after booting. Powering off the monitor (from the control switch, not unplugging from the AC outlet) Wayland freezed and I had to disconnect the notebook from the dock and opening a new graphical console (CTRL-ALT-F2), then going back to CRTL_ALT-F1 and login to gdm again. Wayland usually freezes when resuming from standby or suspend while connected to the dock, or if trying to connect the notebook to the dock while powered on. If I need to bring the X1 with me for a while, I can't use the dock again, unless (as I'm forced to do) I power it off before connecting. Bug occours with a different monitor connected to the HDMI port on the dock too BTW, Fedora was upgraded from 34 to 35, even if the crash report title refers to fc34 package (xorg-x11-server-Xwayland-21.1.4-1.fc35.x86_64 is currently installed). I can make some tests if needed. reporter: libreport-2.15.2 backtrace_rating: 4 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.Y3EJA1 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 crash_function: xwl_log_handler dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-21.1.2-1.fc34.x86_64 (Fedora Project) 1626123963 executable: /usr/bin/Xwayland journald_cursor: s=a11fe9b559c048a982b708753a814ba9;i=283e8;b=d3599d596ed94dfb8851c38a48db236f;m=3f5de37f9;t=5cdd51a6a464c;x=69c1b049d5a02178 kernel: 5.14.9-200.fc34.x86_64 package: xorg-x11-server-Xwayland-21.1.2-1.fc34 reason: Xwayland killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 2071388 has been marked as a duplicate of this bug. ***