Only half the screen is used

[Mattat01]

Hi,
Has anyone come across this situation before? The whole screen is working, but the webpage being displayed only covers half the screen (the splash screen is still visible behind it). This is running on a Pi5 using the nightly build of FullPageOS (from a couple of months ago).

It has been working full screen for months, until today, and I haven't changed anything recently. We had a power failure last night, but it isn't a broken screen, or a problem with the pi hardware, as the display works perfectly. Is there a setting somewhere that might be forcing the display width (maybe the power failure corrupted a settings file???)? I have a cronjob that turns the display off at night and back on in the morning, which has been working fine for months too.

I've upgraded everything, so I don't think it is a Bookworm issue (again, not that I'd changed anything recently).

I'm not sure what else to try.

If anyone has any ideas I'd appreciate your input.

My config.txt file is below:

# For more options and information see
# http://rptl.io/configtxt
# Some settings may impact device functionality. See link above for details

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# Additional overlays and parameters are documented
# /boot/firmware/overlays/README

# Automatically load overlays for detected cameras
camera_auto_detect=1

# Automatically load overlays for detected DSI displays
display_auto_detect=1

# Automatically load initramfs files, if found
auto_initramfs=1

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2

# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

# Disable compensation for displays with overscan
disable_overscan=1

# Run as fast as firmware / board allows
arm_boost=1

[cm4]
# Enable host mode on the 2711 built-in XHCI USB controller.
# This line should be removed if the legacy DWC2 controller is required
# (e.g. for USB device mode) or if USB support is not required.
otg_mode=1

[cm5]
dtoverlay=dwc2,dr_mode=host

[all]
# enable raspicam
start_x=1
#gpu_mem=128
disable_splash=1

[guysoft]

Nope, never saw that.
Does it happen for every url?

[Mattat01]

Good question, I hadn't tried, but yes, it also displays google.com on the left half of the screen.
Could it be a browser setting (like Windows can be docked to an edge), or a setting that should be set to launch fullscreen? I poked around Chromium documentation but couldn't find anything helpful. I did find chromium/Default/Preferences, which contained
window_placement":{"bottom":1076,"left":4,"maximized":false,"right":1916,"top":20,"work_area_bottom":1080,"work_area_left":0,"work_area_right":1920,"work_area_top":0}} which makes it look to me like it is supposed to open a window to the full monitor resolution, but FullPageOS doesn't have the windows border so perhaps this is ignored anyway.

Occassionally since this behavious started, the browser window never opens (maybe 1 in 5 time I reboot, or less frequently), and just the splashcreen remains.

I have also poked about in the scripts folder. I don't know what behaviour is expected, but running . fullscreen results in an error Your windowmanager claims not to support _NET_ACTIVE_WINDOW, so the attempt to activate the window was aborted. xdo_activate_window on window:14680067 reported an error
running . refresh and . safe_refresh produce the same error.

My final tinkering found:

xrandr --current
Can't open display

Again, I'm not certain that this should work (I note the rotate.sh workaround for the Pi4, but not sure if it is also used for Pi5, but I diddn't successfully run that either).

The final interesting thing I found: You can see in the photo above the grey vertical line in the middle (it is the vertical scroll bar). The window is actually sized to half width and my calendar flows down the page. If I run . run_onepageos i get the below respose (which is not surprising):

feh ERROR: Can't open X display. It *is* running, yeah?
Error: Can't open display: (null)
Failed creating new xdo instance
Opening in existing browser session.

with the last 3 lines repeating until I ^C out of it, but then the window acts like it is full screen (in that the scroll bar is gone and the flow of the calendar looks like it did before when it was displaying full screen), but the page is still only showing on the left half of the screen, with the os splashscreen still visible on the right. It is like when it boots it deliberately sets the width of the window to half width, but when I rerun that script it gets confused and tries to display full width in the same half width window.

Hopefully something in that gives someone an idea! If not I can try reimaging and start from scratch.