Hi folks
I was wondering if anyone else had come across this issue or had any workarounds?
I've got a headless setup for a Pi Zero W with an OLED screen. I created a new SD card with the latest Trixie version of Raspberry Pi OS and although my bash and Python scripts still run OK (after I make some slight tweaks re Python virtual environments) I've noticed that two previous aspects no longer work that were OK in Bullseye - sleep and read commands.
I mainly use sleep to slow down some of the processes to ensure users have time to read what is on the screen and occasionally (e.g., due to an error) want to halt things processing so historically used the read command as a way to put things on hold waiting for user input (which wouldn't arrived due to lack of keyboard).
For the latter I guess I can instead put it in a loop, e.g., waiting for a file that never appears, however sleep not working is more annoying.
I've tried markedly increasing sleep times (from 1 or 2 to 1000 or 2000!) but it makes no difference. If I SSH in then I can see with a time command it is pausing appropriately, but running the same scripts when starting up headless seems to cause the problem.
Has something changed in Trixie that it now ignores sleep and read for headless setups? I've had a search but can't find much (mainly ended up on pages about sleep/suspend settings rather than bash scripting!).
Thanks
I was wondering if anyone else had come across this issue or had any workarounds?
I've got a headless setup for a Pi Zero W with an OLED screen. I created a new SD card with the latest Trixie version of Raspberry Pi OS and although my bash and Python scripts still run OK (after I make some slight tweaks re Python virtual environments) I've noticed that two previous aspects no longer work that were OK in Bullseye - sleep and read commands.
I mainly use sleep to slow down some of the processes to ensure users have time to read what is on the screen and occasionally (e.g., due to an error) want to halt things processing so historically used the read command as a way to put things on hold waiting for user input (which wouldn't arrived due to lack of keyboard).
For the latter I guess I can instead put it in a loop, e.g., waiting for a file that never appears, however sleep not working is more annoying.
I've tried markedly increasing sleep times (from 1 or 2 to 1000 or 2000!) but it makes no difference. If I SSH in then I can see with a time command it is pausing appropriately, but running the same scripts when starting up headless seems to cause the problem.
Has something changed in Trixie that it now ignores sleep and read for headless setups? I've had a search but can't find much (mainly ended up on pages about sleep/suspend settings rather than bash scripting!).
Thanks
Statistics: Posted by EDIflyer — Mon Oct 06, 2025 6:49 pm