Conky and KDE 4
 

Two questions about Conky 1.6.1 in KDE 4 (13.0, 32-bit):

1. Has the transparency issues been resolved or do users still have to use the feh workaround?

2. I have 12.2 and 13.0 installed on the same machine in different partitions. With 12.2 the directive for displaying hard drive temperature works as expected but the same directive does not display in KDE 4:

${color black}WD6400AAKS(sda) Temp:${color white} ${hddtemp /dev/sda}

All other Conky parameters display the same in both systems.

Running the hddtemp command from the command line works as expected in both systems.

I appreciate any insights.

Hi!

I have conky 1.7.2 and it uses feh at the end of the .conkyrc to set the background...
IIRC the problem is that the KDE-Wallpaper is drawn on KDEs Plasma and not on the X-Server
root window directly.

last time i checked, it still needs the feh workaround. i couldn't be bothered because i change my wallpaper often, so i just have mine on a gray background :D

Disappointing. :(

In the past I set the conky color to the same as my desktop color. Worked great because I did not use wallpaper. With my new HTPC I want to add some glitter with wallpaper and conky looks awful. Looks like I'll have to try the feh (bleh?) solution.

Still no success with problem No. 2: getting conky to display my hard drive temp. I rebuilt conky 1.6.1 in 13.0 rather than use my package built for 12.2. No difference. This is not a permissions problem. Normal users can display hddtemp temps from the command line. Only conky won't display the same information. Same conkyrc file as used in 12.2.

Any ideas?

Solved
 

Funny how life in a discussion forum works! I solved the problem about 20 minutes after posting my previous message. :scratch:

I noticed in my rc.local that I was using an incorrect host name for starting hddtemp the way I want (each box around here has a slightly different hard drive configuration).

I have my rc.local default to hddtemp -d /dev/hda if no host name is defined. This box is using a SATA drive (/dev/sda). With an incorrect host name, the hddtemp daemon was monitoring /dev/hda rather than /dev/sda.

Running hddtemp /dev/sda worked fine from the command line because the direct command is not the same as the daemon. Conky was configured (correctly) to query the hddtemp daemon. As the rc.local was starting hddtemp -d /dev/hda, conky was asking the daemon for a temp that the daemon was not monitoring.

Computers always do what they are instructed to do, not necessarily what we want them to do! :)

One more "dammit" crossed off the list!