sddm VS Waybar

Well, it seems it is still considered experimental https://github.com/sddm/sddm/pull/1737

There are dozens of threads everywhere about it since around early 2021. KDE will take over the SDDM project and that bug fix may soon finally be up-streamed.

LMAO the login issue was this https://github.com/sddm/sddm/issues/1592

Wayland autologin does not work with sddm (if you're using such a configuration) https://github.com/sddm/sddm/issues/1676

Thanks everyone for your time - installing xorg-minimal solved the issue; next version should solve the issue topic discussed in sddm github. I leave the following here just in case someone with skill & time comes across - seems a bit of love would not hurt sddm: https://github.com/sddm/sddm/issues/1471

Relevant to your keyboard configuration issue: https://github.com/sddm/sddm/issues/703

Also fixed in -git

No, the picture shows that the login manager is still sddm, but somehow the login theme used by sddm has been reverted to the sddm default of the 'maui' instead of the 'breeze' theme used by default in Kubuntu. The package shipping the breeze theme (sddm-theme-breeze) may have become uninstalled, or sddm config changed somehow to not use breeze.

If I understand https://github.com/Alexays/Waybar/wiki/Configuration correctly, what is to be displayed is defined in a JSON file that can be located in one of the directories mentioned.

GNU calls their extensions "equivalent to" things I'd have suggested trying ($_I or $-l), but I'm not sure if the equivalents are themselves GNU extensions, too. Regardless, reading this Waybar Github issue about %OI, I get the impression there was a regression at some point, in any case on March 27th 2022 someone says it "used to work fine until recently".

hope it helps. source btw: https://github.com/Alexays/Waybar/issues/2177

{ config, pkgs, ... }: { wayland.windowManager.sway = let patchedWaybar = pkgs.waybar.overrideAttrs(prev: final: { patches = [ (pkgs.fetchpatch { url = "https://github.com/Alexays/Waybar/pull/2134.diff"; sha256 = "1hzdv3b8zzps50pdcb8pj9cxwaix4q2d4gsqb9dl9vflgl429hq3"; }) ]; }); in { enable = true; config.bars = [{ statusCommand = "${patchedWaybar}/bin/waybar"; }]; };

See this issue. CSS and only new properties in config are reloaded when SIGUSR2 is triggered.

I think this has just been added to waybar (wlr/workspaces) to work in a similar manner to how it is in sway/workspaces. No need for fake empty terminals. Something was merged for wwlr/workspaces in the waybar github. See - https://github.com/Alexays/Waybar/pull/2089.

Ah, well in looking at their git, it appears some do have fallback font issues. See here - https://github.com/Alexays/Waybar/issues/215