Greetings,
Let's start this message from the good news: Fedora 34 was released with Sway 1.6 available as a day 0 update. We're getting a lot of bugfixes, shiny new wlroots DRM renderer backend, and of course new bugs :)
## Upstream release notes:
- https://github.com/swaywm/sway/releases/tag/1.6 - https://github.com/swaywm/wlroots/releases/tag/0.13.0
## Default configuration changes for Fedora package:
A couple of configuration snippets are now provided by the optional dependency sway-systemd:
- `/etc/sway/config.d/10-systemd-session.conf` - configures systemd user session environment - `/etc/sway/config.d/10-systemd-cgroups.conf` - configures automatic management of cgroups for GUI applications in sway session (#1935923)
Detailed documentation: https://github.com/alebastr/sway-systemd/blob/main/README.md
### Opt-in for users with custom config file:
`include /etc/sway/config.d/*` directive in the default configuration already includes these snippets. If you removed the line from your custom config file, you can restore it or just include the parts you want. (the configuration files may change in the future, so it is better to include them instead of copying the contents).
### Opt-out options:
- Remove `sway-systemd` package and add it to `excludepkgs` in the `fedora`, `updates` and `updates-testing` repository configuration - Remove `include` directives that match the files listed above from your sway config file. - Edit `/etc/sway/config.d/*.conf` files and comment all uncommented lines. Be aware that the future updates of sway-systemd package may create `/etc/sway/config.d/*.conf.rpmnew` files which are also sourced by sway
## grimshot
`grimshot` screenshot helper script from the sway/contrib source directory is now offered as a `grimshot` package. It provides several convenient wrappers around grim, slurp and wl-copy.
## xdg-desktop-portal-wlr 0.3.0
Just a heads up that the updated xdpw package now asks you to select the output you'd like to share. It does that using `slurp` though, so it's completely understandable if you get confused first time that happens :) See OUTPUT CHOOSER section of `man 5 xdg-desktop-portal-wlr` to configure alternative chooser command (dmenu, rofi, wofi, etc...).
Deprecation warning: if you have xdg-desktop-portal-wlr.service override with `-o` option for xdpw, you may want to remove it and use chooser or specify desired output as an option in the configuration file.
***
## Known issues:
- Sway may fail to start with *any* GPU (including integrated Intel) if the libs from the proprietary NVIDIA driver are installed. Even if the kernel module for NVIDIA driver is not loaded. Upstream link: https://github.com/swaywm/wlroots/issues/2480 Solution: ensure that libglvnd >= 1.3.2-4.fc34 is installed
- Artifacts and glitches with Nouveau open-source driver for NVIDIA cards. Upstream link: https://github.com/swaywm/sway/wiki#sway-16-shows-garbage-on-nouveau Solution: start sway with WLR_DRM_NO_MODIFIERS=1 environment variable, i.e. `env WLR_DRM_NO_MODIFIERS=1 /usr/bin/sway` Will be fixed with mesa 21.1.x update somewhere in May.
- Sway or any other wlroots-based compositor refuses to start on Allwinner SOC devices with `lima` open-source driver (PinePhone et al.). Upstream link: https://github.com/swaywm/wlroots/issues/2795 Solution: wait for mesa 21.1.x update somewhere in May. Meanwhile, sway-1.5.1 is still available in f34 repositories and should work on this hardware.
- Mouse cursor is not visible in some apps on a scaled output Upstream: https://gitlab.freedesktop.org/wayland/wayland/-/issues/194, https://github.com/swaywm/sway/issues/6166 Solution: a comment in the sway issue mentions that certain cursor themes are not affected. I cannot provide further guidance due to the lack of HiDPI display, so suggestions with the working cursor theme available from Fedora repositories are welcome.
- Applications started as a systemd user service are failing to connect to a wayland socket. Solution: see default configuration changes section above
- Sway with all applications is terminated on low memory condition. Solutions: a) remove systemd-oomd-defaults package to disable systemd OOM killer b) see default configuration changes section above
***
I'm certain that I forgot to mention a lot of things, so feel free to reply with the changes you consider important :)