Closed xinyifly closed 6 months ago
Can you try launching waybar in a terminal to see if there are any errors?
This looks like a home-manager issue, probably caused by some kind of race condition between waybar and sway. Since there is no further information, I will close this issue first.
@Aleksanaa Thank you for your clue of race condition, which inspired me checked failed systemd user units, I found that systemctl --user status xdg-desktop-portal-wlr.service
is complaining:
Mar 12 23:57:13 t8 systemd[2511]: Starting Portal service (wlroots implementation)...
Mar 12 23:57:13 t8 xdg-desktop-portal-wlr[25131]: 2024/03/12 23:57:13 [ERROR] - pipewire: couldn't connect to context
Mar 12 23:57:13 t8 xdg-desktop-portal-wlr[25131]: 2024/03/12 23:57:13 [ERROR] - xdpw: failed to initialize screencast
Mar 12 23:57:13 t8 xdg-desktop-portal-wlr[25131]: 'impl->enter_count > 0' failed at ../spa/plugins/support/loop.c:362 loop_leave()
And finally found adding services.pipewire.enable = true;
to configuration.nix
solved this issue.
Describe the bug
After I upgraded from 23.05 to 23.11, my configured waybar in sway does not launch automatically untill I reload sway several times.
Steps To Reproduce
Steps to reproduce the behavior:
wayland.windowManager.sway.config.bars = [{ command = "${pkgs.waybar}/bin/waybar"; }];
Expected behavior
Waybar is not displayed.
Screenshots
Under 23.11
Under 23.05
Additional context
Related configuration.nix
I didn't see any waybar process running on startup while it exists under 23.05
Notify maintainers
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Add a :+1: reaction to issues you find important.