Description of problem: I ran discord with a command below. And my system froze. flatpak run com.discordapp.Discord --enable-features=UseOzonePlatform --enable-gpu --ozone-platform=wayland Version-Release number of selected component: xorg-x11-server-Xwayland-22.1.1-1.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1001.slice/user/session.slice/plasma-kwin_wayland.service cmdline: /usr/bin/Xwayland :1 -auth /run/user/1001/xauth_ieWwdd -listen 52 -listen 53 -displayfd 24 -rootless -wm 47 crash_function: PrivsElevated dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-22.1.1-1.fc36.x86_64 (Fedora Project) 1652220861 executable: /usr/bin/Xwayland journald_cursor: s=5b078f6faeca424f9d97b659f8e6f92d;i=3845;b=2ebedb39c817429eb2b539f06ef2a173;m=2065fac6;t=5df76291db8aa;x=bdab8c5de46a5e7a kernel: 5.17.8-300.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #10 xwl_screen_destroy_drm_lease_device at ../hw/xwayland/xwayland-drm-lease.c:430 #11 ffi_call_unix64 at ../src/x86/unix64.S:105 #12 ffi_call_int at ../src/x86/ffi64.c:672 #13 wl_closure_invoke at ../src/connection.c:1025 #14 dispatch_event at ../src/wayland-client.c:1583 #15 dispatch_queue at ../src/wayland-client.c:1729 #16 wl_display_dispatch_queue_pending at ../src/wayland-client.c:1971 #17 wl_display_dispatch_pending at ../src/wayland-client.c:2034 #18 xwl_read_events at ../hw/xwayland/xwayland-screen.c:482 #20 ospoll_wait at ../os/ospoll.c:657
Created attachment 1881636 [details] File: backtrace
Created attachment 1881637 [details] File: core_backtrace
Created attachment 1881638 [details] File: cpuinfo
Created attachment 1881639 [details] File: environ
Created attachment 1881640 [details] File: limits
Created attachment 1881641 [details] File: maps
Created attachment 1881642 [details] File: mountinfo
Created attachment 1881643 [details] File: open_fds
Created attachment 1881644 [details] File: proc_pid_status
Created attachment 1881645 [details] File: var_log_messages
The backtrace points at DRM lease code, were you using DRM lease (i.e. a virtual reality device) at some point? This comes to mind: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/894 Which would affect DRM lease and KDE plasma.
Can you please try this scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=87434411 You'll need to restart your session after installing.
Similar problem has been detected: I plugged in external monitors via a DisplayLink USB C dock. This crash is repeatable. reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/plasma-kwin_wayland.service cmdline: /usr/bin/Xwayland :1 -auth /run/user/1000/xauth_hXCwiK -listen 55 -listen 56 -displayfd 47 -rootless -wm 50 crash_function: PrivsElevated dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-22.1.1-1.fc36.x86_64 (Fedora Project) 1650911326 executable: /usr/bin/Xwayland journald_cursor: s=5105132aa5e94f589d051fcd33f5d33f;i=918d0;b=050ac6cde5db4ee0aab6cd352e0a3d0a;m=26d8a45;t=5df1c7d4602ff;x=63b4374b1fb0ed8c kernel: 5.17.6-300.spectre.fc36.x86_64 package: xorg-x11-server-Xwayland-22.1.1-1.fc36 reason: Xwayland killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
FEDORA-2022-0ee78d34e9 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0ee78d34e9
FEDORA-2022-0ee78d34e9 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-0ee78d34e9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0ee78d34e9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-0ee78d34e9 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.