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
fmuellner has quit [Ping timeout: 480 seconds]
gschwind has quit [Quit: Leaving]
wroathe has quit [Ping timeout: 480 seconds]
gusnan has quit [Ping timeout: 480 seconds]
gusnan_ has joined #wayland
glennk has quit [Ping timeout: 480 seconds]
gusnan_ has left #wayland [#wayland]
gusnan___ has joined #wayland
AJC_Z0 has joined #wayland
AJ_Z0 has quit [Read error: Connection reset by peer]
AJC_Z0 is now known as AJ_Z0
AJ_Z0 has quit [Read error: Connection reset by peer]
<tleydxdy>
for libinput when the compositor is reading the mouse does that mean no other process can read the mouse? not even root
slattann has quit []
<tleydxdy>
nevermind, forgot I had to always call get_event
cvmn has joined #wayland
floof58 is now known as Guest3721
floof58 has joined #wayland
Guest3721 has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
cvmn has quit [Ping timeout: 480 seconds]
kts has joined #wayland
zebrag has quit [Quit: Konversation terminated!]
kts has quit [Quit: Leaving]
kts has joined #wayland
kts has quit [Quit: Leaving]
chipxxx has quit [Remote host closed the connection]
wroathe has quit [Ping timeout: 480 seconds]
kts has joined #wayland
chipxxx has joined #wayland
cool110_ has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Leaving]
<dottedmag>
mntirc: All compositors failing in the same manner points to a problem in libwayland. And 4096 -> 0 failure kinda hints at some kind of padding problem or something similar.
<dottedmag>
Just a wild guess of course
cool110 has joined #wayland
dcz_ has joined #wayland
mtretter has quit [Remote host closed the connection]
mtretter has joined #wayland
dcz_ has quit [Read error: Connection reset by peer]
dcz_ has joined #wayland
rasterman has joined #wayland
fmuellner has joined #wayland
rgallaispou has joined #wayland
rgallaispou1 has quit [Ping timeout: 480 seconds]
flibit has joined #wayland
glennk has joined #wayland
flibitijibibo has quit [Ping timeout: 480 seconds]
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
bookworm has quit [Read error: Connection reset by peer]
bookworm has joined #wayland
<MrCooper>
mntirc: maybe check that the failing processes don't pick up stale libraries from /usr/local or somewhere
dcz has joined #wayland
dcz_ has quit [Ping timeout: 480 seconds]
dcz has quit [Ping timeout: 480 seconds]
mokee has joined #wayland
<mntirc>
dottedmag: MrCooper: thx for the ideas. i did clear out usr/local/lib to no avail. i'm gonna continue debugging this now and chroot into and older image to see if it works from there
<mntirc>
i have a good rescue system, and copied libffi from the bad system into /usr/local/lib and now weston-info shows the same garbage data on a working sway desktop
andyrtr has joined #wayland
<dottedmag>
TIL libwayland depends on libffi
Net147 has quit [Quit: Quit]
rv1sr has quit []
<mntirc>
ok, i managed to fix my system by copying in libffi.so.8.1.0 instead of the seemingly broken libffi.so.8.1.1
Net147 has joined #wayland
<MrCooper>
no issues here with the latter from libffi8 3.4.3-3 FWIW
<zubzub>
what (debian/ubuntu) dependency do I need for XWayland when it complains about "dri" not being found? I think I installed just about every possible dev package candidate and it keeps complaining
<mntirc>
interestingly, libffi8_3.4.3-2_arm64.deb from snapshots is still ok
chipxxx has quit [Ping timeout: 480 seconds]
bodiccea has joined #wayland
floof58 is now known as Guest3736
floof58 has joined #wayland
Guest3736 has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
<zubzub>
hmm xwayland compilation fails with dri3 errors like: error: implicit declaration of function ‘dri3_send_open_reply’ but shouldn't that dri3 lib be compiled/handled by the Xwayland build itself?