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
pac85 has quit [Remote host closed the connection]
pac85 has joined #wayland
hardening has quit [Ping timeout: 480 seconds]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
Consolatis_ has joined #wayland
Consolatis is now known as Guest689
Consolatis_ is now known as Consolatis
Guest689 has quit [Ping timeout: 480 seconds]
pac85 has quit [Remote host closed the connection]
pac85 has joined #wayland
luc4 has quit []
floof58 is now known as Guest696
floof58 has joined #wayland
Guest696 has quit [Ping timeout: 480 seconds]
<repetitivestrain>
btw, am i missing something, or is there a way to attach user data to wl_client's?
<repetitivestrain>
with libwayland-server of course
riverdc has quit [Remote host closed the connection]
riverdc has joined #wayland
<soreau>
usually the user data is set for the request group when calling wl_resource_set_implementation()
cvmn has joined #wayland
CodeSpelunker has joined #wayland
Lyude has quit [Remote host closed the connection]
Lyude has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
cvmn has quit [Ping timeout: 480 seconds]
Meh is now known as AndrewYu
<AndrewYu>
Well, I'm going to try Wayland today. I'm on Parabola GNU/Linux-libre. The Arch wiki doesn't seem to give me information on how to get started. I've picked dwl as my compositor (because I use the dwm window manager on X11). I do not want to use a display manager/login manager, and would prefer to use something like startx/xinit. Not sure what to do next.
<danieldg>
just run it from tth
<danieldg>
*tty
<AndrewYu>
like just "$ dwl"?
<danieldg>
yep
<AndrewYu>
hmm
<AndrewYu>
*tries to resolve dependencies and other issues during `make' of dwl*
<AndrewYu>
(Install wlroots, sudo make install on dwl, run dwl on tty1, got some errors)
<AndrewYu>
Mainly permission denied
<danieldg>
if you're not running logind, seatd, or such, then you should do that
<AndrewYu>
Not sure what these are ... hmm
<AndrewYu>
I'm on OpenRC, if that matters
<AndrewYu>
I do have a systemd system with a similar configuration, I'll try it on there first
<AndrewYu>
Trying seatd
<AndrewYu>
Now it's saying permission denied for /run/seatd.sock
<AndrewYu>
(I rc-service seatd start'ed)
<AndrewYu>
(Same issue with systemctl start seatd on the systemd system)
CodeSpelunker has quit [Quit: CodeSpelunker]
<AndrewYu>
adding myself to the seat group works
* AndrewYu
isn't sure what Wayland has to do with XML
<AndrewYu>
The documentation seems to put protocol examples under XML
<AndrewYu>
But the protocol itself is not?
<danieldg>
the protocol definition files are xml
<danieldg>
the actual protocol is not
<AndrewYu>
Thank god
<AndrewYu>
I mean, nice
<AndrewYu>
Current setup: dwl, with no bar yet, and st + dmenu running under Xwayland
zebrag has quit [Quit: Konversation terminated!]
rv1sr has joined #wayland
PuercoPop has joined #wayland
genpaku has quit [Remote host closed the connection]
genpaku has joined #wayland
soreau has quit [Read error: Connection reset by peer]
soreau has joined #wayland
hardening has joined #wayland
dcz has joined #wayland
dcz_ has quit [Read error: Connection reset by peer]
MajorBiscuit has joined #wayland
danvet has joined #wayland
CME has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
CME has joined #wayland
dcz has quit [Ping timeout: 480 seconds]
ecs has quit [Remote host closed the connection]
ecs has joined #wayland
ecs has quit [Remote host closed the connection]
ecs has joined #wayland
dcz has joined #wayland
luc4 has joined #wayland
ine-one1 has joined #wayland
ine-one1 has quit [Excess Flood]
ine-one1 has joined #wayland
ine-one1 has quit [Excess Flood]
ine-one1 has joined #wayland
ine-one1 has quit [Ping timeout: 480 seconds]
dcz has quit [Ping timeout: 480 seconds]
pac85 has quit [Remote host closed the connection]
pochu has quit [Quit: leaving]
pac85 has joined #wayland
<AndrewYu>
Currently using the st terminal with Xwayland, kinda looking for a similar native alternative
dcz has joined #wayland
<kennylevinsen>
try foot if you want a minimal terminal
pac85 has quit [Remote host closed the connection]
pac85 has joined #wayland
WhizzWr has quit [Quit: Bye!]
dcz has quit [Ping timeout: 480 seconds]
WhizzWr has joined #wayland
mbalmer has joined #wayland
kurhnel has joined #wayland
kurhnel has quit [Remote host closed the connection]
kurhnel has joined #wayland
kurhnel has quit [Remote host closed the connection]
<AndrewYu>
It's not minimal enough for my taste (includes scrollback, URL detection, sixel images by default) though, I'll look into forks
<AndrewYu>
but well, it looks like the best option besides XWayland+st now
pac85 has quit [Remote host closed the connection]
pac85 has joined #wayland
dcz has joined #wayland
___nick___ has joined #wayland
jmdaemon has quit [Ping timeout: 480 seconds]
luc4 has quit []
dcz has quit [Ping timeout: 480 seconds]
___nick___ has quit []
___nick___ has joined #wayland
___nick___ has quit []
devilhorns has joined #wayland
___nick___ has joined #wayland
Lucretia has quit [Remote host closed the connection]
Lucretia has joined #wayland
nerdopolis has joined #wayland
AndroUser2 has joined #wayland
pac85 has quit [Read error: Connection reset by peer]
<AndrewYu>
Using st with xwayland, it beeps every time my terminal gets an ascii bell. Disabling pcspkr fixed that in X11, I don't know how to fix that in WL.
dcz has joined #wayland
<ifreund>
configure your terminal to not beep... oh wait it's st
<ifreund>
you can probably just unload the kernel module as well though
<AndrewYu>
ifreund: I unloaded pcspkr
<AndrewYu>
Yeah I shouldn't be lazy and I should just patch st anyway
<AndrewYu>
(Also I'm looking for a native alternative)
<AndrewYu>
ifreund: "oh wait it's st" should lead to "just make the terminal not beep" more than ever :)
cool110_ has quit [Remote host closed the connection]
cool110 has joined #wayland
dcz has quit [Ping timeout: 480 seconds]
Lucretia has quit [Read error: Connection reset by peer]
Lucretia has joined #wayland
devilhorns has quit []
Moprius has joined #wayland
Brainium has joined #wayland
Moprius has quit [Quit: bye]
AndroUser2 has quit [Remote host closed the connection]
Lucretia has quit []
AndroUser2 has joined #wayland
Lucretia has joined #wayland
AndroUser2 has quit [Remote host closed the connection]
AndroUser2 has joined #wayland
AndroUser2 is now known as pac85
zebrag has joined #wayland
<pac85>
I've read some kernel code, at least on amdgpu atomic modesetting works thanks to double buffered registers so supporting async flips should be totally feasable
<pac85>
Though I'm not sure whether all hardware works like that
<DemiMarie>
Are there any Wayland protocol fuzzers?
<c7s>
firefox
<DemiMarie>
what do you mean?
<c7s>
lots of edge cases with subsurfaces come up when testing firefox
<DemiMarie>
I’m mostly interested in fuzzers that try to find security vulnerabilities in compositors.
inferiormartin has joined #wayland
<DemiMarie>
i509VCB: Thanks! That reminds me: do you have recommendations for dealing with `container_of` based C APIs, as found in libwayland-server and wlroots? Simon Ser is working on Rust bindings for wlroots.
<DemiMarie>
Yeah, he is working on a new binding that is hopefully going to be more maintainable.
c6ristian has joined #wayland
<DemiMarie>
My suggestion was to use macros to generate all of the nasty unsafe pinning and `container_of` code.
<kennylevinsen>
(you're talking to yourself again Demi)
<kennylevinsen>
(bloody matrix bridge)
<DemiMarie>
i509vcb: you need to re-authenticate with NickServ
<DemiMarie>
kennylevinsen: time to somehow get OFTC to use a modern IRC server that supprts SASL?
<kennylevinsen>
That too
<DemiMarie>
If there is anything that the bridge could do better please file an issue.
<kennylevinsen>
theres countless things it can do better, they have been reported and unaddressed for years
<ifreund>
^
<kennylevinsen>
In this case, the bridge is not forwarding the errors it's getting on the IRC side
<DemiMarie>
kennylevinsen: It definitely does forward them for at least some rooms.
<kennylevinsen>
Yeah but it consistently doesn't forward this one (or all clients ignore it, potato/tomato)
<DemiMarie>
I think this may be a bad interaction between the bridge and OFTC’s IRCd.
<kennylevinsen>
possibly
AndroUser2 has joined #wayland
<ifreund>
if users recieve it when using an IRC client but don't when using the bridge, it's a bug with the bridge :D
AndroUser2 has quit [Read error: Connection reset by peer]
<DemiMarie>
True, but there are definitely things (such as proper reconnection) that are very difficult to do without certain support from the IRC side.
pac85 has quit [Read error: Connection reset by peer]
AndroUser2 has joined #wayland
<kennylevinsen>
No SASL is also annoying for real IRC users, indeed
<DemiMarie>
The lack of multi-line messages on IRC is also annoying
<kennylevinsen>
It's fine. What is annoying is that Matrix lacks any ability to abide by constraints and assumes all bridges follow all Matrix features and constraints
<kennylevinsen>
Even with multiline, Matrix and a bridged protocol might have different message limits
<DemiMarie>
I mean from the perspective of me writing messages.
<DemiMarie>
Yes, and that should be able to be handled
<kennylevinsen>
Short messages are ingrained in IRC culture. I like it, good for brevity.
<DemiMarie>
Sometimes I have a rather complex thought, and no long messages makes this hard.
AndroUser2 has quit [Read error: Connection reset by peer]
AndroUser2 has joined #wayland
AndroUser2 has quit [Read error: Connection reset by peer]
AndroUser2 has joined #wayland
<kennylevinsen>
It's a good mental exercise though. If you send an essay it pushes the problem down the chain, giving everybody else more work, which is annoying when the channel is active - *especially* in support channels.
<kennylevinsen>
If it's a complex topic we just send more than one message - e.g., one per sentence.