I am on a fresh install of EndeavourOS: ext4 luks, i3wm.
I chose the autologin option.
When I enable picom for transparency (uncomment the picom line without changing flags), I am not able to login anymore. I see the login Manager, when i type the correct password the screen is black for two seconds, after that I see the login prompt again.
If I comment the picom line on another tty, the login is OK again.
It’s best to not run picom as soon as your system logs in. As @lucidae said best to delay it with sleep 2 && picom -b --config /home/s4ndm4n/.config/picom/picom.conf --experimental-backends you only need the --config part if you’re using custom configuration file if not you only need sleep 2 && picom -b --experimental-backends
or you can create a .desktop file and put it in /home/s4ndm4n/.config/autostart folder. And comment the picom line from i3 config file.
GenericName=Picom X compositor
Comment=Picom is a standalone compositor for Xorg, suitable for use with window managers that do not provide compositing.
TryExec=bash -c "sleep 3 && picom -b --experimental-backends"
Exec=bash -c "sleep 3 && picom -b --experimental-backends"
My i3 config file does not like the “sleep” command, it says that there is an error in the config file. I tested the “startup-delay” switch of the exec command, this does not trigger a syntax error in the config file but does not solve the initial problem.
If i run picom in the terminal, my session is immediately logged out and I cannot log in again.
Well, it is a fresh install of EOS but I checked that anyway. There is no compton process.
I had this issue, so I commented picom away and used EOS for some hours, took the comments out and it mysteriously started working. I don’t know if I did anything else that could have fixed it other than updating the system.
The man page for picom says about option -b:
Daemonize process. Fork to background after
initialization. Causes issues with certain
Now I am able to login - BUT only for 3 seconds, after that the login screen appears again.
There is no output regarding picom. But I realized that every time picom starts a coredump appears. So the session crashes and this is the reason why I need to login again.
btw: I started from scratch and installed a fresh eos system on both my Thinkpad T440s and my Thinkpad Yoga 260. I just installed and uncommented the “picom”-line in the default i3 config file.
Yoga 260: Picom just works
T440s: The problem of this thread.
Both systems have Intel HD graphics