This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
Cawbird spams stderr with assertion failure warnings when no monitor is connected #457
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
I regularly disconnect both of my external monitors from my PC. (They’re connected to physical switches that let me quickly toggle them between my private PC and my work laptop.) When this happens, Cawbird logs tons of messages like this:
And by “tons”, I mean ca. 30000 messages (thirty thousand) over the course of a working day (ca. seven hours). It seems to happen in bursts, with a couple hundred messages every two minutes.
500 log messages (the only difference is the timestamp)
To Reproduce
(I haven’t tried to reproduce it yet since working around it by piping cawbird into a grep filtering out this message.)
Expected behavior
Ideally, I suppose Cawbird would handle this more gracefully. None of the other applications on my system seem to handle the disconnected monitors quite as badly (though Cawbird isn’t the only one that I have to move back to its correct position on screen after switching the monitors to the PC again).
Screenshots
N/A
System details:
The text was updated successfully, but these errors were encountered: