07:15 wlb: wayland Issue #351 opened by sbadux (sbadux) Monitor can't go in stanby when in "Auto" mode https://gitlab.freedesktop.org/wayland/wayland/-/issues/351
08:42 wlb: wayland Issue #351 closed \o/ (Monitor can't go in stanby when in "Auto" mode https://gitlab.freedesktop.org/wayland/wayland/-/issues/351)
09:23 kennylevinsen: (for those at fosdem) so who asks daniels about "x11 on fbdev"
09:25 zubzub: Im located at the exit so I might still make it after I ask the question
09:26 kennylevinsen: smart thinking
10:59 daniels: :D
14:13 martin-kokos: Hi. I am running Plasma on wayland 1.21.0 and when I go with mouse cursor from one display to another, there is sometimes a cursor left behind on the previsous display for up to a second. Does that sound like a wayland problem or a Plasma problem?
15:24 SardemFF7: Wayland is only a protocol (and its lib), all the drawing stuff is either in the client or the compositor
15:58 martin-kokos: alright. I thight maybe cursor is a special case because I think I've read it has its own surface
16:27 MrCooper: it's still up to the compositor where that surface is (not) displayed
16:28 martin-kokos: thanks. Have a nice day