ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
<pq>
shashank_, hi, how's the EDID parser work going? I saw Naveen asked me about the old Weston MR just when I left for holidays, but I'd prefer all effort going to your parser if that looks good to you.
<pq>
in the edid-decode based one
linguist has joined #wayland
GentooPhysicist3 has quit []
GentooPhysicist3 has joined #wayland
jgrulich_ has quit []
jgrulich_ has joined #wayland
gryffus has joined #wayland
jgrulich_ has quit []
jgrulich has joined #wayland
<emersion>
what is this wayland/security subgroup, daniels?
<pq>
it's for reviewing confidential merge requests which would disclose security vulnerabilities
<pq>
since Gitlab does not have the concept of confidential MRs
<pq>
emersion, if you don't have access, we should get that for you.
hendursa1 has quit []
<emersion>
ok
<emersion>
i do have access
<pq>
cool
hendursaga has joined #wayland
<ManMower>
an MR to a public repo becomes public, even if its source is a private repo. so you need to do all the clandestine stuff in a private repo before disclosing through the MR to public repo. the workflow is not great.
hexfive has quit [Ping timeout: 480 seconds]
amosk has quit [Ping timeout: 480 seconds]
<kennylevinsen>
Not sure how it would work otherwise - "accept these changes you cannot see because my repo is private"? :)
<pq>
there should be a tick-box for confidential MRs - there isn't
<daniels>
heh, well at least have it there but not viewable to people who don't have access, and be able to open it up when it lands so people can see the whole development and review trail
<daniels>
there's no conceptual reason you can't have it, just that you then need to implement filtering for refs/commits/etc by security group within a repo, rather than filtering the entire repo yes or no
<romangg>
On a keyboard focus change is the wl_data_device::seletion signal supposed to be sent out before the enter event even when there is no current selection, i.e. with a NULL argument?
<romangg>
Seems unnecessary and the protocol text is not 100% clear on that.
<romangg>
Looking at wlroots code at least wlroots seems to always send a selection, even if it is null. It does this after receiving keyboard focus though. Hmm.
<emersion>
yeah, no selection = send event with NULL
<emersion>
that way client don't wait forever on a event which won't come
sychill has joined #wayland
sychill has quit []
sychill has joined #wayland
sychill has quit []
sychill has joined #wayland
leon-p has quit []
zebrag has quit [Remote host closed the connection]
<romangg>
emersion: If they receive an enter event without a selection event before that they know there won't come one anymore, not?
<romangg>
From the protocol description the selection event is supposed to be sent _before_ the enter event.
<emersion>
ah
<emersion>
dunno then
<romangg>
That's what I meant btw with wlroots sending the event after the enter event.
<romangg>
Currently wlroots implicitly behaves like there is no selection and it does not send a selection event before the enter event. Then afterwards it sends one, so from the client's pov it looks like there is at first no selection and then later on the selection changed to something else.
<romangg>
Or if NULL is sent then the wlroots compositor for some unnown reason to the clients wants it to know again that there is no selection.
linguist has left #wayland [#wayland]
autistic has joined #wayland
<autistic>
Hello! Would wayland work on a KVM virtual machine?
<LaserEyess>
yes?
<LaserEyess>
can you be more specific? otherwise the answer is obviously yes
<danieldg>
it might be slow if you don't have a virtual gpu, but that's true of any GUI
<autistic>
The reason I asked is hardware support, maybe
<danieldg>
and you need to display out to a real screen too, but there are several ways to make that work
melissawen has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
<autistic>
danieldg, well, that´s what I was afraid
<danieldg>
wayland itself doesn't require any particular hardware, and should work fine with qemu's emulated devices if you're using that (and then qemu can appear as a normal window on the host)
<danieldg>
or you can treat the VM as a remote machine over the network and use waypipe
<zzag>
romangg: it's not just wlroots sending selection event after enter. as far as I know, weston, mutter, and kwin also send selection after enter event. kwin used to send selection event before enter event though but some clients (or rather a toolkit) don't like that :|
melissawen has joined #wayland
<romangg>
zzag: Ah interesting. Thanks. It's only us here so it's ok to name the toolkit. Which one is it?