ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
abeltramo5895 has quit [Read error: Connection reset by peer]
abeltramo58958 has joined #wayland
abeltramo58958 has quit [Read error: Connection reset by peer]
abeltramo5895 has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
Guest9103 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest9118
rv1sr has joined #wayland
fmuellner has quit []
fmuellner has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
Guest9118 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest9128
sunrise890 has joined #wayland
<i509vcb> orowith2os[m]: wayland-rs has a full rust mode but you'll have to reinvent gl and vulkan wsi to avoid pulling in libwayland
<ids1024> https://registry.khronos.org/EGL/extensions/EXT/EGL_EXT_image_dma_buf_import.txt says the call can fail due to driver restrictions in pitch and offset. `zwp_linux_dmabuf_feedback_v1::main_device` says "Clients need to create buffers that the main device can import and read from, otherwise creating the dmabuf wl_buffer will fail (see the wp_linux_buffer_params.create and create_immed
<ids1024> requests for details)."
<ids1024> Does it follow that `create_immed` may produce a protocol error for an offset or stride that is valid but not supported by the `main_device`, without any way for the client to know this restriction through the protocol?
Company has quit [Remote host closed the connection]
sunrise890 has quit []
ciara has quit [Read error: Connection reset by peer]
ciara has joined #wayland
junaid has joined #wayland
junaid_ has joined #wayland
junaid has quit [Remote host closed the connection]
junaid_ has quit []
<emersion> yes
<emersion> or any other driver-specific reason really
sima has joined #wayland
sevz has quit [Quit: WeeChat 4.0.2]
ohmacs^ has quit [Ping timeout: 480 seconds]
ohmacs^ has joined #wayland
RAOF has quit [Remote host closed the connection]
RAOF has joined #wayland
Leopold_ has joined #wayland
Leopold__ has quit [Ping timeout: 480 seconds]
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
pieguy128 has quit [Ping timeout: 480 seconds]
RAOF_ has joined #wayland
RAOF_ has quit [Remote host closed the connection]
RAOF_ has joined #wayland
sunrise890 has joined #wayland
RAOF has quit [Ping timeout: 480 seconds]
RAOF_ is now known as RAOF
slim has joined #wayland
pieguy128 has joined #wayland
floof58 has quit [Ping timeout: 480 seconds]
sunrise890 has quit []
floof58 has joined #wayland
leon-anavi has joined #wayland
jmdaemon has quit [Ping timeout: 480 seconds]
zvarde1988303206779191688 has joined #wayland
mvlad has joined #wayland
zvarde198830320677919168 has quit [Ping timeout: 480 seconds]
zvarde1988303206779191688 is now known as zvarde198830320677919168
sunrise890 has joined #wayland
tzafrir has quit [Quit: Quassel quit queasily, quoting Quixotic quip]
sunrise890 has quit []
tzafrir has joined #wayland
fmuellner has joined #wayland
Hypfer has quit [Ping timeout: 480 seconds]
sunrise890 has joined #wayland
cvmn has quit [Remote host closed the connection]
caveman has joined #wayland
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
jess has joined #wayland
nerdopolis has joined #wayland
Hypfer has joined #wayland
anarsoul|2 has quit [Remote host closed the connection]
anarsoul has joined #wayland
<WhyNotHugo> Is it possible to run XWayland with a nested X11 window manager?
<WhyNotHugo> This is mostly theoritical curiosity, but if someone wanted to use X11, could they do it entirely in a nested session (with something like cage)?
<emersion> yes
<WhyNotHugo> Oh, I guess that the main details here is not to run it with -rootless
nerdopolis has quit [Remote host closed the connection]
nerdopolis has joined #wayland
shmf1385[m] has left #wayland [#wayland]
sunrise890 has quit []
nerdopolis has quit [Ping timeout: 480 seconds]
leon has joined #wayland
Company has joined #wayland
Moprius has joined #wayland
<MrCooper> ids1024: an LD_PRELOAD based keylogger doesn't break any security boundary; in contrast, an X based one can log all input any other client receives
Moprius has quit [Quit: bye]
junaid has joined #wayland
sunrise890 has joined #wayland
<orowith2os[m]> jadahl: fwiw are you interested in landing some support for `GtkSettings:gtk-application-prefer-dark-theme` in the GTK libdecor plugin?
junaid_ has joined #wayland
<orowith2os[m]> I need to look at the whole process so it's set only when it needs to be (system is dark mode) but seems like something to have
junaid has quit [Remote host closed the connection]
junaid_ has quit []
junaid has joined #wayland
<jadahl> orowith2os[m]: why not
<orowith2os[m]> jadahl: alrighty, gonna research it a bit :)
DPA has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
<iomari891> greetings, can I safely use bindfs to mount a folder as /var?
<iomari891> wrong channel. sorry
sunrise890 has quit []
JakeSays1 has quit [Quit: later..]
JakeSays has joined #wayland
junaid has quit [Remote host closed the connection]
<ids1024> emersion: That does seem like an issue with create_immed. Unless you specifically know what the main device can import, there would be no way to safely use it without getting a protocol error. (With `create` you can handle this, but Mesa's EGL and WSI code seems to only use create_immed currently.)
<emersion> that's an issue with a single GPU as well
<i509vcb> If import can fail due to reasons the driver or application can't predict, I don't see a reason to even have create_immed
DPA has joined #wayland
<ids1024> Yeah, it shouldn't be possible to get a protocol error for something the client can't foresee and avoid. Though it's also a bit odd that `create_immed` says it may produce a protocol on failure, or may send a `failed` event.
<emersion> there is no "failed" event in this case
<ids1024> "Upon import failure, either of the following may happen, as seen fit by the implementation: - the client is terminated with one of the following fatal protocol errors: - INCOMPLETE, INVALID_FORMAT, INVALID_DIMENSIONS, OUT_OF_BOUNDS, in case of argument errors such as mismatch between the number of planes and the format, bad format, non-positive width or height, or bad offset or
<ids1024> stride. - INVALID_WL_BUFFER, in case the cause for failure is unknown or plaform specific. - the server creates an invalid wl_buffer, marks it as failed and sends a 'failed' event to the client. The result of using this invalid wl_buffer as an argument in any request by the client is defined by the compositor implementation."
<ids1024> So `create_immed` is documented to send a protocol error, OR send `failed` and have the wl_buffer behave in future requests in an implementation defined manner.
<ids1024> Oh, I guess the formatting there is kind of broken reading it on wayland.app
<ids1024> The grouping here is clearer in the XML, but it still suggests that `failed` could be sent, instead of a protocol error, and doesn't specify that should only happen for certain types of errors. So that is a possible behavior here as defined by the spec.
<emersion> there is no way to send the failed event in the create_immed path
<emersion> create_immed doesn't create the object where the failed event is sent
<ids1024> Failed is an event on the `zwp_linux_buffer_params_v1`
<emersion> ah, right
<emersion> i thought it was separate
<i509vcb> I'd probably err towards import on the server being 100% fallible
jmdaemon has joined #wayland
<ids1024> If it fails, there's no obvious way for the client to know what will (other than trying different parameters that tend to be better supported), but it could at least fall back to `wl_shm`, which should always work. But currently mesa and Nvidia's egl-wayland just use create_immed.
sevz has joined #wayland
<emersion> the real solution is buffer constraints
sunrise890 has joined #wayland
anki is now known as xantoz
Bran[m] is now known as floki[m]
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #wayland
leon-anavi has quit [Quit: Leaving]
leon has quit [Remote host closed the connection]
that_guy has quit [Quit: I'M OUT]
that_guy has joined #wayland
sunrise890 has quit []
sunrise890 has joined #wayland
sunrise890 has quit []
sunrise890 has joined #wayland
Guru_DE has joined #wayland
Leopold__ has joined #wayland
Leopold_ has quit [Ping timeout: 480 seconds]
junaid has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
sunrise890 has quit []
junaid has quit [Ping timeout: 480 seconds]
<bl4ckb0ne> is somebody already in charge to do next week's governance meeting?
<jadahl> bl4ckb0ne: last one we thought there would be an inputfd one so didn't assigned anyone to schedule a next one
junaid has joined #wayland
<bl4ckb0ne> yeah i messed up last time
<bl4ckb0ne> there was one already scheduled
<bl4ckb0ne> ill take care of it then
<bl4ckb0ne> and try not to put the admin link this time
Moprius has joined #wayland
<manuels> hey guys i have another niche case. i want my launcher to be able to paste text into the frontmost window. like open launcher, select snippet or some other text source and paste it.
<manuels> i guess wayland is not that straight forward in this case, but is it possible?
<manuels> but somehow is has to be possible right, i mean the launcher basically acts as an input method. what do i have to do to achieve such a thing?
junaid has quit [Remote host closed the connection]
junaid has joined #wayland
sima has quit [Ping timeout: 480 seconds]
rv1sr has quit []
sevz has quit [Ping timeout: 480 seconds]
junaid has quit [Ping timeout: 480 seconds]
mvlad has quit [Remote host closed the connection]
akik has joined #wayland
<akik> hi, i'm using Xwayland in wsl 2 (windows) to start it up for :1. the problem is i can't find where the X1 socket is. i can see that it exists somewhere https://termbin.com/onyu
wb9688_ has joined #wayland
wb9688 has quit [Ping timeout: 480 seconds]
<akik> (/tmp/.X11-unix/X0 exists but that's the wsl 2 default)
nerdopolis has joined #wayland
wb9688_ has quit []
<akik> the https://termbin.com/onyu output is from lsof ran in wsl 2
wb9688 has joined #wayland
Moprius has quit [Quit: bye]
nerdopolis has quit [Ping timeout: 480 seconds]
jmdaemon has quit [Quit: WeeChat 4.0.1]
paulk-bis has joined #wayland
lileo has joined #wayland
paulk has quit [Ping timeout: 480 seconds]
Moprius has joined #wayland
Moprius has quit [Quit: bye]
marliere has joined #wayland
rbmarliere has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
<Ermine> X1 should be in the same place as X0, shouldn't it?
<orowith2os[m]> Any X11 sockets are basically required to be in /tmp.X11-unix
<orowith2os[m]> well, you can also go over the network, but that's another topic, and less performant
<orowith2os[m]> but that location is hardcoded, and it's a real pain, especially for us Flatpak folks; see https://github.com/flathub/org.freedesktop.Platform.VulkanLayer.gamescope/issues/6 for an example resulting from it
nerdopolis has quit [Ping timeout: 480 seconds]