Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

liferea crashes on Wayland #1378

Open
bruce-awareit opened this issue Aug 28, 2024 · 7 comments
Open

liferea crashes on Wayland #1378

bruce-awareit opened this issue Aug 28, 2024 · 7 comments
Assignees
Labels

Comments

@bruce-awareit
Copy link

bash> liferea --debug-gui

Gdk-Message: 22:41:41.607: Error 71 (Protocol error) dispatching to Wayland display.

@lwindolf
Copy link
Owner

I cannot reproduce this. Running for a long time on Wayland. Which Liferea version and Linux distro are you using?

Can you please rerun with

WAYLAND_DEBUG=1 liferea

this might give more info on why Wayland refuses starting.

@lwindolf
Copy link
Owner

https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/5 hints on this being an NVidia driver issue. This can be tested by launching with

GSK_RENDERER=gl liferea

@bruce-awareit
Copy link
Author

$ uname -r
6.10.6-arch1-1

$ LANG=C GSK_RENDERER=gl liferea
Gdk-Message: 21:10:24.089: Error 71 (Protocol error) dispatching to Wayland display.

$ LANG=C WAYLAND_DEBUG=1 liferea
.......
.......[1210922.613] {Default Queue} wl_surface#25.enter(wl_output#6)
[1210922.655] {Default Queue} -> wl_shm#5.create_pool(new id wl_shm_pool#49, fd 63, 9216)
[1210922.852] {Default Queue} -> wl_shm_pool#49.resize(27648)
[1210923.025] {Default Queue} -> wl_shm_pool#49.resize(64512)
[1210923.343] {Default Queue} -> wl_shm_pool#49.resize(138240)
[1210923.938] {Default Queue} -> wl_shm_pool#49.resize(285696)
[1210925.069] {Default Queue} -> wl_shm_pool#49.resize(580608)
[1210929.039] {Default Queue} -> wl_shm_pool#49.resize(1170432)
[1210934.193] {Default Queue} -> wl_shm_pool#49.resize(2350080)
[1210952.445] {Default Queue} -> wl_shm_pool#49.create_buffer(new id wl_buffer#50, 1594368, 48, 48, 192, 0)
[1210952.458] {Default Queue} -> wl_pointer#10.set_cursor(449, wl_surface#25, 3, 0)
[1210952.464] {Default Queue} -> wl_surface#25.attach(wl_buffer#50, 0, 0)
[1210952.469] {Default Queue} -> wl_surface#25.set_buffer_scale(2)
[1210952.472] {Default Queue} -> wl_surface#25.damage(0, 0, 24, 24)
[1210952.478] {Default Queue} -> wl_surface#25.commit()
[1210958.728] {Display Queue} wl_display#1.delete_id(47)
[1210958.738] {Display Queue} wl_display#1.error(wp_linux_drm_syncobj_surface_v1#30, 2, "Explicit Sync only supported on dmabuf buffers")
Gdk-Message: 21:08:05.789: Error 71 (Protocol error) dispatching to Wayland display.

@lwindolf
Copy link
Owner

@bruce-awareit Thanks for the trace and test with GSK_RENDERER. This is definitively a Wayland issue. A Google search turns up multiple other apps that are affected too. The Liferea code has no such low level stuff anyway, we just use GDK/GTK.

To workaround you could start Liferea with X11 backend like this

GDK_BACKEND=X11 liferea

I consider this bug report as wont-fix, but will leave it open for some time, so other affected users can easily find it.

@lwindolf lwindolf self-assigned this Aug 30, 2024
@hanikesn
Copy link

hanikesn commented Sep 4, 2024

__NV_DISABLE_EXPLICIT_SYNC=1 fixed the issue for me as well without falling back to X11

@bruce-awareit
Copy link
Author

__NV_DISABLE_EXPLICIT_SYNC=1

@hanikesn Thanks. It works for me, too.

@bruce-awareit
Copy link
Author

WEBKIT_DISABLE_DMABUF_RENDERER=1 fixed the issue for me as well in Wayland on Archlinux.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants