You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The recent aquamarine update from v0.5.0 to v0.5.1 has resulted in a critical failure when my laptop wakes up from s2idle sleep mode. The screen is black and it seems Hyprland is unable to restart, since I cannot find any errors from systemd services activated before and after the suspend action.
After analyzing all packages installed on my system, I've identified the error originates from this aquamarine update. I've also bisected the commits in the update and localized the issue to 4468981 (see #108 for discussion about the change and #107 for the issue that prompted it).
From my understanding, this commit was intended to prevent a segfault on startup which was occurring on certain systems. I am not aware if this was ever an issue on my system, but I do know that #107 suggested the fix that was eventually applied in #108 as a potential workaround and noted that a more complete solution would involve identifying calls to CDRMAtomicImpl::reset() and ensuring that a null pointer will not be dereferenced after the call.
I am not sure how this change results in a sleep mode failure, but my guess is that upon waking up from the sleep state, the fix in #108 prevents critical logic from executing because of a potential null pointer dereference and Hyprland is unable to start.
The text was updated successfully, but these errors were encountered:
The recent aquamarine update from v0.5.0 to v0.5.1 has resulted in a critical failure when my laptop wakes up from s2idle sleep mode. The screen is black and it seems Hyprland is unable to restart, since I cannot find any errors from systemd services activated before and after the suspend action.
After analyzing all packages installed on my system, I've identified the error originates from this aquamarine update. I've also bisected the commits in the update and localized the issue to 4468981 (see #108 for discussion about the change and #107 for the issue that prompted it).
From my understanding, this commit was intended to prevent a segfault on startup which was occurring on certain systems. I am not aware if this was ever an issue on my system, but I do know that #107 suggested the fix that was eventually applied in #108 as a potential workaround and noted that a more complete solution would involve identifying calls to
CDRMAtomicImpl::reset()
and ensuring that a null pointer will not be dereferenced after the call.I am not sure how this change results in a sleep mode failure, but my guess is that upon waking up from the sleep state, the fix in #108 prevents critical logic from executing because of a potential null pointer dereference and Hyprland is unable to start.
The text was updated successfully, but these errors were encountered: