Attila Fidan

Stack trace looks like https://github.com/ValveSoftware/gamescope/issues/1451 / https://github.com/ValveSoftware/gamescope/issues/1456

That abort after wl_display_get_fd was also reported in https://github.com/ValveSoftware/gamescope/issues/1456. I have never run into that abort on the first time the gamescope window opens, on amdgpu/sway. I can only reproduce...

I tested it briefly yesterday and there was issues with the output resolution not being reset, and one time I saw the window show up without an app ID (I...

With only this PR, the title/app ID seems to be set correctly after subsequent window creation after several attempts to reproduce. Output width/height (g_nOutputWidth/g_nOutputHeight) doesn't seem to be set correctly...

I rebased it. I think the PRs should be separate as they fix different bugs, and I'm not sure if my patch fixing stuff inside SetVisible is the most correct...

I was able to hit `assert( !m_Planes[0].GetCurrentState() );` somewhere according to some recent coredump, so I need to change that at some point.

I don't use the gamescope reaper or mangoapp (I start gamescope separately from my application process), so it's possible that I broke something there. Though, when I run `gamescope vkcube`...

rebased on current-ish master ``` diff --git a/src/Backends/WaylandBackend.cpp b/src/Backends/WaylandBackend.cpp index ec28d28..a743450 100644 --- a/src/Backends/WaylandBackend.cpp +++ b/src/Backends/WaylandBackend.cpp @@ -1129,6 +1129,28 @@ namespace gamescope return; m_bVisible = bVisible; + + // Surface...

Removed the surface commit and title/app ID setting as that's no longer necessary. I think the output resolution globals need to be reset on connector init, or output resolution should...