ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
zmike has joined #wayland
glennk has quit [Ping timeout: 480 seconds]
Dami_Lu has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
mclasen has quit []
mclasen has joined #wayland
shoragan has quit [Quit: quit]
shoragan has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
mclasen has quit []
mclasen has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
garnacho has quit [Ping timeout: 480 seconds]
mclasen has quit [Remote host closed the connection]
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
fmuellner has joined #wayland
Dami_Lu has quit [Remote host closed the connection]
Dami_Lu has joined #wayland
Company has quit [Quit: Leaving]
kts has joined #wayland
kts has quit [Quit: Leaving]
glennk has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
<dubiousness>
I would like to prefix this by saying I am absolutely not trying to provoke a flame war, but I wondered if someone could shed some light on what might be required to restore the functionality mentioned in this XFCE report: https://gitlab.xfce.org/panel-plugins/xfce4-whiskermenu-plugin/-/issues/112
<emersion>
dubiousness: can you explain what is the issue for someone not familiar with XFCE?
kts has joined #wayland
<dubiousness>
emersion: previously, the panel menu was resiazable with a click and drag in X, but according to Graeme, this same functionality isn’t possible with Wayland
<dubiousness>
he undoubtedly explains it better than I can
<emersion>
so it's possible to resize it by dragging the edge?
<emersion>
the right edge?
qaqland is now known as Guest12619
Guest12619 has quit [Read error: Connection reset by peer]
qaqland has joined #wayland
<emersion>
i think it should be possible to implement right now, unfortunately would require a roundtrip to the compositor i think
<emersion>
on drag, the client can request to resize the layer surface
<kchibisov>
you certainly can, but some developed extra protocols based layer shell for that.
<dubiousness>
emersion: correct on the drag question, so at the top or the right of the window, with the menu open, I can “easily” resize it
<dubiousness>
Is it fairer to say that it’s a symptom of using GtkLayerShell for this purpose?
<kchibisov>
Do they write their own compositor?
<kchibisov>
Like you can sort of drag resize with layer shell (use transparency and span the entire output, then offset, and when drag ends you drop invisible regions), but if they write their own compositor, they could just write a custom protocol.
<mjt>
what's the way to prevent the "window attempts to grab input, allow/deny?" question? There are quite some legitimate uses of this and such question is definitely unwanted. For example, I run a mini-pc who's sole purpose is to log in to another computer using rdp or vnc and display the remote desktop.
<kennylevinsen>
which compositor?
glennk has joined #wayland
sevz has joined #wayland
rv1sr has joined #wayland
rasterman has joined #wayland
Brainium has quit [Remote host closed the connection]
<mjt>
several, - sway and gnome at the very least
<mjt>
I thought it doesn't depend on the compositor?
Sumera[m] has quit []
<kennylevinsen>
mjt: sway would not ask such a question, so it's coming from the client (or maybe a nosy proxy)
kts has quit [Ping timeout: 480 seconds]
<mjt>
now I'm confused
<mjt>
there's nothing besides sway and - in this case - wlfreerdp (or sdl-freerdp). Lemme double-check..
<mjt>
yes, I confused this terminal client and my desktop. Indeed, sway doesn't ask this question, gnome does
narodnik has joined #wayland
narodnik has quit []
narodnik has joined #wayland
narodnik has quit []
narodnik has joined #wayland
<q234rty>
it's a portal thing
<q234rty>
on gnome you can just use gnome-remote-desktop which uses mutter's dbus api directly instead of the portal
<mjt>
when you have to build freerdp3 from source in order to fix bugs in there (which are numerous).. using gnome-remote-desktop isn't an option :)
<mjt>
it's still interesting to know where the prob is. rdp isn't the only problem user here, - eg, qemu-system has the same prob. What we should do in qemu in order for gnome to stop asking the user if it's okay for qemu to grab input or not, - it is very annoying
<mjt>
what is "portal" anyway?
<kennylevinsen>
mjt: there's nothing the client can or should do to bypass compositor enforced permission checks. It's gnome you'd have to configure to not ask, if possible. Or use a compositor more suitable to your kiosk-esque use case.
<mjt>
for kiosk (rdp) I already use sway which - as I confirmed - does not ask this. But qemu is a different matter, it is not about kiosk
<mjt>
so since gnome-remote-desktop avoids this question, it's possible to implement this avoidance in qemu too, or ship gnome configuration for qemu to do that
<mjt>
it would be really nice to add such option to qemu
<kennylevinsen>
That's not how security configuration should work. Asking is not inappropriate, even if it may seem obvious that the permission is needed.
<kennylevinsen>
How it works in gnome, in particular UX and alternate gnome APIs, is a gnome question for a gnome channel though
<mjt>
yeah, I see
<mjt>
I'd not implement alternative gnome-specific APIs in qemu. But it's really annoying thing. More so once we stopped forcing sdl to x11 only
<kennylevinsen>
Regardless, I'd consider it a bug if gnome implements a prompt and had a way to bypass it. The better discussion isn't how to get around it, but how to improve the UX. Remembering the choice for example, and qemu avoiding grab unless necessary or selected by the user.
mokee has quit [Remote host closed the connection]
fmuellner has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
fmuellner_ has joined #wayland
<bwidawsk>
when/why might a compositor emit wl_output::scale = 0?
<vyivel>
sounds like a compositor bug
fmuellner has quit [Ping timeout: 480 seconds]
<bwidawsk>
The spec specifically doesn't disallow it afaict
<bwidawsk>
Similarly surface scaling
fmuellner_ has quit []
fmuellner has joined #wayland
<bwidawsk>
actually, just fractional scaling
<bwidawsk>
wl_surface has: "If scale is not positive the invalid_scale protocol error is raised."
noord has quit [Quit: bye]
glennk has joined #wayland
noord has joined #wayland
AnuthaDev has quit []
mvlad has quit [Remote host closed the connection]
PopLamina has joined #wayland
PopLamina_ has quit [Ping timeout: 480 seconds]
<kennylevinsen>
bwidawsk: 0 is technically a positive value, but that's a bug
<vyivel>
should've used "strictly positive"
<kchibisov>
kennylevinsen: that's depends who taught you math though.
<kchibisov>
And which type it's.
<kchibisov>
because positive means with-out zero, and when you want to use with zero you say "non-negative" or "non-positive".
bodiccea has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
<fluix>
wiki says 0 is either both positive and negative or neither positive nor negative. what convention you use depends on field or class
<bwidawsk>
I learned neither...
<zzag>
"is either both positive and negative" this makes no sense
<zzag>
if 0 is negative
<zzag>
then 0 < 0
<zzag>
although are we talking about integers?
<zzag>
because floating point numbers are different
<kchibisov>
That's what I said, +- zero makes sense only for real numbers.
<kchibisov>
For naturals/integers it's without a sign.
<Arnavion>
Anyone who defines zero as being negative would also define negative numbers to be <= 0, so 0 < 0 would not happen
<kchibisov>
I mean, in math when it comes to integers it's 0 without sign.
<kchibisov>
So you have, Z-, Z+, Z, N+ sets.
<kchibisov>
but maybe EU/US math is way different from what I was taught.
<Arnavion>
Indeed, Wikipedia's citation for "both positive and negative" is a book that says >A rational number is positive (>= 0) or negative (<= 0); only 0 is both
<kchibisov>
well, yeah, rational, real, the sets when you get floats.
<Arnavion>
But yeah I (Indian / British education system) also learned 0 is neither
<kchibisov>
N+ is just a common way to refer positive ints, since N is with zero...
<Arnavion>
Actually :)
<Arnavion>
The world is not consistent on whether natural numbers includes 0 or not
<kchibisov>
Well, I was taught that 0 is a part of N.
<Arnavion>
Yeah, and some systems (like mine) say natural numbers start from 1 and whole numbers are natural numbers plus 0
rasterman has quit [Quit: Gettin' stinky!]
<Arnavion>
So basically just always use "integers"
<bwidawsk>
so afaict, there are a few protocol bugs here if 0 is never allowed to be specified for output or surface scaling
nerdopolis has joined #wayland
<bwidawsk>
I can try to write an MR for this
PopLamina has quit [Ping timeout: 480 seconds]
noord has quit [Quit: bye]
noord has joined #wayland
sima has quit [Ping timeout: 480 seconds]
soreau has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
soreau has joined #wayland
privacy has joined #wayland
<kennylevinsen>
bwidawsk: not sending a scale is fine, but sending 0 is at least unexpected
<kennylevinsen>
As for clarification, I would suggest an explicit "greater than zero" to avoid further math debates. :)
<fluix>
I think "strictly positive", "non-zero positive", or what you suggested are all fine. I imagine at least one of these is already present somewhere and should be copied
<bwidawsk>
does buffer scale = 0 have a valid usage?