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 started wondering over x-mas time why one of my systems (which is typically idling overnight with an active X session) started consuming more power. And not just a little bit, the wattage almost doubled. And powertop reported icewm as the culprit, causing over 100 wakeups per second while supposedly doing nothing. But the behavior did not always appear, and I was not sure how to reproduce it.
But this time I could catch it, and see it happening even over multiple restarts of icewm. So I did a git-bisect and could identify the following commit as the culprit:
13d384d352a10ebdface07c1b821b0c8c971f209 is the first bad commit
commit 13d384d352a10ebdface07c1b821b0c8c971f209
Author: Bert Gijsbers <[email protected]>
Date: Wed Nov 9 22:05:27 2022 +0100
Freeze the task pane layout while Alt is pressed for #549.
src/atasks.cc | 12 ++++++------
src/wmtaskbar.cc | 2 +-
2 files changed, 7 insertions(+), 7 deletions(-)
And regarding the type of events, that could be anything. Looks like some endlessly repeated X11 communication attempt:
This does not really make a difference. OTOH I am observing more strange issues with CPU activity on that system, seems to be caused by recent updates which trigger strange kernel behaviors. I need to observe this further, the current issue can be probably put on hold.
I started wondering over x-mas time why one of my systems (which is typically idling overnight with an active X session) started consuming more power. And not just a little bit, the wattage almost doubled. And powertop reported icewm as the culprit, causing over 100 wakeups per second while supposedly doing nothing. But the behavior did not always appear, and I was not sure how to reproduce it.
But this time I could catch it, and see it happening even over multiple restarts of icewm. So I did a git-bisect and could identify the following commit as the culprit:
And regarding the type of events, that could be anything. Looks like some endlessly repeated X11 communication attempt:
The text was updated successfully, but these errors were encountered: