05:59 dviola: MrCooper: do you mind if I open a bug report for this issue? (on xserver gitlab)
06:11 dviola: looks like someone already tried to deal with this from the sway side: https://github.com/swaywm/sway/commit/4f718e6c75d2168d417b4b41c0e3d5408e0afded
06:56 dviola: I guess I'll figure out another place to report it since you mention this not being a xwayland issue
06:57 dviola: mentioned*
06:59 dviola: wish there was a way to tell clients to stop doing stupid things
07:30 dviola: I suspect the window is not minimized, just not visible
07:30 dviola: if it were minimized it would be listed in `swaymsg -t get_tree` I think
07:31 dviola: in X the window is never minimized
07:50 dviola: nope, I take that back, I tried another app that allows me to send it to tray and `swaymsg -t get_tree` won't list it at all
07:51 dviola: this thing, gets... confusing
08:30 MrCooper: dviola: what does xwininfo say about the Steam window?
09:15 dviola: labwc seems to be doing a better job than sway, the minimize/maximize buttons in Steam actually work, and I couldn't reproduce the issue yet
09:16 dviola: MrCooper: let me check
09:17 MrCooper: to be clear, I mean when it's invisible
09:21 dviola: MrCooper: xwininfo tells me to select a window but there is nothing for me to select, it's not visible
09:22 dviola: maybe xlsclients?
09:23 MrCooper: "xwininfo -root -tree" to figure out the window's ID, then "xwininfo -id <ID> [...]"
09:23 dviola: ah, sorry I am not familiar with that command, let me check
09:26 dviola: http://0x0.st/XkUS.txt
09:28 dviola: probably that: 0x01a00038
09:29 dviola: http://0x0.st/XkUj.txt
09:30 MrCooper: I guess it's easier to figure out the ID while the window is still visible, with just xwininfo and clicking it
09:30 dviola: sure, let me check that
09:31 MrCooper: BTW, do you see Steam's tray icon?
09:31 dviola: yes
09:31 MrCooper: anyway, that looks plausible; "Map State: IsUnMapped" means a client unmapped the window
09:32 dviola: the id of the window is the same: 0x01a00038
09:32 MrCooper: looks quite unlikely to be an Xwayland issue
09:33 MrCooper: so, can't you get the window back via the tray icon?
09:34 dviola: this is what it looks like when it's minimized: http://0x0.st/XkU9.png
09:35 dviola: MrCooper: I can't, I think the tray in sway is disfunctional, I've tried other trays such as waybar, that gives me a menu and allows me to launch games, but I couldn't bring back Steam itself yet
09:35 dviola: with labwc I can minimize and restore, not sure what the tray is looking like there yet
09:36 dviola: I will try KDE and gnome later
09:36 MrCooper: if the problem doesn't occur with labwc, that indicates an issue in the other compositors
09:36 dviola: yeah
09:37 dviola: glad to know it might not be a xwayland issue, thanks for your help and apologies for being so hard set on this
09:37 MrCooper: no worries
10:08 dviola: yeah labwc is working very nicely, it's a bit shocking knowing that weston, sway and hyprland all have the same issue... not saying that in a negative way, just seems like coincidence
10:11 MrCooper: could be cargo culting
10:13 dviola: haha
10:17 MrCooper: though in theory it's also possible that Factorio / Steam do something wrong, and labwc just happens not to honour it
10:19 dviola: yeah, but wouldn't i3 (X11) also exhibit the issue if that were the case?
10:20 MrCooper: don't think it's that simple, there's a lot of variables
10:21 MrCooper: would be interesting to know what happens in GNOME/KDE Wayland sessions
10:21 dviola: I see, interesting
10:22 dviola: sure, I could try
10:30 dviola:tries gnome first
10:43 dviola: MrCooper: gnome-shell on wayland just gave me the issue as well
10:43 dviola: I tried starting factorio about 5x times on each, wayland and x11 sessions, went back to gnome-shell on wayland and boom, issue
10:44 dviola: I though the issue wouldn't appear first
10:45 dviola: not sure where the tray in gnome-shell is haha
10:45 MrCooper: there is none by default, requires an extension
10:45 dviola: oh
10:46 dviola: anyway, let's try kde
10:50 dviola: maybe the issue is also there in labwc, it just didn't appear in my tests
10:53 MrCooper: right, if it's not always reproducible
10:53 dviola: yeah, it isn't
10:55 dviola: it's starting to look more like a game/steam issue indeed, it just makes me wonder why it does not happen with x11
10:55 dviola: or does it? SDL_VIDEODRIVER=x11
11:07 dviola: just started plasma (wayland session), let's see
11:12 dviola: MrCooper: nothing yet, seems pretty stable
11:24 dviola: no issues with plasma (wayland) it seems
11:25 dviola: tried >= 20x times
11:35 dviola: I noticed there's no way to kill Xwayland in plasma, maybe some KDE component uses it
11:38 dviola: anyway, seems fine
11:41 MrCooper: the plot thickens for the affected compositors
11:43 dviola: went back to sway and got the issue on the first try
11:45 dviola: MrCooper: the odd thing is that a bunch of Steam windows get opened when that happens: http://0x0.st/Xk09.png
11:45 dviola: wait, it didn't happen now
11:46 dviola: different issue it seems
11:47 dviola: but yeah, I think there are some issues with input
11:47 dviola: I didn't hit uninstall
11:50 dviola: got the issue again :D
11:52 dviola: I wonder what to do from here, I find it difficult to believe that sway, weston, mutter and hyprland all have the same issue
11:54 dviola: MrCooper: sometimes Steam also stays like this: http://0x0.st/Xk07.png on sway until I resize the window
11:56 dviola: I didn't experience this in say, labwc
11:56 dviola: nor in KDE
11:57 dviola: MrCooper: could it be a case of those compositors touching some buggy codepath in xwayland?
11:58 dviola: or a driver issue
11:59 dviola: anyway, I'm open for more testing so just let me know if you have more ideas ;)
12:31 dviola: I wonder if there is a way to figure that out, the problem codepaths
12:46 dviola: poking at the sway code right now
12:47 dviola: ha, just made it crash
13:29 dviola: MrCooper: I can reproduce it on labwc now ;)
13:38 dviola: argh... thought it was some change that I've made but apparently not
14:12 dviola: MrCooper: I was able to reproduce it on labwc, so I guess at some point it would be reproducible on KDE too
14:13 dviola: so I guess is not really a compositor problem
14:29 dviola: maybe that's just how it is, it seems to work very inconsistently though
15:08 MrCooper: dviola: honestly can't see how this could be an Xwayland issue, driver seems pretty unlikely as well
15:10 dviola: MrCooper: right
15:28 dviola: thanks for your help so far
15:37 MrCooper: if I could reproduce, here's how I'd try to determine which client unmaps the window: 1) log in from a separate machine via SSH 2) attach gdb to Xwayland 3) set a breakpoint in ProcUnmapWindow 4) when the breakpoint fires, check that stuff->id matches the Steam window ID 5) execute "p GetClientCmdName (client)" at the gdb prompt
15:42 dviola: I see