Picom autostart issue after installing cava #6073
Unanswered
Mar6leS9da
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey guys, so I've installed arch with i3 on my PC, and with some effort got it riced to a point where i like it, Picom was working fine before the cava install, after I installed cava and ran it, it muted my audio, and broke YouTube playback for me, I restarted my PC and got some errors, (which I didn't really understand) but recreated the bug I ran into by running cava again, I decided to uninstall it, got that done and restart gives no errors, but now my picom doesn't start up when I boot the system, I can run it in terminal just fine as even a daemon
my i3 config for picom looked like this:
exec_always --no-startup-id picom --experimental-backends -b
I thought adding the config path to the line might fix things so i changed the line to:
exec_always --no-startup-id picom --config /$home/.config/picom/picom.conf --experimental-backends -b
aaaaand nothing, I scoured the net for help, but most people are either just forgetting to put
exec_always
or something like that, any help is appreciatedUPDATE: after some time I recognized that the line I originally posted had an extra space before
-b
, (both here and in the actual config file) however changing this and testing it in both configurations (with and without config path) failed to fix the issue. I've appended the above code to reflect the changes I made as the issue still stands, I'm not going to reinstall cava to try and get the errors to appear again for fear of further breaking things, I saved my essential config files to the cloud to conserve my work and reinstalled arch with i3 and reapplied the relevant config files and everything works fine againBeta Was this translation helpful? Give feedback.
All reactions