2010-10-02, 21:44
Hi all,
I've been using XBMC for a while now, and recently moved from camelot to Dharma (beta 2, after a couple of svn versions and beta 1).
However i'm running xbmc on a machine that also functions as a server. To be able to put the server in standby i wrote a python script that checks for all kinds of activity (xbmc status, samba shares status, transmission, etcetera. not important for this post, but for more details: http://ubuntuforums.org/showthread.php?p=9917183).
to detect user input from the keyboard or mouse i use 'xprintidle', a command that spits out the X idle time in miliseconds.
This all worked fine in Camelot, but since Dharma there is a problem: Dharma seems to generate events (about every 5 seconds) that disturb this timer.
I've been looking for other programs that do the same, but haven't been able to find any so far (the only thing disturbing the timer seems to be mouse and keyboard activity, or XBMC)
best way to try this out is:
1. opening a terminal window
2. run this command: for i in {1..10}; do sleep 5; xprintidle; done
3. don't touch the mouse or keyboard
4. try it with xbmc on and xbmc off
I'm hoping somebody can tell me why xbmc behaves like this, or that it's a bug that will be crushed in the final release
I've been using XBMC for a while now, and recently moved from camelot to Dharma (beta 2, after a couple of svn versions and beta 1).
However i'm running xbmc on a machine that also functions as a server. To be able to put the server in standby i wrote a python script that checks for all kinds of activity (xbmc status, samba shares status, transmission, etcetera. not important for this post, but for more details: http://ubuntuforums.org/showthread.php?p=9917183).
to detect user input from the keyboard or mouse i use 'xprintidle', a command that spits out the X idle time in miliseconds.
This all worked fine in Camelot, but since Dharma there is a problem: Dharma seems to generate events (about every 5 seconds) that disturb this timer.
I've been looking for other programs that do the same, but haven't been able to find any so far (the only thing disturbing the timer seems to be mouse and keyboard activity, or XBMC)
best way to try this out is:
1. opening a terminal window
2. run this command: for i in {1..10}; do sleep 5; xprintidle; done
3. don't touch the mouse or keyboard
4. try it with xbmc on and xbmc off
I'm hoping somebody can tell me why xbmc behaves like this, or that it's a bug that will be crushed in the final release