#21 2020-01-22 07:49:05

ohnonot

...again

Registered: 2015-09-29

Posts: 5,592

Re: Does Conky Crash on your Machine?

Have you tried the two scripts in other conkys and/or by themselves in a test conky?

Not recently, but I'm positive they work OK. That doesn't mean that conky couldn't get tripped up by a shell script of course.
I'm leery of translating that to a pure conky solution; looks much more complicated than a quick shell script. But who knows, maybe execp instructions are generally problematic? OTOH, my weather conky uses nothing but execp and runs fine.

Comment: Any one think this might be a v1.11 problem?
EDIT #2:  From the link ohnonot supplied: yes I would say so.

This obviously started happening about a year ago, so yes, it's some sort of - how do you call it - regression.

My assumption is that it  with you

own_window_type = 'override',

is. Try that with 'normal'

Good point.
I'm trying it with 'desktop' now.

Thanks for comments & testing everyone!

Sector11

Mod Squid Tpyo Knig

From: Upstairs

Registered: 2015-08-20

Posts: 8,028

Re: Does Conky Crash on your Machine?

Personally I would go with "normal" that way your "own_window_hints" actually work.

       own_window_hints undecorated,below,above,sticky,skip_taskbar,skip_pager
              If  own_window is yes, you may use these window manager hints to affect the way Conky displays.
              Notes: Use own_window_type desktop as another way to implement many of these hints  implicitly.
              If you use own_window_type override, window manager hints have no meaning and are ignored.

Desktop says many of these hints BUT - not which ones or which are not.
OOPS!  Until one reads "own_window_type"

own_window yes
own_window_type normal
own_window_hints undecorated,below (or above),sticky,skip_taskbar,skip_pager

sticky means: on ALL desktops

PUTS YOU IN THE DRIVERS SEAT.

so:

own_window_hints undecorated,below,skip_taskbar,skip_pager ##,sticky, above

and conky only runs on the desktop you started it on, under other applications.

Last edited by Sector11 (2020-01-22 14:19:19)

---

Debian 12 Beardog, SoxDog and still a Conky 1.9er

ohnonot

...again

Registered: 2015-09-29

Posts: 5,592

Re: Does Conky Crash on your Machine?

This is going nowhere, conky keeps on crashing, my issue is slowly giving way for new issues - apparently nobody can reproduce this.
I have now compiled 1.9.0 and am using it. Super minimal version, too, since I'm not using the lua anyhow.
And I did it in a way that it can coexist with newer versions (hopefully):
https://aur.archlinux.org/packages/conky19
My first AUR submission!

Let's see how the weekly backup tomorrow goes, that's when it used to crash the most.

Sector11

Mod Squid Tpyo Knig

From: Upstairs

Registered: 2015-08-20

Posts: 8,028

Re: Does Conky Crash on your Machine?

I have an issue with conky that when I edit or make a change and save the file it crashes conky and it can't be restarted unless I reboot.

Just saw this .... How do you start your conkys?

I put a line at the top of each conky (example):

# pkill -xf "conky -c /media/5/Conky/S11_DateTime_br.conky" &

I start my conkys in a bash script:

(sleep 2 && wmctrl -s 0 && conky -c /media/5/Conky/S11_DateTime_br.conky) &

SO: if you start the conky like this:

conky -c /media/5/Conky/S11_DateTime_br.conky &

and it crashes when you edit it ... try in a terminal:

 07 Feb 20 @ 21:38:33 ~
   $ pkill -xf "conky -c /media/5/Conky/S11_DateTime_br.conky" &
[1] 13671
 
 07 Feb 20 @ 21:38:46 ~
   $ conky -c /media/5/Conky/S11_DateTime_br.conky &
[2] 13740
[1]   Done                    pkill -xf "conky -c /media/5/Conky/S11_DateTime_br.conky"
 
 07 Feb 20 @ 21:38:56 ~
   $ Conky: desktop window (25d) is root window
Conky: window type - normal
Conky: drawing to created window (0x3800002)
Conky: drawing to double buffer

NOTE: after the first command use the ↑ arrow - edit the line and see it it restarts.

Good luck.

---

Debian 12 Beardog, SoxDog and still a Conky 1.9er

ohnonot

...again

Registered: 2015-09-29

Posts: 5,592

Re: Does Conky Crash on your Machine?

I have had this problem for a long time now.

There has been some development; it seems at least one more person experiences the same thing and suggested sticking with the 1.11.3 release.
That has been perfectly stable for me across 3 different installs (all of them Archlinux though).