Conky Problem :(

T-u-N-i-X · 2007-02-25 22:39:48

Hi There,

I just started using Conky and I really loved it. But I have 2 major problems on my GNOME desktop using conky:

1) Conky doesn't quit properly when I logout or restart/shutdown my computer and GNOME pops out a warning message that conky doesn't support "save state" thing..

2) Sometimes conky suddenly disappears and doesn't come back. If I logout or restart/shutdown my computer, it shows up for 1 second then the upper problem occurs.. When I kill and restart conky, it continues how it's supposed to show up..

Here is my conkyrc:

background no
use_xft yes
xftfont Fertigo:size=9
xftalpha 0.8
out_to_console no
update_interval 2
total_run_times 0
own_window yes
own_window_type normal
own_window_transparent yes
own_window_hints undecorated,below,sticky,skip_taskbar,skip_pager
double_buffer yes
draw_shades yes
draw_outline no
draw_borders no
draw_graph_borders yes
stippled_borders 5
border_margin 4
border_width 1
default_color white
default_shade_color black
default_outline_color black
alignment top_right
gap_x 10
gap_y 47
no_buffers no
uppercase no
override_utf8_locale yes
use_spacer no
minimum_size 200

TEXT
${color white}$alignc${exec whoami} @ $nodename
${color white}$alignc$sysname $kernel on $machine
${color white}$alignc Uptime: ${color white}$uptime
$color$stippled_hr
${color slate grey}CPU: ${color white}${cpu cpu1}% ${cpubar cpu1}
${color slate grey}MEM: ${color white}$memperc%  $mem/$memmax $membar
${color slate grey}Swap: ${color white}$swapperc% $swap/$swapmax ${swapbar}
${color slate grey}Processes: ${color }$processes 
${color slate grey}Running:   ${color }$running_processes
$color$stippled_hr
${color slate grey}Highest CPU:
${color} ${top name 1}${top cpu 1}
${color} ${top name 2}${top cpu 2}
${color} ${top name 3}${top cpu 3}
${color} ${top name 4}${top cpu 4}
${color} ${top name 5}${top cpu 5}
${color slate grey}Highest MEM:
${color} ${top_mem name 1}${top_mem mem 1}
${color} ${top_mem name 2}${top_mem mem 2}
${color} ${top_mem name 3}${top_mem mem 3}
${color} ${top_mem name 4}${top_mem mem 4}
${color} ${top_mem name 5}${top_mem mem 5}
$color$stippled_hr
${color slate grey}File Systems:
 /            $color${fs_used /} / ${fs_size /} ${fs_bar /}
 /pub      $color${fs_used /pub} / ${fs_size /pub} ${fs_bar /pub}
$color$stippled_hr
${color slate grey}Recent Updates:
${color white}${execi 300 /home/tunix/.arch-packet-news.sh}
$color$stippled_hr
${color slate grey}Ethernet:
${color}Down: ${downspeed eth1} Kb/s       Up: ${upspeed eth1} Kb/s
${color slate grey}Wireless:
${color}Down: ${downspeed eth0} Kb/s       Up: ${upspeed eth0} Kb/s

T-u-N-i-X · 2007-02-26 17:31:11

Nobody uses conky with GNOME ? Or nobody cares about the problem ?

tsangpo · 2007-02-26 18:14:10

Maybe you could try to write an e-mail to conkies developers about the problem ?

Maybe Conky hides on one of the virtual desktops if you have more than one set.

P.S. Conky is a funny name Nice name for a cuddly pet

ralvez · 2007-02-26 18:25:00

I do not use Gnome, but I do use conky.
I do not know about problem 1 but problem 2 may be related to what seems to be a custom script you have in /home/tunix/.arch-packet-news.sh.
When I started using conky I noticed that it would "die" sometimes for no reason; then I noticed a co-relation between conky failures and a custom script I wrote to report the headers of new e-mails in my e-mail server (so that I get them if they are important).
I added error handling procedures to my script, so it would not "hang" if the e-mail server failed to log me in and the problem has been resolver forever.

As per the other "save state" error ... sorry I have no clue.

R

Last edited by ralvez (2007-02-26 18:28:08)

daedalusman · 2007-02-26 18:35:50

I use to use conky with gnome, and I had the same problem. I would log out and back in and there would be a conky instance that wouldn't have gotten shutdown and upon logging back in the old conky instance would be running at 100% cpu and I would have to kill it myself. I don't have this happen in any other DE/WM so I would say it has something to do with the way gnome exits its sessions. Try the conky-developers list and see what you come up with, or maybe their forums on sourceforge. Sorry I couldn't be more help.

.:B:. · 2007-02-26 19:00:28

I use Conky in XFCE, serves well... It autostarts with XFCE, and I don't have any errors at all when logging out & back in. Nor do i have the appearance problem... Since you have the 'doublebuffer' option enabled, I don't think it's got something to do with flickering or so. Maybe you should check if you're not using any scripts that bork accidentally, as pointed out above.

bones · 2007-02-26 20:38:49

I tried using conky with Gnome, kept having the same problems as you. I tried everything to fix the problem with no luck although that might be just me. Using Fluxbox currently and conky works perfectly so I suspect it doesn't want to play nice with Gnome

T-Dawg · 2007-02-27 01:50:03

You may want to try forking it to the background. There's a setting for it in conkyrc. The developer of conky frequently visits the gentoo forums, you may have better luck posting there. His name is Brenden.

alvmax · 2007-02-27 22:17:04

The only way that conky doesn't give me probs in GNOME, is launching it using a application launcher.
And checking your .conkyrc, mine only differs in this:

own_window_transparent no
own_window_colour black

Never worked forked in the background or launching in the startup.
Hope it helped, .

Arch Linux

#1 2007-02-25 22:39:48

Conky Problem :(

#2 2007-02-26 17:31:11

Re: Conky Problem :(

#3 2007-02-26 18:14:10

Re: Conky Problem :(

#4 2007-02-26 18:25:00

Re: Conky Problem :(

#5 2007-02-26 18:35:50

Re: Conky Problem :(

#6 2007-02-26 19:00:28

Re: Conky Problem :(

#7 2007-02-26 20:38:49

Re: Conky Problem :(

#8 2007-02-27 01:50:03

Re: Conky Problem :(

#9 2007-02-27 22:17:04

Re: Conky Problem :(

Board footer