ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
crazybyte has quit [Quit: Ping timeout (120 seconds)]
crazybyte has joined #wayland
vyivel has quit [Read error: Connection reset by peer]
vyivel has joined #wayland
RAOF has quit [Remote host closed the connection]
mstoeckl has quit [Quit: Lost terminal]
vyivel has quit [Read error: Connection reset by peer]
RAOF has joined #wayland
divark has joined #wayland
divark has quit []
nerdopolis has quit [Remote host closed the connection]
vyivel has joined #wayland
nerdopolis has joined #wayland
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
vyivel has quit [Read error: Connection reset by peer]
vyivel has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
divark has joined #wayland
divark has quit []
vyivel has quit [Read error: Connection reset by peer]
PopLamina has quit [Ping timeout: 480 seconds]
vyivel has joined #wayland
nerdopolis has quit [Remote host closed the connection]
<Riolku>
Stupid question. Why do I care about devices being grouped into seats? To me, there exists keyboards and pointers and touch devices. Why does it matter that they have their own seats?
<jadahl>
Riolku: for the theoretical use case where multiple people interact with the same display server, each with their own keyboard/mouse pair
DodoGTA has quit []
DodoGTA has joined #wayland
bim9262_ has joined #wayland
bim9262 has quit [Ping timeout: 480 seconds]
junaid has quit [Remote host closed the connection]
DodoGTA has quit [Ping timeout: 480 seconds]
tzimmermann has joined #wayland
<emersion>
nice castle daniels :P
<daniels>
it’s not mine :(
<emersion>
not yet
kts has joined #wayland
sima has joined #wayland
kts has quit [Ping timeout: 480 seconds]
vyivel has joined #wayland
rasterman has joined #wayland
DodoGTA has joined #wayland
sevz has quit [Quit: WeeChat 4.0.5]
glennk has joined #wayland
leon-anavi has joined #wayland
iomari891 has joined #wayland
vaishakh-gk has joined #wayland
rv1sr has joined #wayland
vaishakh-gk has quit []
i509vcb has quit [Quit: Connection closed for inactivity]
agd5f_ has joined #wayland
agd5f has quit [Ping timeout: 480 seconds]
cmichael has joined #wayland
ramcq has quit [Quit: WeeChat 3.7.1]
axet has joined #wayland
<axet>
hi! i'm tyring to enable waylang and have some issues. first I unable to add custom resolution. i get black screen instead. looks like wayland picking wrong refresh rate from 'video=eDP-1:1366x768@60' gnome showing 60.02 refresh rate and it fails. Same on xrandr mode. I have two refresh rates 60.00 and 60.02 last one fails on xrandr. is here a way to force wayland to use 60.00?
<axet>
second issue. i unable to disable touch pad middle key. i have no issues remapping keys on x11. but failed on wayland. Option "ButtonMapping" "1 1 3 4 5 6 7". even using xinput failed.
<axet>
3) no xgamma support
mclasen has joined #wayland
Amber_Harmonia has quit [Ping timeout: 480 seconds]
vsyrjala_ has joined #wayland
<kennylevinsen>
axet: Wayland is a protocol. If you use GNOME, you're using their Wayland server (Mutter). You should ask for help in a GNOME channel.
<axet>
thanks. i didn't know this is about protocl! i go there
<kennylevinsen>
xrandr, xinput and such are not applicable though - they are configuring X11
vsyrjala has quit [Ping timeout: 480 seconds]
<kennylevinsen>
But you'll have to ask GNOME for the appropriate replacement :)
<MrCooper>
note that the Matrix rooms are canonical for GNOME, and the IRC bridge isn't working currently
<axet>
MrCooper they moved to Matrix you are saying?
<MrCooper>
basically yeah
<kennylevinsen>
MrCooper: ... did you ack yourself there with "basically yeah" did you respond to yet another unauth'd Matrix user?
* kennylevinsen
thinks this guessing game is getting old
<MrCooper>
replying to axet, I'm not on Matrix though, so a reverse issue maybe?
<kennylevinsen>
Ah ok then I just read too much into it
anarsoul|2 has joined #wayland
anarsoul has quit [Read error: Connection reset by peer]
Amber_Harmonia has joined #wayland
Moprius has joined #wayland
privacy has joined #wayland
fmuellner has joined #wayland
<jadahl>
axet: #gnome-shell on IRC or matrix. there used to be a bridge but no more
ramcq has joined #wayland
Company has joined #wayland
nerdopolis has joined #wayland
Fxzxmic has joined #wayland
privacy has quit [Quit: Leaving]
glennk has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
nerdopolis has quit [Remote host closed the connection]
nerdopolis has joined #wayland
<Fxzxmic>
Will wayland no longer have remote rendering support?
cool110 has joined #wayland
<soreau>
Fxzxmic: it's not really up to 'wayland' but the compositor, how it will support this
cool110 is now known as Guest2962
Guest2671 has quit [Remote host closed the connection]
Guest2962 has quit [Remote host closed the connection]
<soreau>
but the short answer is, that remote rendering works in many different ways and supported by different compositors and components, differently
cool110_ has joined #wayland
<soreau>
your best bet is to ask in your compositor support channel
cool110_ is now known as Guest2963
<Fxzxmic>
Sorry, I don't quite understand this aspect.
<Fxzxmic>
What I'm talking about is like in the X environment, handing over the graphics of a host without a graphics card to a local graphics card for rendering, and then displaying the software interface on the local host.
Guest2963 has quit [Remote host closed the connection]
<Fxzxmic>
Just like SSH's X11 forwarding.
<soreau>
there is waypipe
cool110- has joined #wayland
<soreau>
but you can also run a wayland display server on a headless box and vnc into it where there are graphics
<Fxzxmic>
I don't like VNC.
<Fxzxmic>
However, I am glad that the feature I mentioned has not been deprecated in the wayland environment.
<axet>
hmm i didn't know actually here is waypipe
<axet>
nice to know
kts has joined #wayland
<MrCooper>
"remote X" these days really means "X over SSH" except for some rounding error, and waypipe works mostly the same as that
<Fxzxmic>
I don't think so, it can also be done without SSH.
Moprius has quit [Quit: bye]
<MrCooper>
I'm saying the number of users actually doing so is a rounding error at this point
<soreau>
also, it's not really relevant in this channel
<kennylevinsen>
also, X forwarding with modern X does not "hand over graphics to a local graphics card for rendering". The remote host renders the image, likely with software rendering, and inefficiently sends pictures...
pounce has quit [Remote host closed the connection]
pounce has joined #wayland
<kennylevinsen>
waypipe works way better
pounce has quit [Remote host closed the connection]
pounce has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
pounce has quit [Remote host closed the connection]
pounce has joined #wayland
kts has quit [Ping timeout: 480 seconds]
pounce has quit [Remote host closed the connection]
pounce has joined #wayland
pounce has quit [Remote host closed the connection]
pounce has joined #wayland
dcz_ has joined #wayland
nerdopolis has joined #wayland
junaid has joined #wayland
axet has quit [Remote host closed the connection]
pochu has quit [Quit: leaving]
nerdopolis has quit [Remote host closed the connection]
nerdopolis has joined #wayland
junaid has quit [Remote host closed the connection]
melonai has quit [Quit: Ping timeout (120 seconds)]
axet has joined #wayland
kts has joined #wayland
dcz_ has quit [Read error: Connection reset by peer]
dcz_ has joined #wayland
tzimmermann has quit [Quit: Leaving]
melonai has joined #wayland
kts has quit [Ping timeout: 480 seconds]
dcz_ has quit [Read error: No route to host]
AnuthaDev has joined #wayland
dcz_ has joined #wayland
AnuthaDev has quit []
AnuthaDev has joined #wayland
flom84 has joined #wayland
AnuthaDev has quit []
AnuthaDev has joined #wayland
i509vcb has joined #wayland
flom84 has quit [Remote host closed the connection]
cmichael has quit [Quit: Leaving]
flom84 has joined #wayland
dcz_ has quit [Read error: Connection reset by peer]
dcz_ has joined #wayland
Fxzxmic has quit [Quit: Konversation exit!]
dcz_ has quit [Read error: No route to host]
kenny has quit [Ping timeout: 480 seconds]
dcz_ has joined #wayland
<pitust>
so i'm making my own semi-libwayland thing, and i'm really confused about wl_registry.bind
kenny has joined #wayland
<pitust>
the xml says it takes two params, a uint (name) and new_id (id)
<vyivel>
lol true it's faster to open the local copy of libwayland and check what i want
<pitust>
my protocol lib seems to work
<pitust>
now all i have to do is create a window
<pitust>
somehow
<pitust>
hmm so i don't get a window for some reason
<kennylevinsen>
wl_surface -> xdg_surface -> xdg_toplevel, then commit a buffer from wl_shm
<kennylevinsen>
first empty configure after xdg_toplevel to set the role, then commit a buffer in the size you want with some content to make a visible window
<kennylevinsen>
you need to cmmit without the buffer first
<kennylevinsen>
after applying the xdg_toplevel role
<pitust>
ah
<pitust>
==2043195==ERROR: AddressSanitizer: stack-use-after-return on address 0xffff299fe188 at pc 0xaaab3ac7401c bp 0xffffd4156a00 sp 0xffffd4156a18
<pitust>
exciting
<kennylevinsen>
yeah don't do that
<pitust>
at least i build with asan so i can see the error ig
<pitust>
i love how the asan stacktrace is like completly unreadable
<pitust>
thanks i really wanted to know the error is in std::enable_if<is_invocable_r_v<main::$_2::operator()() const::'lambda0'(unsigned int), void libwl_object::register_event<xdg_surface xdg_surface::on_configure<main::$_2::operator()() const::'lambda0'(unsigned int)>(main::$_2::operator()() const::'lambda0'(unsigned int))::'lambda'(libwl_deser&)>(unsigned int, main::$_2::operator()() const::'lambda0'(
<kennylevinsen>
well, that one is mostly on C++
<pitust>
thats true
<pitust>
okay sway, why is this not an error: 01:35:58.446 [wlr] [render/gles2/texture.c:39] Invalid stride 300 (too small for 4 bytes-per-pixel and width 100)
<pitust>
like a hard wayland error
<pitust>
oh niceee
<pitust>
i have a square on the screen
<vyivel>
congrats
<pitust>
okay so i guess xdg_toplevel.configure is triggered when the window resizes or something
<vyivel>
it's triggered when a compositor wants the toplevel to assume a new state