search

raspberrypi / bookworm-feedback

12 stars 1 forks source link

`chromium-browser --kiosk` display anomaly #31

Open JinShil opened 9 months ago

JinShil commented 9 months ago

Step to reproduce:

  1. Use 2023-09-11 Bookworm Beta OS image
  2. Boot to desktop
  3. Open lxterminal
  4. Run the command chromium-browser --kiosk https://raspberrypi.com
  5. Observe that the browser appears to get reduced to a single-pixel horizontal line at the top of the screen. The desktop panel is all black, and the desktop and lxterminal window are still displayed

Interestingly running the same command from an SSH terminal session works fine.

lurch commented 9 months ago

@tobybroberts I think you also ran into this at some point - do you remember what the fix was?

ferdiamg commented 8 months ago

Experiencing exactly the same right now on the latest official RaspiOS release. What fixed it for me right now (just as I typed the first sentence and after tinkering for 5hrs, LOL) was: --start-maximized and --start-fullscreen

JinShil commented 8 months ago

I can confirm that --start-maximized alone, without --start-fullscreen works around the issue.

But why is this necessary, and why does it work fine without those arguments when launching from and SSH terminal session?

ferdiamg commented 8 months ago

I can confirm that --start-maximized alone, without --start-fullscreen works around the issue.

But why is this necessary, and why does it work fine without those arguments when launching from and SSH terminal session?

Wayland/Wayfire are super restrictive when it comes to SSH commands changing apps state. No idea what mechanism intercepts the correct maximized window behaviour, however I do start these from an autostart.sh now anyways which always runs them from the Pi itself.

I am puzzled on why it even works for you through SSH as most commands result in "$DISPLAY not found" or similar error messages because the command is being run from your main machine and not the PI itself. Thinking about it now.. maybe it works because your main machine is having a correct setup that runs the --start-maximized under the hood already and when ran on your Pi directly, its missing and you need to state it explicitly.. Just a thought though.

popcornmix commented 8 months ago

I've heard this issue is resolved with 0.8.0 release of wayfire. (Although the bump introduces new issues, so may not appear imminently).

JinShil commented 7 months ago

As of today, with the latest updates to Bookworm, this is still an issue.

Guruabyss commented 4 months ago

As of today Bookworm V12 still has this issue!

popcornmix commented 4 months ago

I've tested: chromium-browser --kiosk https://raspberrypi.com On pi5 bookworm with labwc enabled (this is planned as a default update "soon").

The browser opened fullscreen just fine. So I suspect this issue will be resolved in a coming update.

Zebra353 commented 3 months ago

On Pi4 64bit OD release 2024-03-15 still an issue.

PHCPartsAlexis commented 1 week ago

Can confirm the same behaviour still on the latest updates today. Adding --start-maximised was the workaround.

niccoreyes commented 3 days ago

I can also confirm as of July 2, 2024 , "chromium-browser --start-maximized --start-fullscreen" fixes the issue on wayland as a workaround

--start-fullscreen alone fails to render chromium properly in wayland/wayfire mode, but works alrite on X11 mode