it can happen … one of the reasons why i do comment picom per default
To not go into circles go and do NOT enable it in the config and first try to start it manually while logged in to i3 without picom enabled p.d. …
simply try different start commands from terminal: picom -b
or with the config shipped with EndeavourOS: picom --config ~/.config/picom.conf
so you will get some output and you will see if the command and options working for you.
she says that was the solution
picom --config ~/.config/picom.conf
but if I use in my config file
exec --no-startup-id picom -b
gives the same
so I was a little confused for what worked
but okay it worked for her
as long as it works then it is good
A day late and a $ short on the login issue. I had similar problems with Openbox and the solution was in: Openbox-session not starting (Solved)
Changed the default in autostart from picom -CGb &
to picom --experimental-backends --vsync &