Describe the bug
Confirmed fix is to downgrade sdbus-cpp to 2.2.1 for now until hypridle maintainers release an update where they rebuild with the newer sdbus-cpp 2.3.0
Summary
After a routine system upgrade, hypridle crashes immediately on every launch
with SIGSEGV. The screen no longer locks, dims, or suspends on idle, and the
ML4W waybar hypridle module stays red. Clicking the waybar
module to toggle it does nothing because the daemon dies the instant it starts.
This is not an ML4W config bug. Root cause is an sdbus-cpp ABI break:
sdbus-cpp was upgraded 2.2.1 -> 2.3.0 while hypridle was not rebuilt against
it.
Filing here because every ML4W + Arch user will hit this after an update,
and a known-issue note / workaround in the docs would save people a lot of
debugging.
Steps to reproduce
Issue is evident on startup
Expected behavior
hypridle works
Screenshots
No response
Distribution
Arch Linux
If Other, specify
No response
Additional context
No response
Code of Conduct
Describe the bug
Reference Issue: hyprwm/hypridle#200
Confirmed fix is to downgrade sdbus-cpp to 2.2.1 for now until hypridle maintainers release an update where they rebuild with the newer sdbus-cpp 2.3.0
Summary
After a routine system upgrade,
hypridlecrashes immediately on every launchwith SIGSEGV. The screen no longer locks, dims, or suspends on idle, and the
ML4W waybar hypridle module stays red. Clicking the waybar
module to toggle it does nothing because the daemon dies the instant it starts.
This is not an ML4W config bug. Root cause is an
sdbus-cppABI break:sdbus-cppwas upgraded 2.2.1 -> 2.3.0 whilehypridlewas not rebuilt againstit.
Steps to reproduce
Issue is evident on startup
Expected behavior
hypridle works
Screenshots
No response
Distribution
Arch Linux
If Other, specify
No response
Additional context
No response
Code of Conduct