wayfire: [backend/x11/backend.c:478] X11 does not support shared pixmaps
Hello.
I’m trying to configure Wayland and Wayfire on FreeBSD 14.0. You can find the whole configuration here :
https://pastebin.ubuntu.com/p/VtH2YZcfn6/
Expected behavior That is starts !
Screenshots or stacktrace
This is what happens when I run the wayfire script :
nano wayfire-start :
#!/bin/sh
exec dbus-launch --exit-with-session wayfire
=
[src/main.cpp:334] Starting wayfire version v0.8.0
[backend/x11/backend.c:395] Creating X11 backend
[backend/x11/backend.c:478] X11 does not support shared pixmaps
[backend/x11/backend.c:607] Failed to query DRI3 DRM FD
[src/main.cpp:134] Fatal error: Segmentation fault
#1 0x363b40 <main+0x1580> at /usr/local/bin/wayfire
#2 0x82d7db53f <pthread_sigmask+0x53f> at /lib/libthr.so.3
#3 0x82d7daafb <pthread_setschedparam+0x83b> at /lib/libthr.so.3
#4 0x820f1b2d3 <???> at ???
#5 0x82309b5d4 <wlr_backend_get_drm_fd+0x4> at /usr/local/wlroots016/lib/libwlroots.so.11
#6 0x362a3a <main+0x47a> at /usr/local/bin/wayfire
#7 0x82aeb7afa <__libc_start1+0x12a> at /lib/libc.so.7
**Wayfire version**
# pkg search wayfire
wayfire-0.8.0_3 3D Wayland compositor
wayfire-plugins-extra-0.8.0_1 Additional plugins for Wayfire
Keep in consideration that I don’t run the wayfire-start script on top of xorg. But WITHOUT launching it at all,even if I keep it installed on the system.
About this issue
- Original URL
- State: closed
- Created 4 months ago
- Comments: 38 (20 by maintainers)
XDG_RUNTIME_DIRon logoutenv LIBSEAT_BACKEND=consolekit2 ck-launch-session dbus-run-session wayfireXDG_RUNTIME_DIRHi, thanks for the detailed bug report. Unfortunately the error seems to come from wlroots (I suppose Wayfire could handle it and exit gracefully) but in any case there is nothing we can do on our side to actually fix it.
Are you trying to run Wayfire from within an existing X11 session? You ought to run Wayfire directly from a TTY, running from a x11 session is for testing purposes only.
I would also recommend installing wayfire-git (from source) and wlroots 0.17 if you can, because things may have already changed on the wlroots side, if this is a wlroots bug and not a misconfiguration on your side.