You are not logged in.
Pages: 1
Hello I have this error Xlib: ignoring invalid extension event 161 & 146, the home directory glitches etc and its has something to with picom but I searched that if I start picom like this picom -b --backend glx --vsync & it goes away and it does. But how do I autostart with that comment, picom starts like normally not with -b --daemon in the background, I have to manually start it from the terminal. Im supposed to put picom -b --backend glx --vsync & into /home/.config/bunsen/autostart right?
Last edited by pozric (2024-09-03 14:47:46)
Offline
Yes, change the command in the autostart file.
You must unlearn what you have learned.
-- yoda
Online
Ok thanks, Ive put it right under like this but It starts normally and I get those Xlib errors
bl-compositor --start
picom -b --backend glx --vsync &
Offline
Comment out the first line that starts the bl-compositor.
# bl-compositor --start
picom -b --backend glx --vsync &
If the compositor is already running, your new command fails silently.
You must unlearn what you have learned.
-- yoda
Online
Probably in bunsen the 'correct' way to deal with this is to change the config file at:
$HOME/.config/picom.conf
so that various 'restart compositor' menus keep doing what they are supposed to do.
Offline
Ah ok thanks man my picom.conf is simple like this:
#################################
#
# Backend
#
#################################
# Backend to use: "xrender" or "glx".
# GLX backend is typically much faster but depends on a sane driver.
backend = "glx";
#backend = "xrender"
# Unredirect all windows if a full-screen opaque window is detected, to maximize performance for full-screen windows, like games.
# Known to cause flickering when redirecting/unredirecting windows.
unredir-if-possible = true;
vsync = true;
Last edited by pozric (2024-09-03 13:15:07)
Offline
Do I need to add it to .bashrc to?
Offline
Ok thanks guys, this worked # bl-compositor --start, I feel silly for starting a thread for this it was that simple, but I searched and searched before I posted. Last question if I find a simple script to kill picom before starting a game and switch it on and off do I just add it to the autostart too?
Last edited by pozric (2024-09-03 13:57:21)
Offline
There should be a menu option named 'compositor' which should have start, stop, restart and such (unless I misunderstood the question).
You could also write a little launcher script like:
bl-compositor --stop
nameOfTheGame
bl-compositor --start
(untested)
Offline
Ok yeah I dont have that compositor in jgmenu anymore, I think its because I uninstalled picom early on but installed it now again because of screen tearing which I didnt notice before. I guess I can add it to jgmenu again in user settings.
This line unredir-if-possible = true; is for when you game etc, but just to be sure I kill it manually before I start the game, there is probably scripts to add to lutris and such.
Anyways thanks for the help guys:)
Last edited by pozric (2024-09-03 14:49:02)
Offline
There should be a menu option named 'compositor' which should have start, stop, restart and such (unless I misunderstood the question).
You could also write a little launcher script like:
bl-compositor --stop nameOfTheGame bl-compositor --start
(untested)
Thanks I will try with scripts:)
Offline
But how do I autostart with that comment, picom starts like normally not with -b --daemon in the background, I have to manually start it from the terminal. Im supposed to put picom -b --backend glx --vsync & into /home/.config/bunsen/autostart right?
There's a file for setting bl-compositor (picom) startup options: /etc/bunsen/picom-startup
If you edit that, there's no need to change the way bl-compositor is launched from ~/.config/bunsen/autostart
Menu > User Settings > Compositor > Edit compositing system settings (root)
Changes there will affect all users, but things like glx backend are related to the hardware you have, so probably everyone will want the same.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Thanks johnraff and others for helping, I ended up creating the 20-intel.conf in /usr/share/X11/xorg.conf.d/ and add the tearfree option
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "TearFree" "true"
EndSection.
instead wich I struggled with though, turns out i didnt have xserver-xorg-video-intel installed after that it worked. This seems to work better for me, and I saw in tutorials about linux gaming that a lot of people recommend it.
Last edited by pozric (2024-09-07 10:13:54)
Offline
Pages: 1