I had the same issue just now, I fixed it by calling a script in autostart rather than chromium-browser directly, I suppose it has something to do with display envvars, if someone smarter knows why it works let me know.
/home/{USER}/start_browser.shMake sure it's executable: chmod +x start_browser.sh
And my ~/.config/wayfire.ini file looks like this:You don't need to call /bin/sh apparently autostart already does it
Also, note that /etc/wayfire/defaults.ini contains the autostart_wf_shell = false line, I'm not sure if it is needed again in ~/.config/wayfire.ini
/home/{USER}/start_browser.sh
Code:
#!/bin/bashchromium-browser --start-fullscreen --no-first-run "url"And my ~/.config/wayfire.ini file looks like this:
Code:
[autostart]autostart_wf_shell = falsechromium = /home/{USER}/start_browser.shAlso, note that /etc/wayfire/defaults.ini contains the autostart_wf_shell = false line, I'm not sure if it is needed again in ~/.config/wayfire.ini
Statistics: Posted by juandl — Fri May 03, 2024 1:35 am