tpb osd program: strange behavior

[murphycc]

Does anyone else here use the tpb program (for osd) with Kubuntu? I'm running KDE 4.5 and see that when I first install tpb, colors appear blue. When I rerun it after successive reboots, colors are green and even white sometimes. I changed settings in the /etc/tpbrc file and it doesn't seem to consistently change colors.

I did not use tpb in KDE 4.4.x, so not sure if this would have happened with that too.

Has anyone else seen weird issues with 'tpb'?

I'm using T42 with Lucid 10.04 installed.

Thanks,
Chris

[ThinkRob]

IIRC there can be a settings file in your home directory. Have you checked to make sure nothing odd is going on with that?

(Disclaimer: I haven't used tpb in quite a while, so I could just be dreaming about ~/.tpbrc )

[murphycc]

Thanks, Rob. I messed with the .tpbrc file in my home directory earlier too, and that didn't change it.

I do have an update in that when I first start tpb by typing 'sudo /usr/bin/tpb -d' then the OSD color is green. After my laptop has been on a while, it becomes blue as it should after I hit volume button or brightness button.

I'm not sure if this means that some service affects it somehow? Maybe going into screen saver mode or something could affect the way the system reads this?

I will try using the 'strace' command with this to see if I can tell what's happening when it switches to blue.

Thanks,
Chris

[ThinkRob]

Thanks, Rob. I messed with the .tpbrc file in my home directory earlier too, and that didn't change it.

I do have an update in that when I first start tpb by typing 'sudo /usr/bin/tpb -d' then the OSD color is green. After my laptop has been on a while, it becomes blue as it should after I hit volume button or brightness button.

I'm not sure if this means that some service affects it somehow? Maybe going into screen saver mode or something could affect the way the system reads this?

Ah. That may be it. Depending on how you installed TPB, it's possible that it was also installed as a service, meaning that starting it manually will give you two running copies. This could be further complicated if the service one is set to read a config file from a different location than the default.

Check to see if you have an entry in /etc/init.d/ -- I'm betting you'll find one.