Skip to content
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

systemd-failed-units doesn't update #3444

Open
elliott-farrall opened this issue Jul 16, 2024 · 4 comments
Open

systemd-failed-units doesn't update #3444

elliott-farrall opened this issue Jul 16, 2024 · 4 comments
Labels
bug Something isn't working clock custom

Comments

@elliott-farrall
Copy link

I've been having issues with the systemd-failed-units module not updating. If I login with a failed unit then it will successfully report that failed unit. However, if I then restart that unit and it is no longer failing, the waybar module will not reflect this change until I next login (or restart waybar).

I'm not too familiar with the way the modules are implemented but I noticed that in the src for systemd-failed-units it doesn't implement the interval option. I have tried setting both interval and restart-interval and neither has made a difference. Based on this I assume that the module is supposed to continuously check the units without exiting.

Has anyone else had this issue? I have installed waybar via nixpkgs (unstable).

@github-actions github-actions bot added bug Something isn't working clock custom labels Jul 16, 2024
@RobertMueller2
Copy link
Contributor

Just tried it out and fixed a system error, the module was updated right away. It does so by handling DBus signals. No intervals needed. The module hasn't really changed since its inception. Theoretically nixpgks could have patched it, but I doubt it. So I'm probably using the same code.

The best idea I can offer for troubleshooting is to look at Waybar's output, see if there are any error messages.

@elliott-farrall
Copy link
Author

Sorry for the delayed response, just had another go at setting this up and still can't get the module to reflect any changes in the failed units without restarting waybar.

I suspect the issue is with the way waybar is packaged in nixpkgs so I will look into raising an issue there. I couldn't see anything to do with systemd in the output for waybar. I'm far from an expert when it comes to DBus signals; do you have any suggestions of where to look to see if waybar is actually getting these signals? I checked dbus.service at both system and user level and couldn't see anything related to waybar.

@elliott-farrall
Copy link
Author

After further experimentation I have found that this issue only occurs for user units.

@anarcat
Copy link

anarcat commented Jan 7, 2025

i can confirm that waybar doesn't notice resolution on failed user units.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working clock custom
Projects
None yet
Development

No branches or pull requests

3 participants