I3 Trasnparency Issues please help

it can happen … one of the reasons why i do comment picom per default :wink:

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.

2 Likes

That was a completely unnecessary comment. So much for help.

1 Like

Thank you. That worked

what exactly worked?

now I am completely confused :roll_eyes:

55555 that normal for me :blush:

1 Like

It would be hard to imagine that you wouldn’t be confused at this point.

2 Likes

come on :notes:
I know we all here like the comedy… but a new user need help :building_construction:

I gave it my all. In the end - you were the man who helped!

1 Like

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

Edit
@edub
Welcome to the forum

1 Like

Her

1 Like

sorry for that
my mistake :grimacing:

I’ll do a write up later as to how I get transparency as well as blur rounded corners etc.

Thank you, very much.

1 Like

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 &

Me too? Not enough info. :face_with_diagonal_mouth:

I got it working, probably too late for anyone in this thread. I learned alot about picom and tty. Thank you everyone.

I faced same issue as u. So can u describe how did u fixed it?

welcome at the forum and the purple side of the arch :enos: :vulcan_salute:

It would be better to open a new post and give better info on what exactly is your issue.
like:
https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/

give a lot possible ways to provide information and logs.

Hardware information:

inxi -Fxxc0z --no-host | eos-sendlog

Boot log:

journalctl -b -0 | eos-sendlog

–closing–