-
Notifications
You must be signed in to change notification settings - Fork 170
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
[backend/x11/backend.c:478] X11 does not support shared pixmaps #2171
Comments
Hi, 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. |
Hello. Thanks for the fast reply. I'm using wlroots-0.17.1 : is this still good ? Between the ports I also have some old versions,but I don't know if they will work as they are marked as deprecated :
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. Installing wayfire-git (from source) on FreeBSD may be impossible without patching it,I suppose. |
You may have it installed, but you will need a newer Wayfire version (currently wayfire-git) for it. I'm looking at this line:
Which seems to indicate Wayfire is using the wlroots 0.16 (which is indeed the version supported by the last release). If you have wlroots 0.17 it should be relatively easy to install Wayfire from source though - wlroots is the main dependency and because of it people usually have to compile manually also its dependencies like newer wayland-server, etc. but you should already have compatible versions installed since you have wlroots 0.17. |
So,what ? everything seems to be fine. But I'm not able to run WayFire. So,what should I do ? |
Install wayfire-git from source :) https://github.com/WayfireWM/wayfire?tab=readme-ov-file#installation Before you do that, maybe you can try forcing wlroots to use the DRM backend as that's what you want if you run from a tty. |
|
maybe the nvidia driver is not good ?
|
So, the error is indeed that wlroots cannot find a suitable GPU device. Check out the nvidia docs: https://download.nvidia.com/XFree86/Linux-x86_64/510.39.01/README/gbm.html I personally have never tested Wayfire on Nvidia but I have heard of users who have managed to run it, so probably there is some way to configure your driver. |
ok. this is what happens after the installation of wayfire 0.9 :
|
Can I upgrade wlroots to a new version ? |
wlroots 0.17 is the newest release. Did you see my earlier comment? You may be missing some nvidia settings. |
wlroots 0.17.x is the latest wayfire currently supports. Either way, the problem is with the graphics driver. As far as I understand, the GBM requirements are satisfied only with later proprietary driver versions and do not support some cards. Make sure to check the link @ammen99 posted. The other option is to use nouveau, which means removing the proprietary driver and just using mesa. |
The tutorial says to load these modules on /etc/rc.conf :
and I did it. Infact all those modules are in memory :
|
I have no idea which tutorial you are following. Do you have a link? Also loading the modules might not be enough, see the docs I attached. |
This tutorial : https://www.youtube.com/watch?v=5vHdJ5-drMs anyway he followed the FreeBSD handbook to create that video. He did a good work. Maybe some crucial info is missing directly from the FreeBSD handbook ? Infact it works for him,but not for me. |
I don't know what the difference is, but reading the official docs says you need to set a certain parameter to the kernel module. https://download.nvidia.com/XFree86/Linux-x86_64/550.54.14/README/kms.html
|
Or maybe missing the nvidia gbm module? |
Thanks to @ammen99 I found the error. You told me how to configure the nvidia driver as if I was using Linux,but I'm using FreeBSD. BTW I have translated your suggestion to adapt it for FreeBSD and I've understood where it was the error. When I have installed the driver nvidia-drm-515-kmod-550.54.14,the script said :
So I have added this parameter to sysctl.conf :
unfortunately my system does not accept it as is because it says that this is a tunable setting,so it should be put on /boot/loader.conf. I did it and it almost worked :
EE 02-03-24 20:36:03.226 - [src/main.cpp:59] Unable to drop root (we shouldn't be able to restore it after setuid), refusing to start Almost because I still need to fix the last error...maybe it is caused by another error that I see on the dmesg :
This is where the error originates :
(I'm using the zsh shell). Just a little bit of help and I will be able to make it. |
Have you tried running wayfire as user? It would need patching to run as root. |
I'm close to run Wayland + wayfire successfully,but not yet. This is what happens when I run the wayfire-start script :
as user : https://pastebin.ubuntu.com/p/hDCPHjWSj2/ any idea about how to fix it ? thanks. |
You probably need to give your user permissions to write in the directory where the socket files are created, because it says:
|
Also, does your user have ID 1001 or 1000? The |
I think this is the portion of the tutorial involved in the error :
as user this is what reports the id command (when I run xfce and xorg) :
|
I suspect that there isn't a permission problem,but something else. When I log out from xfce4 and from xorg,this is what I see (as user) :
I don't see 1001. Is that normal ? I'm using zsh.
|
Have you tried manually creating the directory? Note that on my Linux Distro (Fedora) the directory is created automatically and I suppose the same is true for many other distributions. Unfortunately, I cannot help much with *BSD but you should be able to find some documentation of what system component(s) are responsible for creating this directory. |
|
@Marietto2008 those images make it really hard to read what is going on, and maybe some messages are missing (happens a lot on ttys). You can redirect the output to a file, for example: |
Do the consolekit messages (dbus stuff) come out when starting Wayfire, or only when you stop it? |
I've removed wayfire 0.9 and reinstalled wayfire 0.8 and the conflict with the plugin libfollow-focus is gone. I've also changed the values connected to my monitor from DP-3 to HDMI-A-1 ,as follows :
I've used HDMI-A-1 because the log says that my screen is connected to the port HDMI-A-1. This is also what I did :
wf-shell appeared,but my mouse does not work,I can't use wcm to configure the panel if the mouse does not move ; internet connection also does not work. This is the log file : |
@Marietto2008 for the mouse issue, are you sure that the mouse does not work at all? Maybe it is simply invisible: https://github.com/WayfireWM/wayfire/wiki/FAQ#2-the-mouse-cursor-is-invisible For the internet connection, you need to have NetworkManager, that's currently the only supported backend by wf-panel. I suppose that the issue that you had with the git build is that you had configured the wrong output. Anyway, if you decide you to go back to the -git build, you may also need to compile wayfire-plugins-extra-git where some of the plugins are located (like follow-focus). |
Bingo. My mouse works now. This is the start script which works good :
the last problems : the keyboard mapping is the english one,but I would like the italian. And the wf-shell is on top of the screen,I would like to have it at the bottom. |
Take a look at wf-shell's config file :) By default,
For input to the applications, you can set the For the compositor shortcuts (things like alt-tab, KEY_E to toggle expo, etc) they are defined according to the hardware keyboard layout (which usually is english, QWERTY) - but you can rebind them in the config file. |
Im trying to configure wayfire using the wayfire config manager,but I see that the changes I made don-t stick. Do you know why ? |
Which changes? Output layout changes are done with an external tool and they won't survive a compositor restart. The rest should actually be written to the config file .. You can try and manually inspect the config file(s) to see what is being written to them. |
Im trying to change the keyboard layout from us to it. Ive changed a lot of parameters,but the keyboard mapping is still configured as us. Can you tell me what-s the exact parameters to change please ? thanks. This is what I did :
nope,this does not work. The keyboard mapping is still configured as us. |
Closing as the remaining issue is tracked in #2178 |
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 :
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.
The text was updated successfully, but these errors were encountered: