I've used pis in Kiosk Mode for years, and have just built a new one using a pi4 and Wayland under Bookworm and had no end of issues getting it to behave as expected.
Most of it now works, but one thing that doesn't is that chromium always seems to start on the 'wrong' HDMI port ... i.e. if you unplug the HDMI cable from HDMI0 and insert it into HDMI1 I can see the browser. On HDMI0 a very small slither (a few pixels) are visible right at the top of the screen.
However, when running Chromium from the command line (rather than from .config/wayfire.ini's autostart) it works as expected.
As a workaround I tried creating a shell script as follows;
This works perfectly when ran from the command line (or cron) but exhibits the same behaviour with the browser being 'off screen' when started from within wayfire.ini
In the interim, the (very hacky) workaround I've found is to run my start script periodically from cron, which works as expected.
But why doesn't this work;
Also, to get rid of the desktop commenting out #panel and #background were not sufficient I had to remove them also from [autostart-static] in `/etc/wayfire/defaults.ini`
Any suggestions of what I'm doing wrong here (I've also tried adding `dtoverlay=vc4-kms-v3d,nohdmi1` to /boot/config.txt) ?
Most of it now works, but one thing that doesn't is that chromium always seems to start on the 'wrong' HDMI port ... i.e. if you unplug the HDMI cable from HDMI0 and insert it into HDMI1 I can see the browser. On HDMI0 a very small slither (a few pixels) are visible right at the top of the screen.
However, when running Chromium from the command line (rather than from .config/wayfire.ini's autostart) it works as expected.
As a workaround I tried creating a shell script as follows;
Code:
export DISPLAY=:0/usr/lib/chromium-browser/chromium-browser --window-position=0,0 --enable-pinch --fast --fast-start --kiosk --noerrdialogs --disable-translate --no-first-run --disable-pinch --overscroll-history-navigation=disabled --disable-features=TouchpadOverscrollHistoryNavigation --disable-restore-session-state --disable-infobars --kiosk --enable-crashpad https://127.0.0.1/In the interim, the (very hacky) workaround I've found is to run my start script periodically from cron, which works as expected.
But why doesn't this work;
Code:
[output:HDMI-A-1]mode = 1920x1080@60#[output:HDMI-A-2]#mode = 1920x1080@60[autostart]#panel = wfrespawn wf-panel-pi#background = wfrespawn pcmanfm --desktop --profile LXDE-pixdg-autostart = lxsession-xdg-autostartscreensaver = falsedpms = falsekiosk = /usr/lib/chromium-browser/chromium-browser --enable-pinch --fast --fast-start --start-maximised --kiosk --noerrdialogs --disable-translate --no-first-run --disable-pinch --overscroll-history-navigation=disabled --disable-features=TouchpadOverscrollHistoryNavigation --disable-restore-session-state --disable-infobars --kiosk --enable-crashpad --ozone-platform=wayland 'https://127.0.0.1'Any suggestions of what I'm doing wrong here (I've also tried adding `dtoverlay=vc4-kms-v3d,nohdmi1` to /boot/config.txt) ?
Statistics: Posted by rshenm — Sun Jan 21, 2024 1:22 pm — Replies 0 — Views 63