Request: upgrade picom to v/12.5-1

[Nokkaelaein]

When speaking of glitches/hacks with picom's current version, are you referring to v/9.1 (bookworm) - or latest build v/12.5 ?

The latest one, i.e. built it from the available current version from github. Sorry about being ambiguous there; everything I thought out loud above is about my experiences with that github version, not the old one in the MX repo.

[siamhie]

@Nokkaelaein Which backend is your config using? The default is xrender but I've switched to glx.

Yeah, glx most of the time for me as well.

Usually I'm passing it directly as a command line parameter, based on whether it's running inside a VM or not. So on this laptop I'm currently writing this with, picom has been launched with something like:

Code: Select all

picom -bcf --backend glx -D 20 -O 0.25 -I 0.25 -l -13 -t -13 -r 15 -o 0.8 --blur-method none --vsync --no-use-damage --no-fading-destroyed-argb --shadow-exclude 'class_g = "conky"'

Have you tried using it with the conf file?

Code: Select all

/usr/share/doc/picom/examples/picom.sample.conf

[Nokkaelaein]

Have you tried using it with the conf file?

Yes.

[ceeslans]

Could we please get back on track, i.e to the actual request to upgrade picom?
@Stevo could you please look into backporting picom-12.5-1 (trixie) for MX23 testrepo. Thanks in advance !

[Stevo]

OK, I'm giving it a try. It needs a backport of libconfig-dev first...maybe that's why the version directly from github is problematic?

[siamhie]

OK, I'm giving it a try. It needs a backport of libconfig-dev first...maybe that's why the version directly from github is problematic?

Just to let you know, I was able to get it built.

I did download the source for picom 12.5 back in Nov and only had to install 3 dev libraries for it to build.

[oops]

OK, I'm giving it a try. It needs a backport of libconfig-dev first...maybe that's why the version directly from github is problematic?

Yes, probably I had: libconfig Dependency libconfig found: NO found 1.5 but need: '>=1.7'

[Stevo]

I bundled it with the unrelated jgmenu update and the new libconfig in a zip, so you'll need to install the libconfig11 deb first, or just wait for it in the test repo.

https://drive.google.com/file/d/1u7PJm2 ... sp=sharing

Siamhie's success in building it is a bit odd in this light, to be honest.

[ceeslans]

@Stevo Thanks for backporting picom 12.5-1 and related libconfig11 to MX23.
Checked it out on a recent snapshot, gave it a good try-out (with xrender as backend) both on my MXFlux and Devuan setup. Picom 12.5-1 is rock solid on both systems and definitely less memory hungry than version 9.1-1 - on startup and during operation.
I'm a happy camper...

[siamhie]

Siamhie's success in building it is a bit odd in this light, to be honest.

@Stevo I was only following what the readme said. All the dev libraries for Debian systems.

Code: Select all

### Dependencies

Assuming you already have all the usual building tools installed (e.g. gcc, python, meson, ninja, etc.), you still need:

* libx11
* libx11-xcb
* xproto
* xcb
* xcb-util
* xcb-damage
* xcb-xfixes
* xcb-shape
* xcb-renderutil
* xcb-render
* xcb-randr
* xcb-composite
* xcb-image
* xcb-present
* xcb-glx
* pixman
* libconfig
* libdbus (optional, disable with the `-Ddbus=false` meson configure flag)
* libGL, libEGL, libepoxy (optional, disable with the `-Dopengl=false` meson configure flag)
* libpcre2 (optional, disable with the `-Dregex=false` meson configure flag)
* libev
* uthash

On Debian based distributions (e.g. Ubuntu), the needed packages are

```
libconfig-dev libdbus-1-dev libegl-dev libev-dev libgl-dev libepoxy-dev libpcre2-dev libpixman-1-dev libx11-xcb-dev 
libxcb1-dev libxcb-composite0-dev libxcb-damage0-dev libxcb-glx0-dev libxcb-image0-dev libxcb-present-dev 
libxcb-randr0-dev libxcb-render0-dev libxcb-render-util0-dev libxcb-shape0-dev libxcb-util-dev libxcb-xfixes0-dev 
meson ninja-build uthash-dev
```