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 recently noticed my framework laptop started kicking the fan on. I was wondering why that is, and it seems like that the touch detector is a bit resource hungry from time to time. It doesn't happen all the time, but sometimes I get the following utilization:
I am curious on why this is happening? Am I the only one experiencing this?
This is happening while using NixOS, and the service is started according to this configuration.
The text was updated successfully, but these errors were encountered:
That's quite unfortunate! Does debug log reveal anything useful, such as which detector is seemingly running crazy? (most likely gpg one...).
I can't consistently reproduce it... I enabled the verbose option, so next time it happens, I will have additional logs to show here!
Did you notice if it started since a particular update?
I started using it not so long ago, maybe a few weeks or two months tops, and this has been happening to me since the beginning, but it was also really inconsistent. This time it happened after I changed some things in my configuration and rebuilt NixOS, so it could be something system-specific.
I recently noticed my framework laptop started kicking the fan on. I was wondering why that is, and it seems like that the touch detector is a bit resource hungry from time to time. It doesn't happen all the time, but sometimes I get the following utilization:
I am curious on why this is happening? Am I the only one experiencing this?
This is happening while using NixOS, and the service is started according to this configuration.
The text was updated successfully, but these errors were encountered: