RetroArch icon indicating copy to clipboard operation
RetroArch copied to clipboard

RetroArch is half off-screen when fullscreen

Open klazoklazo opened this issue 1 year ago • 14 comments

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

RetroArch is half off-screen when fullscreen.

image

image

Expected behavior

RetroArch's fullscreen image should be inside the monitor it's displaying in.

Actual behavior

RetroArch's fullscreen image is instead pushed half of the monitors resolution to the left. This also means any monitors to the left of the used display gets to see the left half of the fullscreened RetroArch view. Moving the fullscreened view between monitors somehow fixes this, but the view regenerating when reopening the program or launching a game reproduces this issue.

Disabling Wayland through Flatseal and forcing it to fallback to Xwayland fixes this issue, but produces a different issue.

Steps to reproduce the bug

  1. Launch RetroArch
  2. Turn on fullscreen mode

Alternatively

  1. Have fullscreen mode already enabled
  2. Launch RetroArch

Bisect Results

[Try to bisect and tell us when this started happening]

Installed through Flatpak, unsure of how to do this.

Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.19.1

Environment information

  • OS: Fedora Workstation 40
  • Compiler: None, installed through Flatpak

klazoklazo avatar Jul 13 '24 18:07 klazoklazo

I can not reproduce this issue using Fedora 40 on Wayland using GLcore video driver.

May you provide some log using ?

flatpak run org.libretro.RetroArch -v

Perhaps you are using several monitors ?

Thank you.

P.S = If it is related to the Flatpak package, it will be better to open the issue in this repository.

gouchi avatar Jul 14 '24 18:07 gouchi

Update!! I managed to fix the issue in a more permanent form by changing the monitor RetroArch displayed on in the settings. Display 0 (auto) seemingly can't decide between either of my two monitors (I am indeed using multiple monitors), so changing it to display 1 fixes the problem.

klazoklazo avatar Jul 15 '24 00:07 klazoklazo

Another update, I've moved to Ubuntu 24.04.1 LTS and tried to run RetroArch through the Flatpak and the problem is no longer fixable with the method I had described previously. I tried forcing the application to run in X11 as well but it broke in a different way, see here: https://github.com/libretro/RetroArch/issues/15259

Through this thread of Reddit comments one of the devs tried helping me in utilizing a different installation method of RetroArch but they all had issues with window decorations and apparently only the PPA version can deal with Ubuntu 24.04.1's version of libdecor-0-dev due to the others being sandboxxed.

Unfortunately after fixing that problem the PPA version similarly shows the same problem with its fullscreen mode being half off-screen with no way to fix it like in the Flatpak. I tried forcing it to run in X11 through using environment variables (full command I tried using was Exec=env GDK_BACKEND=x11 retroarch but it resulted in the window decorations breaking again and instability whenever I tried fullscreening or un-fullscreening RetroArch.

Screenshots below:

The PPA version of RetroArch running in Wayland with window decorations through manually installing libdecor-0-dev:

image

Fullscreening the setup shown above results in the same problem shown in the original post:

image

Running RetroArch in X11 results in the window decorations breaking again:

image

Fullscreening RetroArch commonly causes the window to seemingly disappear, I assume this is a crash?

image

klazoklazo avatar Dec 03 '24 03:12 klazoklazo

I have the same or very similar problem on a clean new RetroArch config. I am running KDE Wayland on Arch and I have 2 screens.

In fullscreen mode, if RetroArch's "Monitor Index" setting is set to "Auto", it will show up in a window off-center as you can see here:

Image (Log in the background, in case it helps)

Alt-tabbing makes it go to the correct position (fill the whole screen). Setting "Monitor Index" to specific monitors also works correctly. It's only the "Auto" that is failing.

@gouchi This is happening to me in both Vulkan and GLcore. Worse yet, on GLcore, even setting the "Monitor Index" does not fix the issue.

EDIT: Not sure if it's related to this issue, but this other issue seems to be more exact to what I'm experiencing: https://github.com/libretro/RetroArch/issues/17372

nfp0 avatar Feb 15 '25 11:02 nfp0

@nfp0 same setup, same problem

vulkan on arch KDE Wayland with a second monitor, I need to alt-tab everytime to fix when Monitor Index is on auto

amigthea avatar Apr 27 '25 08:04 amigthea

It looks like I have a similar issue. I'm running Kubuntu 25.04, and installed Retroarch through the flatpak. I have an external monitor attached to my laptop, which is what I want to play the games on.

Whenever I open retroarch, it starts with the upper left corner in the center of the screen:

Image

I can at least drag the window when it's like that. But when I turn it full screen, it's stuck in that position:

Image

The-Pezman avatar May 12 '25 17:05 The-Pezman

Same on Arch KDE with Wayland and 2 external monitors. RetroArch version 1.20
When it starts in the middle like that - I usually use kwin hotkeys to move the window between the monitors and it snaps to the monitor I need.

Image

0x09AF avatar Jun 09 '25 13:06 0x09AF

That doesn't work in fullscreen mode

On Mon, Jun 9, 2025 at 9:55 AM 0x09AF @.***> wrote:

0x09AF left a comment (libretro/RetroArch#16779) https://github.com/libretro/RetroArch/issues/16779#issuecomment-2955871044

Same on Arch KDE with Wayland and 2 external monitors. When it starts in the middle like that - I usually use kwin hotkeys to move the window between the monitors and it snaps to the monitor I need.

image.png (view on web) https://github.com/user-attachments/assets/35cd3798-80d1-4151-a3dc-8c5e2f559fe5

— Reply to this email directly, view it on GitHub https://github.com/libretro/RetroArch/issues/16779#issuecomment-2955871044, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABPTBHXI2T6TG6ZLELUY7UL3CWG6FAVCNFSM6AAAAABK2PUSSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJVHA3TCMBUGQ . You are receiving this because you commented.Message ID: @.***>

The-Pezman avatar Jun 09 '25 14:06 The-Pezman

That doesn't work in fullscreen mode

It works for me in fullscreen because kwin shortcuts are global. I am not sure how Flatpak works, but I use a native package

0x09AF avatar Jun 09 '25 14:06 0x09AF

Update!! I managed to fix the issue in a more permanent form by changing the monitor RetroArch displayed on in the settings. Display 0 (auto) seemingly can't decide between either of my two monitors (I am indeed using multiple monitors), so changing it to display 1 fixes the problem.

I just installed RetroArch in Bazzite 42 Fedora and was having the same issue where fullscreen put the top left corner in the middle of the screen and it would go off the screen to the bottom right. Your fix of choosing '1' in 'Monitor Index' fixed it for me, so I wanted to thank you!

tonybonesyou avatar Jul 09 '25 20:07 tonybonesyou

I have the same or very similar problem on a clean new RetroArch config. I am running KDE Wayland on Arch and I have 2 screens.

In fullscreen mode, if RetroArch's "Monitor Index" setting is set to "Auto", it will show up in a window off-center as you can see here:

Image (Log in the background, in case it helps)

Alt-tabbing makes it go to the correct position (fill the whole screen). Setting "Monitor Index" to specific monitors also works correctly. It's only the "Auto" that is failing.

@gouchi This is happening to me in both Vulkan and GLcore. Worse yet, on GLcore, even setting the "Monitor Index" does not fix the issue.

EDIT: Not sure if it's related to this issue, but this other issue seems to be more exact to what I'm experiencing: #17372

I could kiss you, sir.

Running CachyOS, KDE Plasma, 2 Monitors, and this is exactly what I needed. Thank you.

Smellbringer avatar Jul 15 '25 03:07 Smellbringer

Problem present on 1.22.1 on kwin_wayland for me.

I do not have multiple monitors, nor does setting the monitor index to something other than 0 fix it.

On gl and glcore driver the problem occurs basically all the time, on vulkan it happens around 50% of the time. When it works, it appears to first appear in the wrong place (windowed with top left corner in middle of screen, half off the screen) and then move up into the right position (fullscreen).

Workaround for now is to add a window rule in kwin for the application to force fullscreen.

Looks like a race condition / timing type issue with when retroarch chooses to make the newly created window fullscreen and/or where it places the window briefly before it does so.

trr avatar Nov 22 '25 04:11 trr

arch on kde here, have the same problem on wayland, and only one monitor connected, cant seem to find a combination of options that fixes it. so am doing same window rule fix as @trr

v4u6h4n avatar Nov 26 '25 08:11 v4u6h4n

Same issue, new Arch install using KDE, dual monitor setup

joshcancode avatar Nov 28 '25 19:11 joshcancode

I have the same issue here. My setup is also a dual monitor (both screens same resolution, refresh rate and color profile) in KDE Wayland, cachyOS, amdgpu driver, Retroarch 1.22.2 compiled from git. When using X11, I don't have any problems at all with Retroarch, although I had problems with mismatched refresh rates above 60Hz when playing anything (probably a X11 issue). I've manage to workaround this retroarch fullscreen problem by creating window rules in KWin:

Image

delazerirafael5 avatar Dec 21 '25 06:12 delazerirafael5

Just wanted to confirm the same issue here. Arch Linux, KDE, Wayland, single monitor. Trying to use native fullscreen within RetroArch causes the top left corner of the window to draw at the center 0,0 of my display, causing three quarters of the window to be cut off. Using delazerirafael5's above workaround resolves the problem, although I set my rule to "Apply initially" rather than "Force". This works well, just with the added detriment of not being able to cycle between fullscreen and windowed mode without an application restart.

Avilnetro avatar Jan 13 '26 12:01 Avilnetro