Arch Linux

Lizzi

Member

Registered: 2016-05-15

Posts: 40

Has anyone managed to get picom to work with conky in openbox?

the learning curve seems steeper than i remember it ever was for compton and my old reliable, unagi is not even buildable for so long i wonder why it is even in the aur.

If you have managed to  get it to work could you share your secrets please?  When i run picom with any variable my very basic text conky disappears from my screen. 

my very basic conky:   https://privatebin.net/?22736a25bdc5738 … XwFeddResN

my picom.conf:  https://privatebin.net/?4fed38233d92927 … 23HQ6r1S16

and an inxi of my arch system running openbox:  https://privatebin.net/?e1cb74d23d2136f … t7fDekmgro

picom just makes my conky disappear every time and i cant make it stop doing that.  if you can, please help.  thanks.

---

BTW, I also use arch, gentoo, artix & manjaro

Ropid

Member

Registered: 2015-03-09

Posts: 1,069

Re: Has anyone managed to get picom to work with conky in openbox?

I noticed this line here in your conky config, it looks like a typo:

own_wnidow = yes,

Maybe that's the problem? What happens when you fix the spelling and change it into "window"?

What's happening when you run picom with an empty config? You don't have to remove your current config to experiment, you can start picom like this:

picom --config /dev/null

It will then ignore your config. You can then repeatedly kill it and add options to see if you can find ones that work or break things:

picom --config /dev/null --experimental-backends --backend glx --vsync

This "--experimental-backends" plus "glx" is what's the best picom settings here for me with an AMD RX480 card. That "--experimental-backends" reduces the latency noticeably compared to default. That experimental-backends option can't be put into the picom config. It has to be on the command line.

Last edited by Ropid (2020-06-16 00:11:30)

Lizzi

Member

Registered: 2016-05-15

Posts: 40

Re: Has anyone managed to get picom to work with conky in openbox?

I noticed this line here in your conky config, it looks like a typo:

own_wnidow = yes,

Maybe that's the problem? What happens when you fix the spelling and change it into "window"?

What's happening when you run picom with an empty config? You don't have to remove your current config to experiment, you can start picom like this:

picom --config /dev/null

It will then ignore your config. You can then repeatedly kill it and add options to see if you can find ones that work or break things:

picom --config /dev/null --experimental-backends --backend glx --vsync

This "--experimental-backends" plus "glx" is what's the best picom settings here for me with an AMD RX480 card. That "--experimental-backends" reduces the latency noticeably compared to default. That experimental-backends option can't be put into the picom config. It has to be on the command line.

TY for catching my typo! 

Ok so after fixing the typo and then trying each of those suggestions, the result was unfortunately the same... conky disappears from my screen and returns when i close the terminal i ran the picom commands in..

it used to be compton -c something or other i think.. it's been years

ah well.  maybe compositing is over rated?

TY for having a look at it.  Much appreciated!

Last edited by Lizzi (2020-06-16 02:01:33)

---

BTW, I also use arch, gentoo, artix & manjaro