ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
ciara has quit [Read error: Connection reset by peer]
ciara has joined #wayland
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
<kennylevinsen>
i509vcb: the configure event specifies a specific size the compositor requests, while the configure_bounds event is a suggested upper bound (e.g., "you won't fit in the screen if you're larger than this")
<kennylevinsen>
perfectly normal for it to be larger than (or equal to) the configured size
DragoonAethis has quit [Quit: hej-hej!]
DragoonAethis has joined #wayland
<i509vcb>
kennylevinsen: yes, however there is nothing really preventing implementations from sending configure bounds larger than the configure
<i509vcb>
I was wondering if this was a documentation oversight or not
fmuellner has quit [Ping timeout: 480 seconds]
<orowith2os[m]>
i509vcb: there's probably a use case somewhere where the "maximum size" is smaller than the "suggested size"
<orowith2os[m]>
not a very useful use case, but a use case nonetheless
Brainium has quit [Quit: Konversation terminated!]
ciara has quit [Read error: Connection reset by peer]
ciara has joined #wayland
sjao2 has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
haasn` has quit []
<sjao2>
I have an issue with attempting to offload rendering to my nvidia card with flatpaks, it just doesn't work and omits egl problems https://paste.debian.net/plain/1288798
<orowith2os[m]>
sjao2: run `flatpak update` and ensure the nvidia drivers are working inside of the Flatpak environment.
<sjao2>
this works on X11
<sjao2>
there seems to be a minor update for the 32 bit nvidia libraries for the 525 branch but nothing the blender would use
<sjao2>
ok after unsetting __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json it starts and a process binds to the gpu but nothing appears and the process hangs https://paste.debian.net/plain/1288799
<sjao2>
I had this set on the host to prevent applications binding to the nvidia card when I didn't want them to
kts_ has joined #wayland
ciara has quit [Read error: No route to host]
ciara has joined #wayland
kts_ has quit []
Leopold__ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
Guest8706 has quit [Remote host closed the connection]
Leopold__ has joined #wayland
cool110 has joined #wayland
Leopold_ has quit [Ping timeout: 480 seconds]
sima has joined #wayland
cool110 is now known as Guest8762
andyrtr has quit [Ping timeout: 480 seconds]
ciara has quit [Read error: Connection reset by peer]
ciara has joined #wayland
andyrtr has joined #wayland
andyrtr_ has joined #wayland
junaid has joined #wayland
andyrtr has quit [Ping timeout: 480 seconds]
andyrtr_ is now known as andyrtr
sozuba has joined #wayland
sozuba is now known as Guest8769
lsd|2 has joined #wayland
ciara has quit [Read error: Connection reset by peer]
ciara has joined #wayland
<kennylevinsen>
i509vcb: "there is nothing really preventing implementations from sending configure bounds larger than the configure" - why would there be? Bounds >= configure is the expected scenario. Did you perhaps mean the other way around?
nerdopolis has quit [Remote host closed the connection]
nerdopolis has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
kts has joined #wayland
junaid has quit [Remote host closed the connection]
CruxOfTheB has joined #wayland
ciara has quit [Read error: Connection reset by peer]
ciara has joined #wayland
fmuellner has joined #wayland
<i509vcb>
kennylevinsen: bounds > configure size was what I was asking about
<i509vcb>
where you have a restricting state such as maximized set on the toplevel
<i509vcb>
Is the case something like, 50% tiled to the right (so maximized with a 960x1080 size) and then the bounds are 1920x1080 for the entire screen?
<kennylevinsen>
i509vcb: the expected use-case is something like the user resizing the window to 1920x1200, but the output is 3840x2160. The configure would then be 1920x1200, while bounds could be 3840x2160 (i.e., larger)
<kennylevinsen>
For tiled, the bounds could be the size of the tile - bounds do not have a hard definition other than being "something the client should probably stay below"
<kennylevinsen>
needed because the client is free to resize freely, including in most states ignoring configured sizes - but might still want to know how big is too big
<kennylevinsen>
in states where configure dimensions are a hard demand, bounds become irrelevant - they're just an upper bound hint for when the client *is* in control
ciara has quit [Read error: Connection reset by peer]
ciara has joined #wayland
<i509vcb>
ok so it's a hint for when the client is free to do what it wants
<sjao2>
I figured it out, I have to revoke the wayland permission in flatpak to force it to use xwayland rather than wayland, and it turns out natively offloading was using xwayland aswell