fix: don't restart if zero active screens are reported #3078
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
farhaven
force-pushed
the
dont-restart-on-zero-screens
branch
from
2f434a3
to
298f996
Compare
On laptops and similar devices, RandR sometimes returns zero active screens, for example when closing a laptop's lid before it suspends. Don't restart in that case because the new polybar instance will see zero screens and quit. Instead, just ignore those kind of events.
farhaven
force-pushed
the
dont-restart-on-zero-screens
branch
from
298f996
to
dbec774
Compare
|
Ping :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this? (check all applicable)
Description
On laptops and similar devices, RandR sometimes returns zero active screens, for example when closing a laptop's lid before it suspends.
Don't restart in that case because the new polybar instance will see zero screens and quit. Instead, just ignore those kind of events.
Related Issues & Documents
Fixes #2418.
Documentation (check all applicable)