ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
feaneron has quit [Ping timeout: 480 seconds]
<karl5fox>
Thanks Kenny, let me check the version, its the one that is mirrored by MS so I'm sure its not the "latest"
Brainium has quit [Ping timeout: 480 seconds]
ybogdano has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
ybogdano has joined #wayland
ybogdano has quit [Ping timeout: 480 seconds]
ybogdano has joined #wayland
glennk has quit [Ping timeout: 480 seconds]
feaneron has joined #wayland
andyrtr_ has joined #wayland
andyrtr has quit [Ping timeout: 480 seconds]
andyrtr_ is now known as andyrtr
garnacho has quit [Ping timeout: 480 seconds]
gallo has joined #wayland
<Consolatis>
<*> DemiMarie hopes that not too much will break without the protocol implemented (Qubes OS)
<Consolatis>
re shortcut protocol: No, it doesn't. Some user controlled (rather than application controlled) alternative mode to supress handling stuff like A-Tab / A-F4 when a specific window has keyboard focus would likely be beneficial for VM / remote clients though
<Consolatis>
I personally very much prefer to not allow random applications like browsers to disable compositor shortcuts just because they got focus, it should be the choice of the user to do so
nerdopolis has quit [Ping timeout: 480 seconds]
mxz_ has joined #wayland
adamtajti_ has joined #wayland
mxz has quit [Ping timeout: 480 seconds]
mxz__ has quit [Ping timeout: 480 seconds]
adamtajti has quit [Ping timeout: 480 seconds]
mxz_ is now known as mxz
Calandracas_ has joined #wayland
Calandracas has quit [Ping timeout: 480 seconds]
feaneron has quit [Quit: feaneron]
pH5 has quit [Remote host closed the connection]
adamtajti has joined #wayland
adamtajti_ has quit [Ping timeout: 480 seconds]
<dviola>
damn it, 6.12-rc6 is also broken (sway inside QEMU has the mouse cursor inverted down)
<dviola>
time to bisect
karenw has joined #wayland
iomari891 has joined #wayland
mxz_ has joined #wayland
sally has quit [Quit: sally]
sima has joined #wayland
tzimmermann has joined #wayland
glennk has joined #wayland
sally has joined #wayland
adamtajti has quit [Ping timeout: 480 seconds]
<dviola>
doesn't look like a kernel regression
kts has joined #wayland
kts has quit [Remote host closed the connection]
<dviola>
bluetail: I might have given you the wrong info in saying that kernel 6.11.6-arch1-1 broke things
<dviola>
looks like it's a problem with weston and hyprland too, will need to check mesa next
coldfeet has joined #wayland
leon-anavi has joined #wayland
JakeSays has joined #wayland
JakeSays1 has quit [Ping timeout: 480 seconds]
garnacho has joined #wayland
mtretter has joined #wayland
coldfeet has quit [Remote host closed the connection]
<karenw>
So updated ubuntu, and now it has "Default Queue" in the output of WAYLAND_DEBUG=client for objects not on a custom queue. Is there a way to name custom queues in a similar way?
<kchibisov>
yes, they should use the new with name api.
<kchibisov>
e.g. mesa uses it already.
<karenw>
Right. Looks like the mesa amd vulkan driver doesn't, so I may go and fix that then.
<kchibisov>
they do, if they are compiled against the new version.
<karenw>
Hmm, okay. I'll make sure I've grabbed the latest then.
<kchibisov>
the point is not the latest, but that mesa was built against the new libwayland with support for it.
<kchibisov>
so you could have latest mesa, but it could have built against previous libwayland.
<karenw>
Ooooh, that *would* make sense. I think the ppa I'm using is latest mesa but built against libwayland from ubuntu 24.04 not 24.10.
<karenw>
Thanks kchibisov
pH5 has joined #wayland
kts has joined #wayland
<MrCooper>
dviola: mostly not even trivial fixes, just churn for questionable if any benefit
<MrCooper>
Consolatis: FWIW, gnome-shell asks for user consent before inhibiting shortcuts
<MrCooper>
(and that dialogue explains how to break the inhibition)
kts has quit [Quit: Leaving]
___nick___ has joined #wayland
mvlad has joined #wayland
JakeSays1 has joined #wayland
JakeSays has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
<karenw>
Huh. wl_surface::frame doesn't work as I expected. It only seems to trigger on events like losing input focus. I expected to get 30/60/N callbacks a second.
<kennylevinsen>
karenw: The wl_surface_frame callback fires once when committed at the next time the compositor believes it's a good time to draw
<kennylevinsen>
for a visible surface in a common setup you'll find that it's generally tied to monitor refresh
<karenw>
kennylevinsen: Rubber Duck Debugging strikes again. I needed to call frame() *before* commit.
<kennylevinsen>
yup, it's double-buffered. :)
<karenw>
Like most things (although my mental model was not including server-triggered events as being part of that until now)
coldfeet has joined #wayland
abhimanyu has joined #wayland
cyrinux has quit []
cyrinux has joined #wayland
fmuellner has joined #wayland
coldfeet has quit [Remote host closed the connection]
yshui has quit [Ping timeout: 480 seconds]
Moprius has joined #wayland
Calandracas_ has quit [Ping timeout: 480 seconds]
linkmauve has joined #wayland
Moprius_ has joined #wayland
Moprius_ has quit []
Moprius has quit [Ping timeout: 480 seconds]
rdiffender has joined #wayland
kts has joined #wayland
nerdopolis has joined #wayland
kts has quit [Quit: Leaving]
dviola has quit [Ping timeout: 480 seconds]
nysach has joined #wayland
nysach has quit [Remote host closed the connection]
rdiffender has quit [Remote host closed the connection]
diego has joined #wayland
karenw has quit [Ping timeout: 480 seconds]
Brainium has joined #wayland
karenw has joined #wayland
yshui has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
yshui_ has joined #wayland
yshui has quit [Ping timeout: 480 seconds]
Brainium has quit [Ping timeout: 480 seconds]
kts has joined #wayland
leon-anavi has quit [Remote host closed the connection]
agd5f_ has joined #wayland
agd5f has quit [Ping timeout: 480 seconds]
garnacho has quit [Read error: Connection reset by peer]
agd5f has joined #wayland
agd5f_ has quit [Ping timeout: 480 seconds]
JEEB has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
yshui has joined #wayland
iomari891 has joined #wayland
yshui_ has quit [Ping timeout: 480 seconds]
paulk has quit [Read error: Connection reset by peer]
yshui has quit [Read error: Connection reset by peer]
tzimmermann has quit [Quit: Leaving]
kts has quit [Quit: Leaving]
yshui has joined #wayland
<karenw>
Hmm, I encountered a similar issue trying to compile code using cursor-shape, had to manually generate headers for tablet-unstable-v2 in order to get it to compile originally (it's now in stable/). Despite not using or supporting touch/tablets in any way.
<karenw>
I feel like some kind of machine-readable dependency tracking between protocols would be useful.
feaneron has joined #wayland
<diego>
MrCooper: I see
diego has left #wayland [WeeChat 4.4.3]
dviola has joined #wayland
<dviola>
this doesn't look right, in my QEMU VM glxinfo reports virgl is in use, but also radeonsi, shouldn't radeonsi be limited to the host only?
<dviola>
if I'm not mistaken, virtio_gpu_dri.so should be loaded on the guest but it isn't
<dviola>
I'm pretty sure something broke, just can't tell exactly what yet
<dviola>
lsof shows a bunch of libdrm_*.so open but no virtio_gpu_dri.so
<MrCooper>
it's clearly a feature, not a bug :) virgl gets the host driver name from the host and includes it in its renderer string
<dviola>
MrCooper: ah, then I just never seen it before
<MrCooper>
*the host renderer string
<dviola>
or maybe I did and don't remember
<MrCooper>
maybe it was added recently
<dviola>
ah ok, thanks
<MrCooper>
well it was added in Mesa over 3 years ago, maybe your hypervisor didn't report the information before though
<dviola>
makes sense
<dviola>
this is really odd now :D -- I started recording the screen with wf-recorder and as soon as the recording starts, the mouse pointer becomes usable again, although I still see the inverted mouse below, so there are two cursors on the screen
<dviola>
if I stop recording, the only cursor left on screen is the odd one
<soreau>
dviola: wf-recorder makes sw cursor happen
<soreau>
(FWIW)
<soreau>
and wf-recorder is per-output
<dviola>
I see
<dviola>
ahh, WLR_NO_HARDWARE_CURSORS=1 made it go away again
<dviola>
had this issue in the past with sway on QEMU, but it went away for a while... now it's back
<soreau>
dviola: sounds like a possible wlroots issue in that case
<soreau>
but you mentioned it happens on weston too?
<dviola>
iirc, around kernel 6.8 it went away
<dviola>
just tried weston now, and it's fine...
<dviola>
yeah maybe I did something wrong in my previous test
<dviola>
river also has the issue
<soreau>
probably wlroots related
<soreau>
maybe try 0.17 vs 0.18
<soreau>
wayfire master is on 0.17, track-wlroots branch on 0.18 too
<dviola>
yep, will do, thanks
<soreau>
đź‘Ť
Brainium has joined #wayland
<soreau>
the unfortunate thing is, wlroots is kinda difficult to bisect with constant unstable API churn :P
<dviola>
I'm also running sway on the host and the cursor on the host also looks weird, maybe that got me confused when I tested weston on the VM
linkmauve has left #wayland [Error from remote client]
<dviola>
soreau: ah heh
<soreau>
dviola: if you find 0.17 works, then try to gather info and complain loudly in #wlroots ;)
linkmauve has joined #wayland
<soreau>
and maybe file an issue
<dviola>
ha :P they probably get enough complaining already, but I will let them know ;)
<dviola>
I bet they get less now, with hyprland not using it anymore... sorry
<dviola>
I know vaxry was complaining very loudly about wlroots for a while
pbsds is now known as Guest8861
pbsds has joined #wayland
yshui_ has quit [Read error: Connection reset by peer]
Guest8861 has quit [Ping timeout: 480 seconds]
yshui has joined #wayland
mripard has quit [Quit: WeeChat 4.4.2]
Brainium has quit [Ping timeout: 480 seconds]
<karl5fox>
hey guys, so I've gotten weston to output the three monitors over the RDP shell, they show as XWAYLAND0 - XWAYLAND02 at the shell, but in the gui terminal in GNOME I see WAYLAND0 connected and rdp-0, rdp-4, rdp-3 disconnected. Can I put those RDP-0 etc in weston.ini as outputs?
___nick___ has quit []
___nick___ has joined #wayland
Brainium has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
Brainium has quit [Read error: Connection reset by peer]
karenw has quit [Ping timeout: 480 seconds]
<dviola>
tbh I think wayland is too good to be true sometimes, it mostly just works for me nowadays... I went back to X a couple of days ago and couldn't believe I never saw the tearing before
<DemiMarie>
How does one see tearing?
<dviola>
one thing I often hear people complain about wayland is how they need portals and pipewire for screen sharing, are portals always going to be mandatory for screen sharin or will that be replaced in the future?
<DemiMarie>
Portals are the portable solution, but some compositors offer non-portable extension APIs
<kennylevinsen>
wayland protocols are also a perfectly portable solution, it’s just a different solution
<kennylevinsen>
dviola: portals are currently the design flatpak and it’s proponents favor so it’s unlikely to go away anytime soon
<kennylevinsen>
pipewire isn’t going away either - and people were used to pulseaudio, so a more capable modern replacement isn’t an issue
Brainium has joined #wayland
<dviola>
DemiMarie: I see a noticeable difference when scrolling with firefox on wayland and X, when I was using X I was like "why do I even need a compositor?" because it was good enough, but I see the difference now
<dviola>
soreau: hah
<dviola>
kennylevinsen: ah yes, pipewire is really good
<DemiMarie>
dviola: is it a case of one being able to see the different images or is it more something that feels wrong subconsciously?
<psykose>
you see a torn line on the screen
<psykose>
where e.g. above it is the new frame and below it is the old frame
<dviola>
DemiMarie: good question, it's mostly about text not flowing as smoothly, what psykose said (I think)
<kennylevinsen>
Tearing is very obvious, but you also often ran separate compositors to fix it
<psykose>
separate compositors that crashed 4 times a day
<psykose>
i wonder if that ever got fixed, sure didn't in all the time i used X
<dviola>
for me crashes related to X were almost always due to some issues with xf86-video-intel, went away after I switched to -modesetting
<kennylevinsen>
The path to get pixels to your screen is a lot simpler now, that’s for sure
<jadahl>
kennylevinsen: the NES is waiting for the toddler to gain a few more years until it becomes theirs :P
<kennylevinsen>
Better start educating them early :)
<kennylevinsen>
Ugh those modifiers with size-dependent parameters encoded into them again…
<soreau>
jadahl: I had this plan for an old P4 machine but now probably would have to get a tcouhscreen for it, since there's a certain addiction to touchscreens that has developed
nerdopolis has quit [Ping timeout: 480 seconds]
<soreau>
if you can't touch it - it's broke
<soreau>
(the DS4->rpi->rc car project is a bit more successful, but they still want me to drive it)
sima has quit [Ping timeout: 480 seconds]
<jadahl>
soreau: did the plan work out?
<soreau>
jadahl: yet to be seen, we have to decide where it will live first
iomari891 has quit [Ping timeout: 480 seconds]
<soreau>
jadahl: it might help in your situation to acquire the 'stomp/jump pad' or whatever it's called, so they can just dance around to make input happen (only supported by certains games, like track meet IIRC)
iomari891 has joined #wayland
karl5fox has quit [Remote host closed the connection]