I'm using a Raspberry Pi 3B, connected to a touch screen (HDMI/USB), to run a browser in kiosk mode.
The basic install is the following (not including the browser installation etc):When running this on Bullseye (Debian 11) everything works as expected: startx shows a black screen with a cursor.
(it then shows the browser but I didn't include it to simplify).
But when doing the exact same thing in Bookworm (Debian 12) there is only a black screen, no cursor.
(and no browser in my actual setup).
Before I try to run startx both Bullseye and Bookworm will show the command line on the connected screen so no difference up until that point.
If I look in .xsession-errors there is no difference between Bullseye and Bookworm.
I was using the Raspberry Pi Imager to create the installation and in the latest version (32-bit) I noticed that if I select "Raspberry Pi 3" as my hardware it will not show me Bookworm as an install option, only "legacy" Bullseye. I do not know if this is related or not.
I did run raspi-config and tried "switch between X and Wayland backends" but that didn't make a difference.
will show the connected display in both Bullseye and Bookworm. shows the same thing as well in both OS's (and the same thing for the browser if its started).
Anyone got any idea why this is working on Bullseye but not in Bookworm for me?
The basic install is the following (not including the browser installation etc):
Code:
sudo apt updatesudo apt dist-upgradesudo apt install xserver-xorg x11-xserver-utils xinit openboxsudo nano /etc/xdg/openbox/environmentexport DISPLAY=':0.0'sudo nano /etc/xdg/openbox/autostartxset -dpms # turn off display power management systemxset s noblank # turn off screen blankingxset s off # turn off screen saversudo nano ~/.bash_profile[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && startx --sudo raspi-configSystem Options -> Boot / Auto Login -> B2 Console Autologin(it then shows the browser but I didn't include it to simplify).
But when doing the exact same thing in Bookworm (Debian 12) there is only a black screen, no cursor.
(and no browser in my actual setup).
Before I try to run startx both Bullseye and Bookworm will show the command line on the connected screen so no difference up until that point.
If I look in .xsession-errors there is no difference between Bullseye and Bookworm.
I was using the Raspberry Pi Imager to create the installation and in the latest version (32-bit) I noticed that if I select "Raspberry Pi 3" as my hardware it will not show me Bookworm as an install option, only "legacy" Bullseye. I do not know if this is related or not.
I did run raspi-config and tried "switch between X and Wayland backends" but that didn't make a difference.
Code:
DISPLAY=:0 xrandrCode:
ps -ef|grep startxAnyone got any idea why this is working on Bullseye but not in Bookworm for me?
Statistics: Posted by AnAx — Mon Dec 18, 2023 1:54 am