Re: Gkrellm locking
Bill Wilson <[email protected]>
| Newsgroups | gmane.comp.gnome.apps.gkrellm |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 14 Nov 2007 09:45:46 -0300 "Salatiel Filho" <[email protected]> wrote: > I am using gkrellm and somehow everytime i use gkrellmms plugin for a > while gkrellm locks. Any idea how to fix this ? I've seen this happen because of the combination of a slow sensor reading thread and gkrellmms calling a libxmms function which then locks up gkrellm. I think there's a race condition somewhere caused by the libxmms function calling setuid() which in turns tries to signal the setuid change to all gkrellm threads, but I never have been able to track down a good fix. You can have a slow sensor reading thread if you are monitoring a GPU temp (which runs the nvidia-settings command which can be a bit slow), or if you have a sensor chip which is slow to read (ASB100 is the one I know of). If it's the GPU temp, then I guess you have to quit monitoring it or stop using gkrellmms. If it's because of monitoring the ASB100 chip, then you can install mbmon and use it for getting sensor data instead of using the internal gkrellm sensor functions. Bill ______________________________________________ Gkrellm mailing list [email protected] Read archives-join-leave-set RSS feed: http://archive.lists.netservicesgroup.com