ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
nerdopolis has quit [Ping timeout: 482 seconds]
<RAOF>
So you can test core stuff in wlroots with tinywl, which is still helpful.
<DemiMarie>
RAOF: any chance Mir could support xdg-decoration?
guru_ has joined #wayland
Guru_DE has quit [Ping timeout: 480 seconds]
<DemiMarie>
@orowith2os:fedora.im: if you want apps to be able to use GTK for decorations then GTK had better be an easily embedded in an application, which it isn’t.
columbarius has joined #wayland
<DemiMarie>
and do not care about accessibility
co1umbarius has quit [Ping timeout: 480 seconds]
<DemiMarie>
What I will say is that clients had better implement xdg-decoration
<DemiMarie>
Some compositors will draw SSDs whether clients like it or not, and if the client doesn’t notice that the result will be double decorations.
nerdopolis has joined #wayland
qaqland is now known as Guest3989
qaqland has joined #wayland
Guest3989 has quit [Ping timeout: 480 seconds]
<ids1024>
DemiMarie: Generally Wayland is designed on the assumption that servers never draw window decorations (except maybe minimal borders) for clients that don't implement those protocols. But I guess the point here is that Qubes doesn't trust clients to provide their own decorations?
<DemiMarie>
ids1024: exactly!
<DemiMarie>
@orowith2os:fedora.im: why is this so surprising?
<DemiMarie>
@orowith2os:fedora.im: you don’t, it’s the colored borders that matter
<danieldg>
yes, qubes is designed with the idea that untrusted clients are likely to play clickjacking games if you let them do their own decorations
<danieldg>
plus the colors to indicate which VM the window came from
<DemiMarie>
@_oftc_danieldg:matrix.org: yup!
<DemiMarie>
@orowith2os:fedora.im: that’s an interesting idea, thanks
fmuellner has quit [Ping timeout: 480 seconds]
<DemiMarie>
@orowith2os:fedora.im: trust me, this is _not_ the worst hack Qubes has when it comes to displaying stuff
<DemiMarie>
The worst is injecting GTK4 CSS to work around performance problems with software rendering
<DemiMarie>
more would not help, sorry
<DemiMarie>
Native contexts are the goal, but they will have to be off by default until GPU driver security improves
<DemiMarie>
Also, Nautilus might be slow on a 1vCPU VM with software rendering, but it should at least work, not get stuck displaying the spinner forever.
Guest3943 has quit [Remote host closed the connection]
<RAOF>
(I understand Lomiri, one of our downstreams, even implements it)
* DemiMarie
is glad this is possible, unlike in Mutter
PuercoPop has joined #wayland
<DemiMarie>
@orowith2os:fedora.im: I know you were joking about 1 GPU per VM, but if you knew how bad GPU passthrough security was, you would not be recommending this solution. Cloud providers get away with it by using custom hardware.
<DemiMarie>
Specifically custom board designs, possibly with custom chips.
sevz has joined #wayland
glennk has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
PuercoPop has quit [Ping timeout: 480 seconds]
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
supernyan has joined #wayland
andyrtr has joined #wayland
mxz has quit [Quit: cya]
mxz has joined #wayland
guru_ is now known as Guru_DE
Fischmiep has quit [Ping timeout: 480 seconds]
Fischmiep has joined #wayland
tzimmermann has joined #wayland
Company has joined #wayland
<Sachiel>
orowith2os[m]: fwiw, you are not identified on irc so we old farts can't read you
glennk has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
i509vcb has quit [Read error: Network is unreachable]
cheako has quit [Write error: connection closed]
i509vcb has joined #wayland
cheako has joined #wayland
ManMower has quit [Remote host closed the connection]
ManMower has joined #wayland
rv1sr has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
AnuthaDev has joined #wayland
navi has joined #wayland
neniagh_ has quit [Remote host closed the connection]
neniagh has joined #wayland
iomari891 has joined #wayland
neniagh has quit [Ping timeout: 480 seconds]
neniagh has joined #wayland
leon-anavi has joined #wayland
AnuthaDev has quit [Ping timeout: 480 seconds]
i509vcb has quit [Quit: Connection closed for inactivity]
AJ_Z0 has quit [Read error: Connection reset by peer]
<mlausch>
don't know if that's the correct place to ask about mouse input events in wayland (actually gnome/Xwayland). `libinput debug-events;' shows me hid++ scroll events, `wev` doesn't.
<mlausch>
or i don't know what i'm doing and misread things. I can provide literal output of libinput debug-events and wev if needed.
<vyivel>
i don't wev supports axis_value120
<vyivel>
don't think*
<vyivel>
so no hires scrolling
<mlausch>
@vyivel thanks. wev does the right thing. i looked into the source and the wayland proto spec. what i see in wev output is a sequence of 8 axis_source events, followed by 1 axis event. the 1 axis event corresponfs to one ratchet (detent) of the wheel.
<mlausch>
which is weird, because wayland server gets all the hid++ events, but only emits axis events after N such hid++ scroll events.
<mlausch>
or i don't understand the semantics of the scroll events in the wayland proto (which is a totally valid thing).
manuel__ has joined #wayland
manuel_ has quit [Ping timeout: 480 seconds]
manuel_ has joined #wayland
manuel__ has quit [Ping timeout: 480 seconds]
<mlausch>
vyivel: you're right. i skimmed the mutter source code and the 120 scroll values are not used. so no smooth scrolling in wayland?
<vyivel>
it might be helpful to rename .gitlab/issue_templates/Bug.md to Default.md so the template is visible immediately to reduce the number of issues like the one above