01:19 NepNep[m]: Testing
13:34 wlb: wayland Issue #435 opened by Simon Ser (emersion) Unclear what an <enum> since attribute means when used externally https://gitlab.freedesktop.org/wayland/wayland/-/issues/435
15:19 wlb: wayland Issue #387 closed \o/ (Clarify whether wl_buffer destruction after wl_surface.attach is allowed https://gitlab.freedesktop.org/wayland/wayland/-/issues/387)
15:21 wlb: wayland/main: Kirill Primak * protocol: clarify pending wl_buffer destruction https://gitlab.freedesktop.org/wayland/wayland/commit/8f499bf4045f protocol/wayland.xml
15:21 wlb: wayland Merge request !363 merged \o/ (protocol: clarify pending wl_buffer destruction https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/363)
22:19 lsd|2: lsd@Crawler-E25:~/q2pro/builddir$ ./q2pro ------- FS_Init ------- Current search path: ./baseq2 ----------------------- ------- R_Init ------- Using video driver: wayland ]warning: queue 0x564c1d75e840 destroyed while proxies still attached: wl_registry@3 still attached Using GLSL rendering backend. ******************** FATAL: Couldn't load pics/colormap.pcx: No such file or directory **********
22:19 lsd|2: what the fuck is this shit?
22:20 lsd|2: fuck sake, can linux ever will be normal?
22:20 lsd|2: i shutted down that fucking game
22:20 riteo: calm down geez
22:21 riteo: this happened during shutdown right? It's just some bad cleanup
22:21 lsd|2: yes
22:21 riteo: it's simply the game not cleaning up stuff properly
22:22 riteo: it means exactly 0 to the average player
22:22 lsd|2: riteo: it might be since developer of this fork is strongly active recently
22:22 lsd|2: thank you <3
22:23 riteo: lsd|2: yeah, if the backend is being worked on it's extremely probable that it's just a temporary artifact
22:24 riteo: let the developer know about that issue though, as they shouldn't be destroying queues like that, although it being a wl_registry it's probably done ever-slighlty too early, can't say a lot without further context
22:25 riteo: 'nyways, yw :D
22:34 lsd|2: whats that guy i spoke before i reset
22:35 lsd|2: riteo: after reset is still hanged
22:35 lsd|2: ]warning: queue 0x55bbf3524840 destroyed while proxies still attached:
22:37 riteo: uh you left
22:37 riteo: I was going to answer lol
22:38 riteo: I mean, if it's stuck just Ctrl+C
22:38 riteo: It's _probably_ a client issue, especially if you can't replicate this anywhere else, but I don't know further info
22:39 danieldg: windows habit, always reboot :)
22:39 riteo: a windows user I know always reboots too, is it that broken? Lol
22:39 danieldg: not so much these days, but those habits formed decades ago
22:40 danieldg: and it does clean things up better on both windows and linux
22:40 danieldg: (mostly relevant with broken drivers, for both)
22:41 riteo: well yeah it's a good habit, especially after some system changes, but otherwise it's not a good thing I think
22:41 riteo: in the "should not happen in the first place" way
22:42 danieldg: regarding the actual error, an easy fix would be for the game to just call exit(0) instead of trying to clean everything up in the right order
22:43 riteo: I wonder, what's the difference between exiting and cleaning up properly, outside of correctness?
22:44 riteo: like, is there some practical advantage or is it just prettier to do?
22:44 danieldg: you'll have a harder time finding leaks with valgrind if you don't clean up properly
22:44 danieldg: that's about it
22:44 riteo: fair