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
I'm not sure if this is an issue with cosmic-idle or some other piece of cosmic. When I wake the system from monitors-idle (I don't use standby or sleep, just monitor turn-off) there's about a 25% chance that one or more of my monitors will fail to wake up.
The only way I've found to recover from this is to logout and log back in, I assume this causes the compositor to restart.
The text was updated successfully, but these errors were encountered:
Any input event should re-enable outputs. pop-os/cosmic-comp#741 does that internally as a fail-safe so even if a client like cosmic-idle wasn't working properly, monitors should still turn on.
So I guess it's a cosmic-comp issue. But odd. Does turning the monitor off and on fix it? I wonder if anything is logged to journalctl by cosmic-comp, or if there are any drm driver errors of dmesg.
I just tried it and indeed yes, if you power off the monitor and then turn it back on, it comes up -- maybe its an issue with the monitor? They're amazon-house sceptre brand so who knows how well they adhere to standards.
It's definitely possible that the monitor is doing something wrong. But if this issue happens on cosmic-comp and not other desktops, there must be something we're doing differently.
I'm not sure if this is an issue with cosmic-idle or some other piece of cosmic. When I wake the system from monitors-idle (I don't use standby or sleep, just monitor turn-off) there's about a 25% chance that one or more of my monitors will fail to wake up.
The only way I've found to recover from this is to logout and log back in, I assume this causes the compositor to restart.
The text was updated successfully, but these errors were encountered: