Version-Release number of selected component: xorg-x11-server-Xwayland-21.1.4-1.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cmdline: /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.U1MYI1 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 crash_function: xwl_log_handler dso_list: /usr/bin/Xwayland xorg-x11-server-Xwayland-21.1.4-1.fc35.x86_64 (Fedora Project) 1641350700 executable: /usr/bin/Xwayland journald_cursor: s=05f74a5be53b407d99095b4647569c9b;i=e26866;b=7010d0f19b2b4a66bbdaa309904b9fa1;m=2d405e3b42;t=5d9f61d8e4b94;x=38a10d40b15272f5 kernel: 5.16.12-200.fc35.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1943936
Created attachment 1865534 [details] File: backtrace
Created attachment 1865535 [details] File: cgroup
Created attachment 1865536 [details] File: core_backtrace
Created attachment 1865537 [details] File: cpuinfo
Created attachment 1865538 [details] File: environ
Created attachment 1865539 [details] File: limits
Created attachment 1865540 [details] File: maps
Created attachment 1865541 [details] File: mountinfo
Created attachment 1865542 [details] File: open_fds
Created attachment 1865543 [details] File: proc_pid_status
Created attachment 1865544 [details] File: var_log_messages
From attachment 1865544 [details]: > wl_display@1: error 1: invalid arguments for zwp_linux_buffer_params_v1 Which hardware/driver are you using?
> Which hardware/driver are you using? I assume you are asking about the GPU. Hardware: AMD Radeon R9 290X Sapphire Tri-X (8GB) Kernel driver in use: amdgpu
Ah thanks! So this is Wayland error with the first parameter of zwp_linux_buffer_params_v1:add(). As it turns out, the first parameter is a file descriptor. Which version of wayland are you using? (I suspect this is similar to bug 2062030).
> Which version of wayland are you using? libwayland-server-1.20.0-1.fc35.x86_64 Since the crash occurs about once a day i'll also downgrade to libwayland-server-1.19.0-2.fc35 and see if this changes in the next days.
(In reply to Kevin Weis from comment #15) > > Which version of wayland are you using? > > libwayland-server-1.20.0-1.fc35.x86_64 > > Since the crash occurs about once a day i'll also downgrade to > libwayland-server-1.19.0-2.fc35 and see if this changes in the next days. I wouldn't recommend downgrading, it can break newly build binaries (see https://bugzilla.redhat.com/show_bug.cgi?id=2062030#c16) Can you instead try the scratch build I ran: https://koji.fedoraproject.org/koji/taskinfo?taskID=83954399 (Note, being a scratch build, it will be automatically removed after some time)
> I wouldn't recommend downgrading, it can break newly build binaries Ahh, good to know thanks! > Can you instead try the scratch build I ran I've never installed something from a scratch build, do i just download and install the listed .rpm packages manually?
> I've never installed something from a scratch build, do i just download and install the listed .rpm packages manually? Yes, either you download everything for your arch locally and run `rpm -Fvh *.rpm` (`-F` for “freshen”) you can use rpm directly with the URL for the packages, e.g. for x86_64: $ sudo rpm -Fvh \ https://kojipkgs.fedoraproject.org//work/tasks/4447/83954447/libwayland-client-1.20.0-1.1test.fc35.x86_64.rpm \ https://kojipkgs.fedoraproject.org//work/tasks/4447/83954447/libwayland-cursor-1.20.0-1.1test.fc35.x86_64.rpm \ https://kojipkgs.fedoraproject.org//work/tasks/4447/83954447/libwayland-egl-1.20.0-1.1test.fc35.x86_64.rpm \ https://kojipkgs.fedoraproject.org//work/tasks/4447/83954447/libwayland-server-1.20.0-1.1test.fc35.x86_64.rpm \ https://kojipkgs.fedoraproject.org//work/tasks/4447/83954447/wayland-devel-1.20.0-1.1test.fc35.x86_64.rpm \ https://kojipkgs.fedoraproject.org//work/tasks/4447/83954447/wayland-doc-1.20.0-1.1test.fc35.noarch.rpm Downloading the packageslocally first has the advantage to have them at hamd, because scratch builds get erased automatically after a little while.
Thanks, i've installed the scratch build packages and have a local copy of them.
Just to be sure, you'll need to restart your session for these to take effect. Please let me know how that goes!
*** Bug 2065485 has been marked as a duplicate of this bug. ***
*** Bug 2068320 has been marked as a duplicate of this bug. ***
Similar problem has been detected: X11 applications like Thunderbird and Java applications like Android Studio start crashing after a few hours of usage. Trying to restart them sometine is unsuccesful or crash after a few seconds again of a window being displayes. Thunderbird logs error about channel problems for example: mozilla-thunderbird.desktop[4496]: Exiting due to channel error I have to restart the machine to be able to continue working. It must be caused by a recent update (a few weeks) that I have been unable to identify yet. 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.USSLJ1 -listenfd 4 -listenfd 5 -displayfd 6 -initfd 7 crash_function: xwl_log_handler executable: /usr/bin/Xwayland journald_cursor: s=9fe2ff4171d5405a9b8a9ff6a2e945f6;i=231a95;b=83161fccf4aa4c96b8b1f23563920794;m=17d267537;t=5daf8034c6b40;x=631f01f7df255168 kernel: 5.16.16-200.fc35.x86_64 package: xorg-x11-server-Xwayland-21.1.4-1.fc35 reason: Xwayland killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
I just installed the scratch build packages. The problem should manifest tomorrow if not fixed, I will report back in a few days.
Since installing the the scratch build packages i've had no crash.
Same here, I had an entire day at the office without a single X11 application crash. It only needed a few ours of usage for applications to start crashing.
I installed 1.20.0-1.fc35.x86_64 from the offical update repositories, but it seems that these are different versions. Is it possible to get the scratch version again ?
I still have the scratch build packages locally (wayland-1.20.0-1.1test.fc35.x86_64), is it okay if i upload them here or on one of my servers and post a link?
There should be a scratch build (for the CI) in the merge request I posted as well: https://src.fedoraproject.org/rpms/wayland/pull-request/2
(But it's for rawhide)
From my side, I also would take your server :-). I will check this bug report and give feedback, when I downloaded the files Thanks a lot.
@anton.clemens.bors here: https://compilenix.org/static/wayland-1.20.0-1.1test.fc35.x86_64/
I posted an update here: rawhide: https://bodhi.fedoraproject.org/updates/FEDORA-2022-237a9785ac F36: https://bodhi.fedoraproject.org/updates/FEDORA-2022-157d79b1ab F35: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ca717e6f35 F34: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9d2bca3d15 If that solves the issue, we should just close this bug as a duplicate of bug 2062030.
@red-hat-bugzilla-s0hdudiv thank you for the files. I got them.
*** Bug 2070413 has been marked as a duplicate of this bug. ***
closing as duplicate of bug 2062030 which is solved with wayland 1.20.0-4 *** This bug has been marked as a duplicate of bug 2062030 ***
*** Bug 2090165 has been marked as a duplicate of this bug. ***