screen freezes when using picom and opening fullscreen apps

treblaHY · 2023-12-26 09:28:56

OS: Arch Linux x86_64 
Host: ASUS TUF Gaming F15 FX507VU4_FX507VU4 1.0 
Kernel: 6.6.8-arch1-1 
Resolution: 1920x1080 @ 144 Hz
WM: xmonad 
CPU: 13th Gen Intel i9-13900H (20) @ 5.200GHz 
GPU: Intel Raptor Lake-P [Iris Xe Graphics] 
GPU: NVIDIA GeForce RTX 4050 Max-Q / Mobile

As the subject says, my whole screen freezes when using I'm picom and opening fullscreen apps. Even after killall picom, the whole screen freezes too when opening fullscreen apps. Moreover, running picom gives this error:

[ 12/26/2023 17:16:46.591 _gl_fill ERROR ] GL error at line 714: GL_INVALID_FRAMEBUFFER_OPERATION

This situation happens after I do the following in my config:

unredir-if-possible = true;

I used picom-ftlabs-git from AUR now, but switch to picom(or picom-git) still shows the same problem.

I have two GPUs, one is Iris Xe iGPU, and the other one is RTX 4050 Max-Q. I have mesa and nvidia installed.
pacman -Qs mesa gives:

local/glu 9.0.3-1
    Mesa OpenGL utility library
local/lib32-mesa 1:23.3.1-1
    An open-source implementation of the OpenGL specification (32-bit)
local/mesa 1:23.3.1-1
    An open-source implementation of the OpenGL specification
local/mesa-utils 9.0.0-3
    Essential Mesa utilities

And pacman -Qs nvidia gives:

local/egl-wayland 2:1.1.13-1
    EGLStream-based Wayland external platform
local/ffnvcodec-headers 12.1.14.0-1
    FFmpeg version of headers required to interface with Nvidias codec APIs
local/lib32-nvidia-utils 545.29.06-1
    NVIDIA drivers utilities (32-bit)
local/libvdpau 1.5-2
    Nvidia VDPAU library
local/libxnvctrl 545.29.06-1
    NVIDIA NV-CONTROL X extension
local/nvidia 545.29.06-7
    NVIDIA drivers for linux
local/nvidia-prime 1.0-4
    NVIDIA Prime Render Offload configuration and utilities
local/nvidia-prime-rtd3pm 1.0-2
    Configure your discrete NVIDIA GPU to power down when not in use.
local/nvidia-settings 545.29.06-1
    Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 545.29.06-1
    NVIDIA drivers utilities
local/nvtop 3.0.2-1
    GPUs process monitoring for AMD, Intel and NVIDIA

My journalctl -b -1:
https://pastebin.com/KZ58FX9m

lspci | grep VGA:

0000:00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04)
0000:01:00.0 VGA compatible controller: NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile] (rev a1)

By the way, this is my first post here, so please remind me if I have done something wrong or need to provide more information, I'll reply as soon as I can.

seth · 2023-12-26 09:44:10

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

This situation happens after I do the following in my config:

Even after killall picom, the whole screen freezes too when opening fullscreen apps.

If you allow picom to redirect fullscreen windows, this doesn't happen?

If you use your WM (xmonad?) to fullscreen glxgears, does this also happen?

Does this happen
* w/ openbox instead of xmonad
* w/o sddm (but using startx or xinit)?

treblaHY · 2023-12-26 10:14:50

My Xorg.log:
https://pastebin.com/XEHq29bc

If you allow picom to redirect fullscreen windows, this doesn't happen?

If I allow picom to redirect fullscreen windows, this doesn't happen. However, if I allow picom to redirect fullscreen windows, but turn off picom using killall picom before opening the fullscreen app, there are chances (I would say about 75%) that it freezes.
Also, when it freezes, my keyboard don't work, can't close window, can't change workscape, can't Ctrl+Alt+number to go to TTYs, but cursor is still being rendered and I can move it around, although I can't do anything with it in xmonad.

If you use your WM (xmonad?) to fullscreen glxgears, does this also happen?

Not sure if this is how to do it, but I do this in my xmonad.hs

main = do
	xmonad $ ewmhFullscreen.ewmh $ fullscreenSupportBorder $ docks defaults

And run glxgears -fullscreen.
It didn't freeze for now, but I'm not sure if it will after sometime, since sometimes this is the case for other applications.
The GL error is still there.(and keeps displaying in my terminal for like 10+ lines while glxgears is running)

When I run glxgears -fullscreen without tweaking my xmonad.hs, it is still a window and can be resized, but unredir-if-possible is being runned, and all the animations, shadows, opacity are gone. However, it is not freezing the whole screen, and is running consistently 144FPS.

* w/ openbox instead of xmonad

It happens too with openbox.

* w/o sddm (but using startx or xinit)?

It happens too with startx.

Last edited by treblaHY (2023-12-26 10:49:01)

treblaHY · 2023-12-26 15:04:50

Eh... a rather surprising news, my screen freezes again without out me even running picom(like I didn't killall picom after running it once), and it freezes when I open a steam game(not using proton, the game is naturally supported on linux).
So I guess there are now two problems, first picom gives gl error, then fullscreen apps causes freeze(it become two seperate questions), should I change this post subject?

Also, due to not carefully reading wiki, I've installed xf86-video-nouveau before, but I removed it like 1 month after(it's few months ago though), and went on using prime-run when I have to, maybe this cause problem also? Although I don't think removing xf86-video-nouveau would have any bad effect to my system, also nvidia blacklists nouveau in /usr/lib/modprobe.d too, so I don't think this is the cause, but I'm not sure.

glxinfo -B:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) Graphics (RPL-P) (0xa7a0)
    Version: 23.3.1
    Accelerated: yes
    Video memory: 15618MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (RPL-P)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.3.1-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.3.1-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.3.1-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Last edited by treblaHY (2023-12-26 16:11:49)

seth · 2023-12-26 19:30:11

Unless you're prime-run'ning those fullscreen applications, nvidia isn't relevant - you're running on the intel chip and the only output is wired there.
You're also running on the modesetting driver, so it's not an xf86-video-intel problem (don't install that package!)

Dec 26 17:06:06 treblaHY kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

Enable https://wiki.archlinux.org/title/NVIDIA … de_setting and in doubt add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters but I don't think that's the cause of your problems.

Next question: do you get those freezes when prime-run'ning the games?

treblaHY · 2023-12-27 01:00:58

Enable https://wiki.archlinux.org/title/NVIDIA … de_setting and in doubt add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters but I don't think that's the cause of your problems.

Adding those parameters doesn't help, the freezing still happens.
However, it only freezes the game, since I trying playing a YouTube video before opening the steam games, and the sound from the game stops, but YouTube video doesn't.

Next question: do you get those freezes when prime-run'ning the games?

Yes, I do get thoes freezes no matter with or without prime-run, I put parameters below when launching the game from Steam, which is the same as prime-run.

__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%

Edit:
Just open steam in terminal and found out that Steam might also have some problem opening games, there are quite some errors, but I have no idea what they mean or how to fix it, the game launches fine though.

steam.sh[16479]: Running Steam on arch rolling 64-bit
steam.sh[16479]: STEAM_RUNTIME is enabled automatically
setup.sh[16551]: Steam runtime environment up-to-date!
steam.sh[16479]: Steam client's requirements are satisfied
[2023-12-27 11:49:38] Startup - updater built Dec  8 2023 00:32:59
[2023-12-27 11:49:38] Startup - Steam Client launched with: '/home/Albertchen/.local/share/Steam/ubuntu12_32/steam'
12/27 11:49:38 Init: Installing breakpad exception handler for appid(steam)/version(1702079146)/tid(16597)
[2023-12-27 11:49:38] Loading cached metrics from disk (/home/Albertchen/.local/share/Steam/package/steam_client_metrics.bin)
[2023-12-27 11:49:38] Using the following download hosts for Public, Realm steamglobal
[2023-12-27 11:49:38] 1. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 1000, source = 'update_hosts_cached.vdf'
[2023-12-27 11:49:38] 2. https://cdn.cloudflare.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'update_hosts_cached.vdf'
[2023-12-27 11:49:38] 3. https://cdn.steamstatic.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2023-12-27 11:49:38] Verifying installation...
[2023-12-27 11:49:38] Verification complete

Steam logging initialized: directory: /home/Albertchen/.local/share/Steam/logs

XRRGetOutputInfo Workaround: initialized with override: 0 real: 0xe860fdc0
XRRGetCrtcInfo Workaround: initialized with override: 0 real: 0xe860e500
/usr/share/themes/Adwaita-dark/gtk-2.0/main.rc:733: error: unexpected identifier 'direction', expected character '}'
/usr/share/themes/Adwaita-dark/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant
steamwebhelper.sh[16616]: Runtime for steamwebhelper: defaulting to /home/Albertchen/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[16616]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3()
CAppInfoCacheReadFromDiskThread took 24 milliseconds to initialize
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 16713
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
BRefreshApplicationsInLibrary 1: 1ms
BuildCompleteAppOverviewChange: 242 apps
RegisterForAppOverview 1: 11ms
RegisterForAppOverview 2: 11ms
/bin/sh\0-c\0/home/Albertchen/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=412220 -- /home/Albertchen/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/home/Albertchen/.local/share/Steam/steamapps/common/DDraceNetwork/ddnet/DDNet'\0
chdir "/home/Albertchen/.local/share/Steam/steamapps/common/DDraceNetwork/ddnet"
ERROR: ld.so: object '/home/Albertchen/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/Albertchen/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/Albertchen/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/Albertchen/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
2023-12-27 11:49:58 I engine: running on unix-linux-steam-amd64
2023-12-27 11:49:58 I engine: arch is little endian
2023-12-27 11:49:58 I engine: operating system version: Linux 6.6.8-arch1-1 (x86_64, #1 SMP PREEMPT_DYNAMIC Thu, 21 Dec 2023 19:01:01 +0000); "Arch Linux"
2023-12-27 11:49:58 I storage: added path '$USERDIR' ('/home/Albertchen/.local/share/ddnet')
2023-12-27 11:49:58 I storage: added path '$DATADIR' ('data')
2023-12-27 11:49:58 I storage: added path '$CURRENTDIR' ('/home/Albertchen/.local/share/Steam/steamapps/common/DDraceNetwork/ddnet')
2023-12-27 11:49:58 I discord: error initializing discord instance, error=4
[S_API] SteamAPI_Init(): Loaded '/home/Albertchen/.local/share/Steam/linux64/steamclient.so' OK.
Setting breakpad minidump AppID = 412220
SteamInternal_SetMinidumpSteamID:  Caching Steam ID:  76561198410432882 [API loaded no]
2023-12-27 11:49:58 I http: libcurl version 7.22.0 (compiled = 8.0.1)
2023-12-27 11:49:58 I console: executing 'settings_ddnet.cfg'
2023-12-27 11:49:58 I client: starting...
2023-12-27 11:49:58 I sdl: SDL version 2.28.5 (compiled = 2.0.6)
2023-12-27 11:49:58 I gfx: Created Vulkan 1.1 context.
Fossilize INFO: Overriding serialization path: "/home/Albertchen/.local/share/Steam/steamapps/shadercache/412220/fozpipelinesv6/steamapprun_pipeline_cache".
2023-12-27 11:49:58 I gfx: GPU vendor: NVIDIA
2023-12-27 11:49:58 I gfx: GPU renderer: NVIDIA GeForce RTX 4050 Laptop GPU
2023-12-27 11:49:58 I gfx: GPU version: Vulkan 1.3.260 (driver: 545.29.6.0)
2023-12-27 11:49:58 I textrender: Freetype version 2.13.2 (compiled = 2.10.4)
2023-12-27 11:49:58 I joystick: 0 joystick(s) found
GameOverlay: started '/home/Albertchen/.local/share/Steam/ubuntu12_32/gameoverlayui' (pid 16928) for game process 16873
12/27 11:49:58 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20231208003324)/tid(16928)
12/27 11:49:58 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(16928)
2023-12-27 11:49:58 I http: https://master3.ddnet.org/ddnet/15/servers.json failed. libcurl error (6): Couldn't resolve host 'master3.ddnet.org'
2023-12-27 11:49:59 I client: version 17.4.2 on linux-steam amd64
2023-12-27 11:49:59 I client: git revision hash: b33c0d8fb9a68d05c7851ceedf7d0d45144b407a
2023-12-27 11:49:59 I http: fetching https://info.ddnet.org/info?name=treblahy
2023-12-27 11:49:59 I http: fetching https://master2.ddnet.org/ddnet/15/servers.json
2023-12-27 11:49:59 I http: fetching https://info.ddnet.org/info?name=treblahy
2023-12-27 11:49:59 I http: task done https://master2.ddnet.org/ddnet/15/servers.json
2023-12-27 11:50:00 I serverbrowse_http: found master, url='https://master1.ddnet.org/ddnet/15/servers.json' time=818ms
2023-12-27 11:50:00 I http: task done https://info.ddnet.org/info?name=treblahy
2023-12-27 11:50:00 I serverbrowse_http: found master, url='https://master2.ddnet.org/ddnet/15/servers.json' time=190ms
2023-12-27 11:50:00 I http: https://master4.ddnet.org/ddnet/15/servers.json failed. libcurl error (22): The requested URL returned error: 404
2023-12-27 11:50:00 I serverbrowse_http: determined best master, url='https://master2.ddnet.org/ddnet/15/servers.json' time=190ms
2023-12-27 11:50:01 I http: task done https://info.ddnet.org/info?name=treblahy
2023-12-27 11:50:18 I client: disconnecting. reason='unknown'
Game 412220 created interface STEAMAPPS_INTERFACE_VERSION008 / 
Game 412220 created interface SteamController008 / 
Game 412220 created interface SteamFriends017 / 
Game 412220 created interface SteamInput006 / 
Game 412220 created interface SteamUser021 / User
Game 412220 created interface SteamUtils010 / 
Game 412220 method call count for IClientAppManager::GetLaunchCommandLine : 1
Game 412220 method call count for IClientUtils::RecordSteamInterfaceCreation : 7
Game 412220 method call count for IClientUtils::GetAppID : 9
Game 412220 method call count for IClientFriends::GetPersonaName : 1
Game 412220 method call count for IClientUser::GetSteamID : 1
Uploaded AppInterfaceStats to Steam

(process:16928): GLib-GObject-CRITICAL **: 11:50:19.806: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
reaping pid: 16928 -- gameoverlayui

Somehow it says this

2023-12-27 11:49:58 I engine: running on unix-linux-steam-amd64

Last edited by treblaHY (2023-12-27 03:54:09)

seth · 2023-12-27 09:07:53

However, it only freezes the game, since I trying playing a YouTube video before opening the steam games, and the sound from the game stops, but YouTube video doesn't.

You seem to have pipewire and pulseaudio active, replace pulseaudio w/ pipewire-pulse and make sure to use wireplumber, not pipewire-media-session.

Do the games also freeze if you run them in windowed mode?

treblaHY · 2023-12-27 10:07:35

Okay, I've replaced pulseaudio with pipewire-pulse and installed wireplumber.

Do the games also freeze if you run them in windowed mode?

They work really well, no freeze at all.

Also, I just realize hitting Alt+SysRq+r(sending keyboard back to 'raw' mode) let me goes to tty2, and by going to tty2 and back to tty1(which is where xmonad is running), I'm able to switch workspace again.
And the game just doesn't render anything except the cursor. More specifically, my fullscreen game(should not have rounded borders) shows only border and cursor and is moveable, I'm also able to see the Steam window behind it.
Besides that, chrome is also broken, the window it displays become whichever workspace I switched from, and going back to normal after stopping the game from Steam.

I also runs steam through terminal, below is the output from launching the game to force stopping the game:

reaping pid: 4121 -- gameoverlayui
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
/bin/sh\0-c\0__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia /home/Albertchen/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=11020 -- /home/Albertchen/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/home/Albertchen/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/Albertchen/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun  '/home/Albertchen/.local/share/Steam/steamapps/common/TrackMania Nations Forever/TmForever.exe'\0
chdir "/home/Albertchen/.local/share/Steam/steamapps/common/TrackMania Nations Forever"
ERROR: ld.so: object '/home/Albertchen/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/Albertchen/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/Albertchen/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/Albertchen/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/Albertchen/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
Setting breakpad minidump AppID = 11020
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561198410432882 [API loaded no]
Fossilize INFO: Overriding serialization path: "/home/Albertchen/.local/share/Steam/steamapps/shadercache/11020/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize WARN: Pipeline library handle 0xffffffffe2b89f18 is not registered.
It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).
Fossilize WARN: Pipeline library handle 0xffffffffe2ba18f8 is not registered.
It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).
GameOverlay: started '/home/Albertchen/.local/share/Steam/ubuntu12_32/gameoverlayui' (pid 6333) for game process 6278
12/27 17:56:45 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20231208003324)/tid(6333)
12/27 17:56:45 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(6333)
pid 6215 != 6214, skipping destruction (fork without exec?)
Uploaded AppInterfaceStats to Steam

(process:6333): GLib-GObject-CRITICAL **: 17:57:44.423: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
reaping pid: 6333 -- gameoverlayui

I'll keep trying and see if I can find more information about this problem.

Last edited by treblaHY (2023-12-27 10:08:20)

seth · 2023-12-27 14:32:47

reaping pid: 6333 -- gameoverlayui

Does it help to disable the steam overlay?

treblaHY · 2023-12-27 15:15:54

If you're talking about the one in settings > In Game > THE STEAM OVERLAY > Enable the Steam Overlay while In-game, then it's never turned on, neither had I use Overlay shortcut keys(shift + tab) to temporarily turn it on too.

seth · 2023-12-27 21:45:40

Maybe the crashing gameoverlayui is a red herring.

seth wrote:
Do the games also freeze if you run them in windowed mode?
They work really well, no freeze at all.

Is this only w/ picom or also without?

I put parameters below when launching the game from Steam, which is the same as prime-run.

Try to also https://wiki.archlinux.org/title/Vulkan … initialize

treblaHY · 2023-12-28 04:11:04

Is this only w/ picom or also without?

Never experienced freezes under windowed mode, no matter with or without picom.

Try to also https://wiki.archlinux.org/title/Vulkan … initialize

Have set the environment variable VK_DRIVER_FILES to /usr/share/vulkan/icd.d/nvidia_icd.json, and it's not freezing anymore.
However, it also doesn't freeze after i unset(?) the environment variable, so I'm not sure if that works, I'll try a bit more to figure out the answer.
The freezes doesn't happen everytime, which makes it very harder to know what works and what doesn't. It usually happens when I'm actively using it and the uptime is over 1 hour.

Also, I experienced a graphical glitch in openGL with fullscreen mode only. The comparation video is below:
https://youtu.be/mlrJGN2V8zU

video IRL:
https://youtu.be/33tyAs-7d3k?si=APWwhUs8kPyjpWJT

Edit: The graphical glitch only happens when I open the game after picom, if I open the game then run picom, the glitches are nowhere to be seen, even after I restarted the whole game by closing it entirely and re-open it(this is weird af behavior and I don't understand why it is like this)
A temporary solution is by limiting the ingame framerate to 300(it used to be unlimited)

Last edited by treblaHY (2023-12-28 04:44:24)

secretknowledge · 2023-12-28 04:12:02

I am having this exact same issue with Minecraft. I am using i3 and it appears to fix itself via resizing the window.

treblaHY · 2023-12-28 04:34:06

I am having this exact same issue with Minecraft. I am using i3 and it appears to fix itself via resizing the window

May I ask what do you mean by resizing the window? Is it under windowed mode or fullscreen?

Also I've tried using Openbox, but the result are the same in xmonad.

Last edited by treblaHY (2023-12-28 04:34:14)

secretknowledge · 2023-12-29 04:22:56

My switching from fullscreen to windows is what I mean by "resizing." Sorry for the confusion.

seth · 2023-12-29 08:01:32

@treblaHY, any updates on the post-vulkan selection situation?

The graphical glitch only happens when I open the game after picom, if I open the game then run picom, the glitches are nowhere to be seen

Check "xwininfo" on the glitching window and notably the depth. Steam might get you an ARGB/32bit window if there's a compositor and a regular RGB/24bit window w/o (and this cannot change during the lifetime of the window, so starting/killing a compositor afterwards would not impact this one way or the other)

treblaHY · 2023-12-30 11:23:36

The xwininfo always give the similar results like this, regardless if picom is on:

xwininfo: Please select the window about which you
          would like information by clicking the
          mouse in that window.

xwininfo: Window id: 0x3000008 "DDNet Client"

  Absolute upper-left X:  0
  Absolute upper-left Y:  0
  Relative upper-left X:  0
  Relative upper-left Y:  0
  Width: 1920
  Height: 1080
  Depth: 24
  Visual: 0x744
  Visual Class: DirectColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x3000004 (installed)
  Bit Gravity State: ForgetGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners:  +0+0  -0+0  -0-0  +0-0
  -geometry 1920x1080+0+0

which I believe is a regular RGB/24 bit window

Also, the whole glitch thing is really weird and seems like it happens randomly.
I do the first test w/o picom and somehow get glitches.
Then I reboot and launch the game w/o picom again, but I get no glitches.
Finally, I reboot and launch the game with picom, and this time getting no glitches.

BTW, I have done memtest and cpu test (done in ASUS bios), and the results are good, so this basically removes the posibilities of hardware problem.

Also, I have linux and linux-zen, but when I boot into linux-zen, system does not recognize nvidia GPU at all, "xrandr --listproviders" lists only 1 provider, is this the correct behaviour or I do need to set up dGPU again?
Edit: It says "Failed to start NVIDIA Persistence Daemon." when booting linux-zen

Last edited by treblaHY (2023-12-30 14:58:11)

seth · 2023-12-30 21:44:54

For linux-zen you'll need nvidia-dkms.
Can you capture the glitches in a screenshot?

treblaHY · 2023-12-31 05:26:28

Get it, I'll get nvidia-dkms and try again!

https://youtu.be/mlrJGN2V8zU
A comparison of vulkan/openGL and fullscreen/window.
However, the glitch when using openGL and fullscreen makes the screen recording super laggy, so I also took another video using my phone directly recording the laptop monitor.

https://www.youtube.com/watch?v=33tyAs-7d3k
Video IRL

Also, using Vulkan seems to make to game more laggy, although the framerate(show by steam) is higher than 144(my monitor refresh rate) so it should be all smooth. Not sure if this is noticeable in the video.

Last edited by treblaHY (2024-01-01 03:53:57)

seth · 2023-12-31 10:41:56

The glitch doesn't show in the direct recording resp. probably presents itself as the massive lag.
The artifacts in the RL video look like it's either tearing or an older buffer leaks into the image.

Since it seems somehow™ related to picom, please post your picom config.
Either picoms vsync prevents it (tearing) or the blur texture flickers into the output (blur settings)

treblaHY · 2023-12-31 11:46:10

My picom.conf (using picom-ftlabs-git)

#################################
#             Shadows           #
#################################

shadow = true;
shadow-radius = 7;
shadow-offset-x = -7;
shadow-offset-y = -7;
shadow-exclude = [
  "name = 'Notification'",
  "class_g = 'Conky'",
  "class_g ?= 'Notify-osd'",
  "class_g = 'Cairo-clock'",
  "class_g = 'Rofi'",
  "window_type = 'menu'",
  "window_type = 'dropdown_menu'",
  "window_type = 'popup_menu'",
  "window_type = 'tooltip'",
  "_GTK_FRAME_EXTENTS@:c"
];


#################################
#           Fading              #
#################################


fading = true;
fade-in-step = 0.05;
fade-out-step = 0.05;

#################################
#   Transparency / Opacity      #
#################################
inactive-opacity = 1;
frame-opacity = 1;
inactive-opacity-override = false;
focus-exclude = [ "class_g = 'Cairo-clock'" ];
opacity-rule = [
	"93:class_g = 'URxvt' && focused",
	"72:class_g = 'URxvt' && !focused"
]

#################################
#           Corners             #
#################################
corner-radius = 10;
rounded-corners-exclude = [
  "window_type = 'dock'",
  "window_type = 'desktop'",
  "class_g = 'Rofi'"
];

#################################
#          Animations           #
#################################

animations = true
animation-for-transient-window = "zoom"
animation-for-open-window = "zoom"
animation-stiffness = 350
animation-window-mass = 0.7
animation-for-workspace-switch-in = "zoom"
animation-exclude = [
  "class_g = 'fcitx'",
  "window_type = 'dock'",
  "window_type = 'desktop'",
  "window_type = 'menu'",
  "window_type = 'dropdown_menu'",
  "window_type = 'popup_menu'",
  "window_type = 'tooltip'",
  "_GTK_FRAME_EXTENTS@:c"
];

#################################
#       General Settings        #
#################################
backend = "glx";
dithered-present = false;
vsync = true;
mark-wmwin-focused = true;
mark-ovredir-focused = true;
detect-rounded-corners = false;
use-ewmh-active-win = true
unredir-if-possible = true;
detect-transient = false
glx-no-stencil = true
glx-no-rebind-pixmap = true
use-damage = true;
xrender-sync-fence = true
log-level = "warn"
log-file = "/home/Albertchen/picom_debug.txt"

wintypes:
{
  tooltip = { fade = true; shadow = true; opacity = 0.75; focus = true; full-shadow = false; };
  dock = { shadow = false; clip-shadow-above = true; }
  dnd = { shadow = false; }
  popup_menu = { opacity = 0.8; }
  dropdown_menu = { opacity = 0.8; }
};

Last edited by treblaHY (2023-12-31 11:50:12)

seth · 2023-12-31 15:18:48

The one you initally posted had some blur settings - is anything blurring atm?

backend = "glx";
vsync = true;
unredir-if-possible = true;

When you're starting the compositor after the FS window, it might not unredirect it - so if that contrast is reproducible, disabling "unredir-if-possible" will reveal whether the redirection is the critical difference.
Disabling vsync will show whether the compositors vsync is ultimately what prevents the glitches (because they'll appear with it if vsync is crucial, but disabled)

treblaHY · 2023-12-31 18:26:24

I've tested it a few times and got results like this.
First time: picom on with unredir-if-possible, glitch happens
Second time: picom on without unredir-if-possible, glitch doesn't happen
Third time: picom on with unredir-if-possible(same as first time), glitch happens <--- ?????

So I think unredir-if-possible isn't the critical difference of this behavior, same does v-sync.

I don't have anything blurring at the moment, the first config had blurring settings, but it's all comment out, and I remove it just to make it easier to read.

seth · 2023-12-31 20:24:22

So I think unredir-if-possible isn't the critical difference of this behavior

The paragraph before suggested that the glitches were reproducible w/ unredir-if-possible but no w/o
I'm not gonna say that the sample size of 3 is significant enough to draw a conclusion, but if anything, the fact that the window gets unredirected is very much relevant to the behavior?

treblaHY · 2024-01-01 03:55:30

So after doing more testing(for 20 times), glitch happens 15/20 times, 8 times with picom and 7 without picom.
The rest 5 times doesn't, 2 times with picom and 3 without picom.
And I reboot between every tests, to make sure no other stuffs are effecting it.

The paragraph before suggested that the glitches were reproducible is because I kinda never turn off the unredir-if-possible, and when I try to test if, it just so happens that the glitch didn't happened that time, so it my bad for not testing it more

Also I've edit something in the posts before, but I probably update it too late so I'll re-post it here and edit out the ones I post before.
Below is my eglinfo -B
But I have some questions to ask(gotta apologize first because I don't understand and of this TAT)
What does the "Surfaceless platform" mean in the output?
Besides that, I somehow have 4 devices listed. Device #0 being NVIDIA, Device #1 and #3 being iGPU, but differs in some part, and Device #2 just says libEGL warning: egl: failed to create dri2 screen and eglinfo: eglInitialize failed.

GBM platform:
eglinfo: eglInitialize failed

Wayland platform:
eglinfo: eglInitialize failed

X11 platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.1-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.1-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4050 Laptop GPU/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 545.29.06
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4050 Laptop GPU/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 545.29.06
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4050 Laptop GPU/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 545.29.06
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: NVIDIA
EGL version string: 1.5
EGL client APIs: OpenGL_ES OpenGL
OpenGL core profile vendor: NVIDIA Corporation
OpenGL core profile renderer: NVIDIA GeForce RTX 4050 Laptop GPU/PCIe/SSE2
OpenGL core profile version: 4.6.0 NVIDIA 545.29.06
OpenGL core profile shading language version: 4.60 NVIDIA
OpenGL compatibility profile vendor: NVIDIA Corporation
OpenGL compatibility profile renderer: NVIDIA GeForce RTX 4050 Laptop GPU/PCIe/SSE2
OpenGL compatibility profile version: 4.6.0 NVIDIA 545.29.06
OpenGL compatibility profile shading language version: 4.60 NVIDIA
OpenGL ES profile vendor: NVIDIA Corporation
OpenGL ES profile renderer: NVIDIA GeForce RTX 4050 Laptop GPU/PCIe/SSE2
OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 545.29.06
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Intel
OpenGL core profile renderer: Mesa Intel(R) Graphics (RPL-P)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.1-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: Intel
OpenGL compatibility profile renderer: Mesa Intel(R) Graphics (RPL-P)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.1-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: Intel
OpenGL ES profile renderer: Mesa Intel(R) Graphics (RPL-P)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #2:

Platform Device platform:
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
eglinfo: eglInitialize failed

Device #3:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 23.3.1-arch1.1
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 23.3.1-arch1.1
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.1-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Arch Linux

#1 2023-12-26 09:28:56

screen freezes when using picom and opening fullscreen apps

#2 2023-12-26 09:44:10

Re: screen freezes when using picom and opening fullscreen apps

#3 2023-12-26 10:14:50

Re: screen freezes when using picom and opening fullscreen apps

#4 2023-12-26 15:04:50

Re: screen freezes when using picom and opening fullscreen apps

#5 2023-12-26 19:30:11

Re: screen freezes when using picom and opening fullscreen apps

#6 2023-12-27 01:00:58

Re: screen freezes when using picom and opening fullscreen apps

#7 2023-12-27 09:07:53

Re: screen freezes when using picom and opening fullscreen apps

#8 2023-12-27 10:07:35

Re: screen freezes when using picom and opening fullscreen apps

#9 2023-12-27 14:32:47

Re: screen freezes when using picom and opening fullscreen apps

#10 2023-12-27 15:15:54

Re: screen freezes when using picom and opening fullscreen apps

#11 2023-12-27 21:45:40

Re: screen freezes when using picom and opening fullscreen apps

#12 2023-12-28 04:11:04

Re: screen freezes when using picom and opening fullscreen apps

#13 2023-12-28 04:12:02

Re: screen freezes when using picom and opening fullscreen apps

#14 2023-12-28 04:34:06

Re: screen freezes when using picom and opening fullscreen apps

#15 2023-12-29 04:22:56

Re: screen freezes when using picom and opening fullscreen apps

#16 2023-12-29 08:01:32

Re: screen freezes when using picom and opening fullscreen apps

#17 2023-12-30 11:23:36

Re: screen freezes when using picom and opening fullscreen apps

#18 2023-12-30 21:44:54

Re: screen freezes when using picom and opening fullscreen apps

#19 2023-12-31 05:26:28

Re: screen freezes when using picom and opening fullscreen apps

#20 2023-12-31 10:41:56

Re: screen freezes when using picom and opening fullscreen apps

#21 2023-12-31 11:46:10

Re: screen freezes when using picom and opening fullscreen apps

#22 2023-12-31 15:18:48

Re: screen freezes when using picom and opening fullscreen apps

#23 2023-12-31 18:26:24

Re: screen freezes when using picom and opening fullscreen apps

#24 2023-12-31 20:24:22

Re: screen freezes when using picom and opening fullscreen apps

#25 2024-01-01 03:55:30

Re: screen freezes when using picom and opening fullscreen apps

Board footer