Yeah thats about what I figured too... I haven't submited a bug report yet because my work around is working fine other then I do have to be careful of (suspend, battery/AC change). I'm debating wheather I want to try rewriting the blanker and the lightnpower.py script into one program or script because there are other times when supending is bad like rewiting files to the Zaurus via USB...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=123951\"][{POST_SNAPBACK}][/a][/div]
After claiming here that everything worked fine for me I discovered it didn't... so I came up with a workaround also. The problem is that the blanker is compiled, so I gave away the idea of using that. The lightnpower.py script however is actually very reliable, and the settings here are honoured throughout (settings in ~/Choices/lightnpower.cfg). So, I made a second file with some always-on settings, and:
#!/bin/sh
case "$1" in
on)
if [ -f ~/Choices/lightnpower.cfg.blanker ]; then
mv ~/Choices/lightnpower.cfg ~/Choices/lightnpower.cfg.normal
mv ~/Choices/lightnpower.cfg.blanker ~/Choices/lightnpower.cfg
/usr/bin/lightnpower.py --loadandquit
fi
;;
off)
if [ -f ~/Choices/lightnpower.cfg.normal ]; then
mv ~/Choices/lightnpower.cfg ~/Choices/lightnpower.cfg.blanker
mv ~/Choices/lightnpower.cfg.normal ~/Choices/lightnpower.cfg
/usr/bin/lightnpower.py --loadandquit
fi
;;
*)
echo "Usage: $0 (on|off)"
exit 1
;;
esac
exit 0
This script just copies the different settings file in, runs the lightnpower.py script to update settings, and they are used until swapped back. Instead of 'on' and 'off', it would be reasonably trivial to have any number of modes/files...
And you don't have to be careful about taking on or off AC power or suspending at all.