[SOLVED] Conky either doesn't run or crashes

PClOStinspace · 10-04-2013, 04:39 AM

I have installed conky manager and tweaked the conky_orange to my requirements but no matter what I try it continually either fails to start or crashes regularly. It will allways crash whenever any application goes into full screen view also.

I have put my rc, the various lua scripts and py scripts and my startup file in a .zip in dropbox here. Can anyone shed any light on what is going on as I have completely run out of ideas how to sort this out!!

Habitual · 10-04-2013, 08:30 AM

Code:

######################
# - Conky settings - #
######################
update_interval 1
total_run_times 0
net_avg_samples 1
cpu_avg_samples 1

imlib_cache_size 0
double_buffer yes
no_buffers yes



#############################
# - Window specifications - #
#############################
own_window yes
own_window_type override
own_window_transparent yes
own_window_hints undecorated,below,skip_taskbar,skip_pager,sticky
#own_window_colour gray
own_window_class Desktop
own_window_title Chronograph

gap_x 20
gap_y 0
alignment tr

draw_shades no
draw_outline no
draw_borders no
draw_graph_borders no

minimum_size 280 300
maximum_width 280

################      Graphics settings       ######################
use_xft yes
xftfont Ubuntu:normal:size=8
override_utf8_locale yes
text_buffer_size 2048
draw_shades no
#default_bar_size 40 8
default_outline_color black
own_window_argb_visual yes

default_color FFDEAD #NavajoWhite
color0 8FBC8F #	DarkSeaGreen
color1 C2CCFF # LightSlateGray
color2 3300CC # Mid Blue
color3 7FFF00 #	Chartreuse
color4 FFA07A #	LightSalmon
color5 c0c0c0 #	Silver
color6 00BFFF # DeepSkyBlue
color7 00FFFF #	Cyan
color8 FFFF00 #	Yellow
color9 330088 #	Dark Blue
xftalpha 1

###  LUA Settings  ###########################################################
# lua_load ~/.conky/.scripts_orange/main.lua
# lua_draw_hook_pre conky_widgets
# lua_load ~/.conky/.scripts_orange/bargraph.lua
# lua_draw_hook_post main_bars

TEXT
${voffset 150}
${goto 32}${font :bold:pixelsize=11}${time %a, %d %b %Y}${font}

##### MAIL ########
Mail goes here.
${voffset -25}${goto 230}${font :bold:size=8}GMAIL${font}

################      Weather       ######################
Weather goes here.
######### System ##########
System goes here...
########## HDD ###########
HDD goes here.
#####  Network ########
Network goes here.
##### Processes #########
Processes go here.
##### Memory #########
Memory goes here.
##### Radio Tray ########

My changes in red.

keeps it on the screen, so you can edit conkyrc_orange to suit in your favorite text editor while conky is running.
With conkyrc_orange open in your editor, slowly start adding one line of code at a time,
hit save, wait for conky to refresh and see the result.
Your mistakes or script errors will become apparent in "real-time" on the screen after you hit save in the editor.

If you make a mistake, or you don't like the result,
you can always "undo" (control+z in most graphical text editors these days)
and hit save again, wait for conky to refresh on the screen.
Evaluate the result.

I'm old-school and I coded conkyrc for months, by hand, so I consider conky_manager to be "cheating"
and robbing you of a valuable experience that you could be gaining, ie. how to code and debug your code.
There is great satisfaction when you learn to do so and it comes in handy in other areas of Linux-Life
</sermon>

Tips:

Once you are absolutely certain you are making the progress you want to have as a final result (but aren't finished with the total conky)
Save conkyrc_orange and exit your editor.

The next editing session, you can always "undo" back to the state where conkyrc_orange was opened.
Most graphical text editors (gedit, anyway) support this.
It will only "undo" back to the state it was opened in, a "roll-back" feature.
This includes undo-ing any saves you may have made in the editing process.

So, if you open it and make 42 changes today and hit save each time
but at the end of the day, you decide to toss it and start over from when you opened conkyrc_orange,
you can with "undo" (Control+Z) all the way back to the beginning of today's editing session.
Hit save again once more and you're back to the start.
You can then close the editor and prevent any further "undo-ing". A rollback point if you will.

If you close the file after hitting save, your undo will no longer be able to function since the state
is written to the file and the undo buffer is empty.

If you have any questions about coding your own conkyrc or this method I have described, I'd be happy to answer them.
But I will not respond to any questions about "conky manager" other than "edit it yourself in an editor", or a pointer or 2
to how to edit it in the editor. Nor can I help with LUAs and .py scripts in conkyrcs, other than using an editor and the editing
of your conkyrc. Sorry about that.

Good luck.

Subscribed with interest.
I ought to blog this.

PClOStinspace · 10-04-2013, 09:06 AM

Thanks Habitual.

I did initially use conky manager to install conky and the various themes this time but have since modified the rc and lua's in gedit as the standard theme was not entirely to my liking. I have tweaked the x positioning as per your suggestion and am now going to let it run for a bit to see what happens. I'd rather keep the window type as panel as I have a wide screen and prefer not to let 'normal' windows maximise over it. I'm confident the window type is not the issue as the problem was occuring before I discovered the panel option anyway.

If you are really up for a challenge I have posted a previous thread about something......

(oh hang on, it just crashed again while I was typing so x pos is not the culprit I guess!)

........I am trying to achieve with this conky. Thread can be found here if you're game!!

Do you know if there is a way I can run conky from terminal so it will tell me what is causing it to crash? At the moment I am calling the startup script each time it crashes and that just gives me:-

Code:

gregg@Singularity:~$ /home/gregg/conky-manager/conky-startup.sh
Conky: no process found
gregg@Singularity:~$ Conky: desktop window (1200d3c) is subwindow of root window (9d)
Conky: window type - panel
Conky: drawing to created window (0x3e00002)
Conky: drawing to double buffer
Conky: defining struts

Habitual · 10-04-2013, 09:33 AM

Quote:

Originally Posted by PClOStinspace

...if you're game!!

I will not quote myself.
I will not quote myself.
I will not quote myself.

Quote:

Originally Posted by PClOStinspace

Do you know if there is a way I can run conky from terminal

yeah,
terminal >

Code:

conky -c /path/to/conkyrc_orange

using own_window_type panel causes my Xfce desktop to go wonky,
messing up the placement of my desktop icons and window placement
of my open programs also on my 23" monitor.

Try poking around http://conky.pitstop.free.fr/wiki/in...itle=Main_Page

PClOStinspace · 10-04-2013, 09:21 PM

Quote:

Originally Posted by Habitual

I will not quote myself.

Sorry, I consider my wrists slapped, I will not ask for any more lua/py specific help.

Quote:

Originally Posted by Habitual

yeah,
terminal >

Code:

conky -c /path/to/conkyrc_orange

Using this I get:-

Code:

gregg@Singularity:~$ conky -c /home/gregg/conky-manager/themes/conky\ orange/config/conkyrc_orange 
Conky: desktop window (1200d3c) is subwindow of root window (9d)
Conky: window type - panel
Conky: drawing to created window (0x1c00002)
Conky: drawing to double buffer
Conky: defining struts
Alarm clock

I can find no reference to 'Alarm clock' in either the rc, any of the lua's or py's. As it happens I do have 'Alarm clock' installed and running but stopping it doesn't seem to make any difference??

I hope I haven't upset you so far as to evade any further assistance?

Habitual · 10-04-2013, 09:36 PM

Gregg:

Did you check all of /home/gregg/.scripts/?

Code:

grep -i *clock* /home/gregg/.scripts/* -Rln

will show the file name, if it exists in one.

Any other conkies running when you ran that in terminal?

Code:

conky -v

output please.

John

PClOStinspace · 10-05-2013, 05:04 PM

Quote:

Originally Posted by Habitual

Did you check all of /home/gregg/.scripts/?

Code:

grep -i *clock* /home/gregg/.scripts/* -Rln

will show the file name, if it exists in one.

That command returns nothing, looking with nemo ~/.scripts contains only the 5 scripts that point to the directories I am trying to query with the lua bar graphs. These have nothing to do with alarm clock. The dropbox one looks like:-

Code:

#!/bin/bash
dir="/home/gregg/Dropbox"
du -hs $dir | cut -f 1

and the rest follow the same format but with different paths.

Quote:

Any other conkies running when you ran that in terminal?

No

Quote:

Code:

conky -v

output please.

Code:

gregg@Singularity:~$ conky -v
Conky 1.9.0 compiled Thu May 24 15:31:18 UTC 2012 for Linux 2.6.24-31-server (x86_64)

Compiled in features:

System config file: /etc/conky/conky.conf
Package library path: /usr/lib/conky

 X11:
  * Xdamage extension
  * XDBE (double buffer extension)
  * Xft
  * ARGB visual

 Music detection:
  * Audacious
  * MPD
  * MOC
  * XMMS2

 General:
  * math
  * hddtemp
  * portmon
  * Curl
  * RSS
  * Weather (METAR)
  * Weather (XOAP)
  * wireless
  * support for IBM/Lenovo notebooks
  * nvidia
  * eve-online
  * config-output
  * Imlib2
  * apcupsd
  * iostats
  * ncurses
  * Lua

  Lua bindings:
   * Cairo
   * Imlib2

Thanks for coming back again. I'm not a complete noob, I've been 100% Linux for 5 years but I do struggle when things get a bit complex. I have no IT training I just muddle along trying to pick it up as I go!

Habitual · 10-05-2013, 07:49 PM

I don't have LUA nor Imlib2 support in my version of Conky 1.9.0.

Sorry, I wish I could help more.

PClOStinspace · 10-06-2013, 03:58 PM

Quote:

Originally Posted by Habitual

I don't have LUA nor Imlib2 support in my version of Conky 1.9.0.

Sorry, I wish I could help more.

OK, thanks anyway. I've googled until my fingers are raw, it's really tough even finding a start point to crack this one!!

Habitual · 10-06-2013, 09:08 PM

Post #4, 2nd link.

PClOStinspace · 01-24-2014, 07:58 AM

Still no idea what the problem was here but it seems to have resolved itself since I upgraded to 13.10 Saucy?!?!?!