I checked the published Hyprland source packages for Stonking and Tenacious. Both currently ship 0.56.2+ds-1, using identical source files.
Both include: - e123fd3, the monitor disconnect fix. - e0cf888, including default image-description initialization. The newer monitor constructor initializes m_imageDescription with getDefaultImageDescription(). The additional defensive m_imageDescription.valid() check from my second debdiff is not present. The default initialization appears to address the crash path that prompted that check, though this is source verification only; I haven’t run DPMS tests on those releases. Would this be sufficient to consider Stonking and Tenacious already fixed for this bug and proceed with the Resolute SRU, or would you like the defensive check submitted for those releases too? The second patch has remained stable on my Resolute system. Thanks, Paul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2165180 Title: Hyprland 0.53.3 crashes on monitor wake/DPMS reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hyprland/+bug/2165180/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
