ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
bwbuhse_ has joined #wayland
valpackett has quit [Ping timeout: 480 seconds]
bwbuhse has quit [Ping timeout: 480 seconds]
bwbuhse_ is now known as bwbuhse
iomari891 has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
karenw has quit [Ping timeout: 480 seconds]
dviola has quit [Read error: Connection reset by peer]
<riteo>
Hi people. I just wanted to update you all on my old experiment, the XEmbed like pseudo-compositor protocol proxy thing (you can check the logs if you're curious) and as of now I still haven't crashed into a wall. I'm honestly quite surprised myself because it really doesn't feel like it should work lol
<riteo>
regarding the issue with old globals without a destructor I simply added some logic to instance them once at most and recycle them, with some tracking for the occasional init event (e.g. wl_shm.format)
<riteo>
that worked surprisingly well and now I don't get random leaks
diego has joined #wayland
<riteo>
I have a pretty rough prototype for Godot over at https://github.com/godotengine/godot/pull/107435 and if it keeps going great I hope one day to turn this approach into a generic C library
<riteo>
right now the code sucks a lot but hey, it's working :D
<riteo>
to end this wall of text, note that the PR above does not describe the approach in detail (since its internals are still very fluid) but hopefully gives a good idea of the pros and cons
diego2 has joined #wayland
diego has quit [Ping timeout: 480 seconds]
garnacho has quit [Ping timeout: 480 seconds]
diego has joined #wayland
diego2 has quit [Ping timeout: 480 seconds]
Moprius has joined #wayland
valpackett has joined #wayland
luna has joined #wayland
Moprius has quit []
bindu_ has joined #wayland
bindu has quit [Ping timeout: 480 seconds]
luna has left #wayland [#wayland]
nerdopolis has quit [Ping timeout: 480 seconds]
kts has joined #wayland
bindu has joined #wayland
bindu_ has quit [Ping timeout: 480 seconds]
orowith2os[m] has joined #wayland
<orowith2os[m]>
Is there some way for, if I were to jam a Wayland client into a server's address space, have that client modify other wl_surfaces?
<orowith2os[m]>
ideally without needing compositor-specific integrations
<orowith2os[m]>
well, I guess I'd probably need to get to compositor-specific stuff anyways...
<orowith2os[m]>
I'm thinking on how a client, like GTK, could be linked into Mutter, and learn to handle xdg_toplevels requesting decorations from xdg_decoration without needing to learn how to be an entire compositor
feaneron has quit [Ping timeout: 480 seconds]
<Eighth_Doctor>
Oro (any/all): that seems fairly similar to the kwin kdecoration plugin interface model
<pq>
karolherbst, on Xorg/fluxbox, I used to have the copy&paste problem with e.g. Geany IIRC, that copying new stuff did not actually copy after a while and then paste pasted previous stuff. I didn't run any clipboard managers, and no Wayland nor Xwayland. To fix it, I had to restart a few apps.
<karolherbst>
pq: sounds like a different problem. For me it's just that individual copies don't seem to work, but it can be fixed by copying something else and try again
<pq>
riteo, congrats! :-)
<pq>
karolherbst, hmm, indeed. I'm not quite sure if the paste pasting old stuff was specific to an app, or did it happen on all apps. I did have the feeling that some app just managed to "lock" the clipboard contents. Hard to recall details, it was perhaps around the previous Debian stable, and I haven't used Geany for a long time either.
<karolherbst>
pq: yeah so if I try to copy the same content it won't work, just copying something different before retrying fixes it. So it might just be some sync issue between wayland and X11 apps or something like that?
<pq>
This is just to say that clipboard issues are not exclusive to Wayland being part of the picture. :-)
<pq>
karolherbst, do you re-select the same thing to copy and that won't work?
<karolherbst>
correct
<pq>
but selecting something else from the same window works?
<karolherbst>
not sure tbh
<pq>
*selecting and copying
<karolherbst>
I mean, I don't know if it must be from a different window or not to fix it
<pq>
do you use another window or another app to "fix" it?
<karolherbst>
possibly, will have to wait for it to happen again and then I'll try to see if it's related to the specific window or not
<karolherbst>
but I think the pasting only fails if it's into a different application
<pq>
ok
<pq>
curious details there
<daniels>
I hate to dig out anyone in specific, but I remember Firefox being the common denominator for a lot of clipboard issues in the past - I'm sure it's a lot better these days, but if that still occurs there then maybe that's something to look at
narodnik has quit [Ping timeout: 480 seconds]
narodnik has joined #wayland
<bluetail>
daniels do u know why? btw, wayland is a protocol... and for implementations, e.g sway I had to use wayland-proxy to load balance software that was a bit top heavy, cause not properly multi-threading. Cause, it appears, clients are disconnected if they take too long to respond, in wayland implementations.
<kennylevinsen>
the need for that should be gone
<kennylevinsen>
as of jan, sway sets a max buffer size of 1 MiB which is more than plenty
<kennylevinsen>
(the value that caused slow/blocked clients to disconnect was 4KiB for reference)
<bluetail>
I see. That's interesting. Thanks. I will test that sometime again
<kennylevinsen>
they'll still be disconnected if they reach the 1MiB limit, but that gives them roughtly 256x the amount of time to pull themselves together and read from their socket :)
<bluetail>
is there a known issue with SILK.NET=> GLFW is unable to create a window on Wayland? I found their SDL backend just works fine, but the GLFW one never seems to commit and thus the window never shows up.
narodnik has quit [Ping timeout: 480 seconds]
bindu_ has joined #wayland
bindu has quit [Ping timeout: 480 seconds]
nowrep has quit [Quit: WeeChat 4.6.1]
nowrep has joined #wayland
<Ermine>
i had a funny case: launched an application through terminal, suspended it with ctrl-z and forgot to move it to background with bg. When i've realized it, it was too late
<kennylevinsen>
to be fair, that will break applications in all sorts of ways depending on what it's trying to do
kts has joined #wayland
narodnik has joined #wayland
bindu_ has quit [Ping timeout: 480 seconds]
bindu has joined #wayland
coldfeet has quit [Quit: Lost terminal]
kts has quit [Ping timeout: 480 seconds]
V has quit [Ping timeout: 480 seconds]
valpackett has joined #wayland
coldfeet has joined #wayland
fmuellner has joined #wayland
kts has joined #wayland
lsd|2 has joined #wayland
kts has quit [Ping timeout: 480 seconds]
narodnik has quit [Ping timeout: 480 seconds]
azerov has quit [Quit: Gateway shutdown]
Moprius has joined #wayland
Moprius has quit [Remote host closed the connection]
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
nerdopolis has joined #wayland
Flat has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Konversation terminated!]
bindu_ has joined #wayland
bindu has quit [Ping timeout: 480 seconds]
coldfeet has joined #wayland
Brainium has joined #wayland
Flat has joined #wayland
diego has left #wayland [WeeChat 4.6.3]
feaneron has joined #wayland
dviola has joined #wayland
leon-anavi has quit [Quit: Leaving]
rasterman- has joined #wayland
rasterman- has quit []
rasterman has quit [Remote host closed the connection]
rasterman has joined #wayland
Cherrio has joined #wayland
<Cherrio>
How well does wayland work on i915 integrated gpus? Im wondering becouse i have a laptop with nvidia and igpu and when moving a window its as if i have a low framerate like 60hz or similiar, but my hz is set to 144hz. Im not sure if its bad performance or too weak chipset
<riteo>
thanks pq :D
narodnik has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
valpackett has quit [Ping timeout: 480 seconds]
<anarsoul>
Cherrio: is it really an i915 GPU? It's like ~20yo. Or you mean the driver name?
<anarsoul>
wayland compositors work reasonably well on modern(-ish) Intel iGPUs
valpackett has joined #wayland
<Cherrio>
ah then its not that since its a pretty highend laptop
<akyoto>
my current desktop uses i915 + wayland, works just fine (1920x1080@165Hz)
<Cherrio>
i recently discovered that without the external monitor it runs as it should. Its when i use external monitor wayland feels choppy. Programs that run on the dedicated gpu runs fun even on external monitor