Thanks for the response!
I forgot to mention—I did try switching back to X11. Unfortunately, under X11, the site won’t load properly in Chrome. It just hangs on a black screen and throws a codec error. This wasn’t an issue before upgrading to Bookworm, so I’m not sure what changed. Interestingly, I don’t encounter this problem when using labwc, which is why I’ve decided to stick with it for now.
As for the autostart setup: since this Pi sits on my desk and I’m the only user, I initially used the system-wide autostart file. However, I’ve since moved both the Chromium launch and the Bash script call into the user-specific autostart file ($HOME/.config/labwc/autostart) to test if that makes a difference. Unfortunately, the behavior is the same—the bash script doesn’t seem to execute at startup.
Right now, I’m focused on figuring out why the Bash script runs fine manually from the terminal but doesn’t execute when called via the autostart file.
How can I enable logging to capture any errors or output from the script during startup? If nothing shows up in the logs, I’ll assume the script isn’t being triggered at all. But if there are entries, that could help pinpoint what’s going wrong.
I forgot to mention—I did try switching back to X11. Unfortunately, under X11, the site won’t load properly in Chrome. It just hangs on a black screen and throws a codec error. This wasn’t an issue before upgrading to Bookworm, so I’m not sure what changed. Interestingly, I don’t encounter this problem when using labwc, which is why I’ve decided to stick with it for now.
As for the autostart setup: since this Pi sits on my desk and I’m the only user, I initially used the system-wide autostart file. However, I’ve since moved both the Chromium launch and the Bash script call into the user-specific autostart file ($HOME/.config/labwc/autostart) to test if that makes a difference. Unfortunately, the behavior is the same—the bash script doesn’t seem to execute at startup.
Right now, I’m focused on figuring out why the Bash script runs fine manually from the terminal but doesn’t execute when called via the autostart file.
How can I enable logging to capture any errors or output from the script during startup? If nothing shows up in the logs, I’ll assume the script isn’t being triggered at all. But if there are entries, that could help pinpoint what’s going wrong.
Statistics: Posted by Drewbsterz — Wed Sep 03, 2025 3:46 pm