Hi everybody, this might have been overdue, as the changes have been made already. With the recent commits to mainly xorg repository, CRUX supports Wayland as a modern replacement for X11! The default is still X11, Wayland is purely optional at this point. If you want to try it out, I have imported contrib/sway as a i3 compatible Wayland alternative. This means you can carry over your i3 config to sway, if you have that. To my knowledge, tsaops kf5 repo should work fine, and jaegers mate repository should work too. If there are any questions/problems/hints/.., please post them here or preferably open a ticket on flyspray to make it easier to track. Personally I have been using wayland with sway for soon 2 years and have been more than happy with it. Best regards, Tim
Hello. Thank you for bringing Wayland support to CRUX. Here are my first impressions using "sway": - When moving the mouse pointer above the top bar of sway the top bar will crash with a segmentation fault. - When switching to another console with Ctrl-Alt-Fn the sway session will be terminated. I don't know if this is intended. - Besides from the two issues mentioned above it seems to work pretty well. Here some hints for others who want to try it: ------------------------------------------------------------------- input "type:keyboard" { xkb_layout de xkb_variant nodeadkeys } ------------------------------------------------------------------- This section in the sway config file will enable a german keyboard. Adjust to your preferred locale. ------------------------------------------------------------------- for_window [shell=".*"] title_format "%title :: %shell" ------------------------------------------------------------------- This line in sway config will show in the title bar of an application window if it runs with "xwayland" or natively ("xdg_shell"). I wrote a small shell script to start sway from terminal more simply: ------------------------------------------------------------------- #!/bin/bash export MOZ_ENABLE_WAYLAND=1 if [ ! -d /tmp/markus ]; then mkdir /tmp/markus fi chmod 700 /tmp/markus export XDG_RUNTIME_DIR=/tmp/markus sway ------------------------------------------------------------------- The MOZ_ENABLE_WAYLAND variable will make firefox run natively on wayland. The sway session can be exited gracefully with Windowskey-Shift-e if not configured otherwise. Best regards Markus Heinz
On 2021-09-22 22:53:26, Markus Heinz wrote:
Thank you for bringing Wayland support to CRUX.
Completely agreed. Thanks much Tim, and thanks Markus for getting us started on tips 'n tricks!
Here are my first impressions using "sway":
- When moving the mouse pointer above the top bar of sway the top bar will crash with a segmentation fault.
I also ran into this. If you run sway with `dbus-run-session sway` rather than just `exec sway`, this fixes the issue. There is a relevant bug over on the Alpine linux bug tracker for this: https://gitlab.alpinelinux.org/alpine/aports/-/issues/10673 Additionally, for folks who modified their touchpad or keyboard behavior within their .xinitrc file, you can now do this with the `input type:*` items like Markus mentioned. I added these in my sway config: # Configure the touchpad input type:touchpad { dwt enabled tap enabled natural_scroll enabled pointer_accel 0.4 } # Configure the keyboard input type:keyboard { repeat_delay 250 repeat_rate 100 } Finally, if you are having trouble getting gtk themes to apply successfully (expecting the gtkrc-2.0 and gtk3 settings.ini files to work), it seems there is a known bug with GTK+ and how it interacts with Wayland. The workarounds can be found here: https://github.com/swaywm/sway/wiki/GTK-3-settings-on-Wayland But in short, throw this in your startup wrapper script to apply themes, fonts, icons, etc at runtime (modify as needed). gsettings set org.gnome.desktop.interface gtk-theme 'Pop-dark' gsettings set org.gnome.desktop.interface icon-theme 'Papirus' gsettings set org.gnome.desktop.interface font-name 'Iosevka Aile 12' Thanks for the great work on Crux! -- Aaron Ball :: https://oper.io \0
Hello.
On 2021-09-22 22:53:26, Markus Heinz wrote:
- When moving the mouse pointer above the top bar of sway the top bar will crash with a segmentation fault.
I also ran into this. If you run sway with `dbus-run-session sway` rather than just `exec sway`, this fixes the issue.
There is a relevant bug over on the Alpine linux bug tracker for this: https://gitlab.alpinelinux.org/alpine/aports/-/issues/10673
Thank you for sorting this one out. My start script now looks like this: ----------------------------------------------------------------------- #!/bin/bash export MOZ_ENABLE_WAYLAND=1 export _JAVA_AWT_WM_NONREPARENTING=1 if [ ! -d /tmp/${USER} ]; then mkdir /tmp/${USER} fi chmod 700 /tmp/${USER} export XDG_RUNTIME_DIR=/tmp/${USER} exec dbus-run-session --dbus-daemon=/usr/sbin/dbus-daemon sway ----------------------------------------------------------------------- Best regards Markus Heinz
Hello.
- When switching to another console with Ctrl-Alt-Fn the sway session will be terminated. I don't know if this is intended.
It's a bug which is desribed here: <https://github.com/swaywm/wlroots/issues/3200> I tried the mentioned patch and it resolves the issue for me. As attachment the modified seatd port. After updating you need to restart seatd service if it's running already. I forgot this on first try with the result that all consoles were messed up and I had to restart my computer. Best regards Markus Heinz
participants (3)
-
Aaron Ball -
Markus Heinz -
tbier＠posteo.de