4B+Which model Pi are you using?
I know it's overkill, but I'm reusing the hardware that someone else got to put one of those dedicated sign OS's on. It worked for a while, and then got stuck on the OS's splash screen, and so I'm redoing it.
That makes sense. I don't keep track of codenames. Too confusing, and no direct indication anywhere. It's "whatever the official imager took a while to download yesterday, when I burned the card".If by "TODAY'S Raspberry Pi OS" you mean RPiOS Bookworm and your Pi has at least 2GB RAM it won't be using X it'll be using Wayland so xdotool won't work.
That does indeed work! I had to set my visual preferences again, but I guess that's expected.You can switch to X via the advanced option menu of sudo raspi-config. Your .desktop fiel will still work.
And the old familiar taskbar widgets are back! I was slightly wondering about that too...
That's actually abbreviated to show the idea. I do use absolute paths in every cronjob. Even >> to a preexisting file with wide-open permissions does nothing. As if cron isn't even running at all.On cron:
No idea why it won't even echo test > logfile. Are you checking in the right place for the logfile? With a relative path it will be in the user's home directory. For root that's /root.
I know about not having a desktop, from a previous rig. export DISPLAY=:0 in the same script, before starting anything with a GUI.Starting Desktop applications from cron is particularly tricky. @reboot jobs run before the desktop has started and all jobs must be told which desktop to connect to. It;s a liitle easier when using a systemd service as those can be made to run only after the desktop has started.
I didn't realize that @reboot runs so early though, even for the user. That might have been a problem anyway, even if it did run at all. My other rig is on 24/7 and has specific times, so the startup sequence doesn't matter there.
Statistics: Posted by AaronD — Tue Sep 03, 2024 11:27 pm