Is 'killall compton' a "proper way" of disabling compositing?

soocki · 2017-05-30 16:34:46

Is it? I found it in the other thread and just wondering. I ask because:

Before:

After:

Ps. Hmm those images didn't work quite right did they? Ps2. Yes they did.

Last edited by soocki (2017-05-30 16:56:30)

hhh · 2017-05-30 17:24:48

If you don't want it to autostart with your session, comment it out of ~/.config/openbox/autostart.

Otherwise, yes, it's fine to kill it like that, or with pkill compton.

hhh · 2017-05-30 17:26:24

Upgrading your kernel via jessie-backports or upgrading to stretch will most likely fix your icons, it's a known issue.

Last edited by hhh (2017-05-30 17:29:56)

soocki · 2017-05-30 17:34:35

hhh wrote:

If you don't want it to autostart with your session, comment it out of ~/.config/openbox/autostart.

Thank you.

Head_on_a_Stick · 2017-05-30 17:38:28

Those artefacts are usually caused by the acceleration method used by the DDX graphics driver.

@OP, do you have an Intel card?

If so, try this fix:

soocki · 2017-05-30 17:49:56

Head_on_a_Stick wrote:

@OP, do you have an Intel card?

I sure do.

Head_on_a_Stick wrote:

If so, try this fix:
https://forums.bunsenlabs.org/viewtopic … 072#p20072

Worked like a charm.

Head_on_a_Stick wrote:

Those artefacts are usually caused by the acceleration method used by the DDX graphics driver.

Thanks for an explanation.

Last edited by soocki (2017-05-30 23:51:18)

#1 2017-05-30 16:34:46