ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
aaron465 has quit [Quit: Client limit exceeded: 20000]
sythemeta847[m] has quit []
bbaovanc[envs][m] has quit []
hch12907 has quit [Quit: Client limit exceeded: 20000]
kts has quit [Ping timeout: 480 seconds]
general_j[m] has quit []
AJ_Z0 has quit [Ping timeout: 480 seconds]
underpantsgnome[m] has quit []
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
pac85[m] has quit []
Brainium has quit [Quit: Konversation terminated!]
AJ_Z0 has joined #wayland
tent405 has joined #wayland
Dami_Lu has joined #wayland
rv1sr has joined #wayland
culuar has joined #wayland
carlos_ has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
me has joined #wayland
me is now known as Guest8252
Guest8252 has quit []
cvmn has joined #wayland
cvmn has quit []
Company has quit [Remote host closed the connection]
na[m] has quit [Quit: Client limit exceeded: 20000]
Harvey[m] has quit []
rasterman has joined #wayland
lyasm[m] has quit [Quit: Client limit exceeded: 20000]
sima has joined #wayland
deknos82[m] has quit [Quit: Client limit exceeded: 20000]
heapheap has quit [Ping timeout: 480 seconds]
tent405 has quit [Quit: tent405]
thevar1able_ has quit [Remote host closed the connection]
thevar1able_ has joined #wayland
iomari891 has joined #wayland
bwanda has joined #wayland
<bwanda> so nvidia does noto support wayland
<bwanda> not/
<kennylevinsen> bwanda: it does support Wayland, albeit your milage may vary based on choice of GPU/driver/Wayland server. Note that this channel is for Wayland protocol development - for assistance, ask in a suitable forum for your Desktop Environment or Wayland server of choice.
leon-anavi has joined #wayland
rgallaispou has joined #wayland
carlos_ has joined #wayland
mvlad has joined #wayland
Naruto[m] has quit [Quit: Client limit exceeded: 20000]
cmichael has joined #wayland
qyliss has quit [Quit: bye]
qyliss has joined #wayland
qyliss has quit []
qyliss has joined #wayland
anarsoul|2 has joined #wayland
anarsoul has quit [Read error: No route to host]
fmuellner has joined #wayland
agd5f_ has joined #wayland
kts has joined #wayland
kts has quit []
agd5f has quit [Ping timeout: 480 seconds]
ohmaddd^ has quit [Ping timeout: 480 seconds]
ohmaddd^ has joined #wayland
kts has joined #wayland
<wlb> weston Merge request !1342 opened by Marius Vlad (mvlad) Minor fixes for kiosk-shell https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1342 [kiosk-shell]
<wlb> weston Issue #787 closed \o/ (Weston crashes when plugging in a new output https://gitlab.freedesktop.org/wayland/weston/-/issues/787)
<wlb> weston/main: Derek Foreman * libweston: Rebuild view list after adding an output https://gitlab.freedesktop.org/wayland/weston/commit/3f2ce9827847 libweston/compositor.c
<wlb> weston Merge request !1341 merged \o/ (libweston: Rebuild view list after adding an output https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1341)
DrNick has quit []
nerdopolis has joined #wayland
heapify has joined #wayland
heapify has quit [Quit: heapify]
kts has quit [Ping timeout: 480 seconds]
<wlb> weston Issue #793 opened by Philipp Zabel (pH5) Surface position instability when resizing outputs https://gitlab.freedesktop.org/wayland/weston/-/issues/793
kts has joined #wayland
radu24284303951534727071489559 has joined #wayland
<Max1> How do I interpret array values that were logged using WAYLAND_DEBUG=1? e.g. for xdg_toplevel.configure, how do I map from logs like array[0], array[4], array[16] etc to the values of xdg_toplevel.states?
<wlb> weston Merge request !1343 opened by Marius Vlad (mvlad) desktop-shell: Don't reposition windows on every resize https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1343 [Desktop shell]
Company has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
jlco has joined #wayland
kts has quit [Quit: Leaving]
Moprius has joined #wayland
jmdaemon has quit [Ping timeout: 480 seconds]
jlco has quit [Ping timeout: 480 seconds]
jlco has joined #wayland
Moprius has quit [Quit: bye]
agd5f_ has quit [Read error: Connection reset by peer]
agd5f has joined #wayland
kts has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
Guest8128 has quit [Remote host closed the connection]
Leopold__ has quit []
cool110 has joined #wayland
cool110 is now known as Guest8302
Leopold_ has joined #wayland
radu24284303951534727071489559 has quit [Ping timeout: 480 seconds]
Leopold_ has quit []
Leopold_ has joined #wayland
cmichael has quit [Quit: Leaving]
leon-anavi has quit [Quit: Leaving]
iomari891 has quit [Ping timeout: 480 seconds]
agd5f has quit [Read error: No route to host]
agd5f has joined #wayland
fmuellner has joined #wayland
junaid has joined #wayland
geemili[m] has joined #wayland
geemili has joined #wayland
<geemili> Hi, I'm learning about the low-level protocol of wayland and I've found that some implementations (river compositor and wayland-rs) have a different signature for wl_registry.bind
<geemili> Instead of (name, new_id), they are using (name, interface, version, new_id)
gusnan has joined #wayland
<geemili> Is this an error with the documentation?
<vyivel> geemili: in wl_registry.bind, new_id doesn't have a type specified
<vyivel> so an interface and a version are required
<geemili> Ah, okay. So this is me misunderstanding that `new_id` has a much different type than something like `new_id<wl_registry>`?
<geemili> Okay, I see it in the documentation now. Thank you!
<Arnavion> Specifically https://ppaalanen.blogspot.com/2014/07/wayland-protocol-design-object-lifespan.html "Binding is slightly special still..."
kts has quit [Quit: Leaving]
pbsds has quit [Quit: The Lounge - https://thelounge.chat]
pbsds has joined #wayland
junaid has quit [Remote host closed the connection]
mvlad has quit [Remote host closed the connection]
mrkzboo[m] has joined #wayland
jmdaemon has joined #wayland
rv1sr has quit []
CruxOfTheB has joined #wayland
<CruxOfTheB> I'm using gnome on a touchscreen (with no accelerometer) placed "verticaly" or portrait mode. What I see on the screen is correctly oriented 90° but the input from the touchscreen is still in "landscape" mode.
<CruxOfTheB> How can I go about setting this up correctly in wayland ?
<orowith2os[m]> CruxOfTheB: you'd probably do better to ask in GNOME channels, Wayland doesn't really have much say in how all of that is handled.
<wlb> wayland Issue #404 opened by Edgar Neubauer (Desperado17) Nullptr proxy with test apps on Ubuntu 22.04 https://gitlab.freedesktop.org/wayland/wayland/-/issues/404
<CruxOfTheB> Thanks orowith2os[m], will do.
<wlb> wayland Issue #404 closed \o/ (Nullptr proxy with test apps on Ubuntu 22.04 https://gitlab.freedesktop.org/wayland/wayland/-/issues/404)
Leopold__ has joined #wayland
Leopold_ has quit [Ping timeout: 480 seconds]
tent405 has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Remote host closed the connection]
nerdopolis has joined #wayland
sima has quit [Ping timeout: 480 seconds]
ciara has quit [Remote host closed the connection]
ciara has joined #wayland
ciara has quit [Read error: No route to host]
ciara has joined #wayland
agd5f_ has joined #wayland
agd5f_ has quit []
agd5f_ has joined #wayland
agd5f has quit [Ping timeout: 480 seconds]
Nosrep has quit [Remote host closed the connection]
Nosrep has joined #wayland
Brainium has joined #wayland