(Linux) slowly takes longer going into/out of fullscreen on any app.

[Mnky313]

I'm having this weird issue on my main laptop where going into and out of fullscreen (any app) causes the system to pause/stutter, for probably the first few hours after rebooting it's totally fine but over time slowly gets worse and worse to the point where it freezes for several seconds everytime anything goes into fullscreen. (NOT just exclusive fullscreen, but anything including youtube videos, browsers, remote desktop, etc.)

I'm running arch (6.6.10-arch1-1) with GNOME on X11, latest nvidia drivers (from pacman).

Anyone have any idea what is going on?

It's quite hard to find anything about this because most results are people complaining about stutters when in fullscreen, that's not the case here. Once It is finished entering fullscreen it's totally fine.

(I can't use Wayland mostly because video playback is extremely stuttery on anything chromium based, but it also likes to break after logging out)

10900k/RTX 2080S (Clevo X170SM-G Laptop).

[Nayr438]

11 hours ago, Mnky313 said:

(I can't use Wayland mostly because video playback is extremely stuttery on anything chromium based, but it also likes to break after logging out)

X11 is pretty much in maintenance mode apart from xwayland, which was primarily maintained by RedHat
https://www.phoronix.com/news/X.Org-Maintenance-Mode-Quickly

https://www.phoronix.com/news/RHEL10-Removing-X.Org

The X11 Session file is being removed in March and X11 is being completely dropped at the end of the year.
https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/99#note_1867026

 

Chromium doesn't support hardware video acceleration on Wayland and doesn't reliably work on X11
https://wiki.archlinux.org/title/chromium#Hardware_video_acceleration

 

Firefox does support Hardware Video Acceleration

https://wiki.archlinux.org/title/firefox#Hardware_video_acceleration

It is more reliable when used in Wayland Mode in a Wayland Session, requires adding the following to "/etc/environment"

MOZ_ENABLE_WAYLAND=1

 

Make sure that you have setup the following https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend

[Mnky313]

1 hour ago, Nayr438 said:

X11 is pretty much in maintenance mode apart from xwayland, which was primarily maintained by RedHat
https://www.phoronix.com/news/X.Org-Maintenance-Mode-Quickly

https://www.phoronix.com/news/RHEL10-Removing-X.Org

The X11 Session file is being removed in March and X11 is being completely dropped at the end of the year.
https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/99#note_1867026

 

Chromium doesn't support hardware video acceleration on Wayland and doesn't reliably work on X11
https://wiki.archlinux.org/title/chromium#Hardware_video_acceleration

 

Firefox does support Hardware Video Acceleration

https://wiki.archlinux.org/title/firefox#Hardware_video_acceleration

It is more reliable when used in Wayland Mode in a Wayland Session, requires adding the following to "/etc/environment"

MOZ_ENABLE_WAYLAND=1

 

Make sure that you have setup the following https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend

Thanks for the info.

I switched back to wayland to see if I can track down the issues I've been having there.

I don't use chromium for my browser, however I do use freetube which is built on chromium. Running it with

--enable-features=VaapiVideoDecodeLinuxGL --use-gl=egl --disable-features=UseChromeOSDirectVideoDecoder

seems to resolve it (though hardware acceleration still reports and not working:

 

OBS also just doesn't launch, no idea what's wrong with that but I'll look at it later.

gSnap (like fancyzones but for GNOME) also seems to be kind of broken with wayland, it works for a bit (a few minutes maybe?), then randomly stops and I have to manually assign monitors their snap profiles again....

But I guess that does resolve the fullscreen issues : /
 

Edited January 9 by Mnky313
stop replacing shit with emojis

[Nayr438]

Just now, Mnky313 said:

Thanks for the info.

I switched back to wayland to see if I can track down the issues I've been having there.

I don't use chromium for my browser, however I do use freetube which is built on chromium. Running it with

--enable-features=VaapiVideoDecodeLinuxGL --use-gl=egl --disable-features=UseChromeOSDirectVideoDecoder

seems to resolve it (though hardware acceleration still reports and not working:

I did completely forget something when mentioning hardware video acceleration. It depends on vaapi support, something nvidia doesn't actually support.
There is a community maintained translation layer called nvidia-vaapi-driver, however there is a note on the Arch Wiki

Quote

Series 525 of the NVIDIA driver introduced a regression, breaking VA-API. nvidia-vaapi-driver#126 You may downgrade the drivers to version 520 or use the experimental direct-backend in the meantime.

https://wiki.archlinux.org/title/Hardware_video_acceleration#Translation_layers

[Mnky313]

Adding to this now that I've 'resolved' it.

Even under Wayland on Arch I still had the same issue (it wasn't as predictable, sometimes it would be fine, sometimes it would hang for several seconds but it still happened)

I ended up going back to Debian for my systems (because the main reason I went to Arch was to hopefully improve the experience on my Z13 (asus-linux recommends using Arch/Fedora for the best experience however it made virtually no difference for me except the trackpad was worse (it kept grabbing the wrong driver) and the keyboard backlight went from not controllable but always on (Debian, Kernel 6.1) to sometimes controllable but randomly turns off (Arch, Kernel 6.6).

The issue doesn't happen on Debian, I'm still using X11 for now (trying the usual workarounds (modifying 61-gdm.rules and adding nvidia-drm.modeset=1 parameter) to get Wayland working with Nvidia drivers doesn't seem to work, it might work once but a lot of the time attempting to login results in flashing black screens for a few seconds followed by getting kicked back to the login screen with no Wayland option.....

Weirdly these work totally fine on the Z13 and my Zenbook Duo...