sharkautarch

I encountered a similar but slightly different sigsegv w/ latest gamescope when running qemu gtk w/ zink on and gamescope WSI disabled, currently working on debugging it w/ valgrind: ```...

@emersion When you said > This is already fixed in the latest iteration of the wlroots MR I believe, but gamescope seems to use an earlier version Was this issue...

@matte-schwartz I think I know exactly whats causing the crash after the wlroots upgrade in upstream... because there was an extra nullpointer check (that I found to be necessary at...

@kisak-valve This issue *should* be fixed as of PR #1444 being merged

``` Thread 1 (Thread 0x7f503adf26c0 (LWP 144916)): #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x00007f503cfb2b03 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x00007f503cf60576 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3...

I vaguely remember someone w/ a custom Wayland compositor complaining about gamescope crashing when gamescope was given a {0,0} geometry or something Not sure if this is the same issue...

AHHH yes so the message `[1239232.643] {Display Queue} wl_display#1.error(wp_viewport#35, 0, "invalid source geometry")` makes sense now wayland protocol spec for [`wp_viewport::set_source`](https://wayland.app/protocols/viewporter#wp_viewport:request:set_source) says: > If all of x, y, width and...

@ThomasPrzybylinski @matte-schwartz @Quince-Pie I just pushed out a branch with a fix for the protocol error: https://github.com/sharkautarch/gamescope/tree/steam_notification_crash_fix_attempt Let me know if that fixes all of the steam notification issues, and...

Good to hear that the branch fixes the crash I've just updated it now to fix that compiler error I heard from matt that he also says it fixes the...

I made another branch in an attempt to fix the remaining issue w/ the steam notifications window being invisible: https://github.com/sharkautarch/gamescope/tree/steam_notification_crash_fix_attempt_v2 Let me know if that branch fixes both the issue...