ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
MrCooper__ has joined #wayland
MrCooper_ has quit [Ping timeout: 480 seconds]
MrCooper_ has joined #wayland
Tokoyami has quit [Quit: ~@~]
Tokoyami has joined #wayland
MrCooper__ has quit [Ping timeout: 480 seconds]
glennk has quit [Ping timeout: 480 seconds]
MrCooper__ has joined #wayland
MrCooper_ has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
tokyo4j has quit [Remote host closed the connection]
tokyo4j has joined #wayland
coldfeet has joined #wayland
rv1sr has joined #wayland
wmlhwl has quit [Quit: Leaving]
___nick___ has joined #wayland
__nick__ has quit [Ping timeout: 480 seconds]
bindu has joined #wayland
bindu_ has quit [Ping timeout: 480 seconds]
Calandracas has joined #wayland
agd5f has quit [Ping timeout: 480 seconds]
agd5f has joined #wayland
agd5f_ has joined #wayland
agd5f has quit [Read error: Connection reset by peer]
agd5f_ has quit []
agd5f has joined #wayland
__nick__ has joined #wayland
shankaru has joined #wayland
___nick___ has quit [Ping timeout: 480 seconds]
<eqw>
is there a wayland way to `xdotool key`/`xdotool type` ?
tzimmermann has quit [Quit: Leaving]
tokyo4j has quit [Ping timeout: 480 seconds]
<danieldg>
eqw: wtype, if your compositor supports the virtual keyboard protocol
<eqw>
how to find out what my compositor is? Is it possible to replace my compositor?
yaslam has joined #wayland
<danieldg>
your compositor is the program that implements the wayland server. Unlike X, there isn't one Xorg binary - wayland is a library that compositors use
yaslam has quit []
<danieldg>
you can choose to use another one
yaslam has joined #wayland
tokyo4j has joined #wayland
feaneron has quit [Ping timeout: 480 seconds]
hergertme has joined #wayland
__nick__ has quit [Ping timeout: 480 seconds]
coldfeet has quit [Remote host closed the connection]
feaneron has joined #wayland
bjorkintosh has quit [Quit: "Every day, computers are making people easier to use." David Temkin]
bjorkintosh has joined #wayland
yaslam has quit [Ping timeout: 480 seconds]
yaslam has joined #wayland
coldfeet has joined #wayland
fmuellner has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
mohit815822635306 has quit [Remote host closed the connection]
mohit815822635306 has joined #wayland
rv1sr has quit []
iomari891 has joined #wayland
<grinja1>
is there anything in protocol preventing having more workspaces side by side (or any layout) on one output monitor or outputs are somehow exclusive? Also, I'm not reffering to workspace protocol only, asking more in general
iomari891 has quit [Ping timeout: 480 seconds]
<vyivel>
grinja1: *in general*, a compositor can manage the windows however it wants
<vyivel>
so no restrictions
<vyivel>
actually it think multiple workspaces per output is allowed by the workspace protocol too
<grinja1>
vyivel: thanks, I thought so, but needed confirmation
<grinja1>
last time I checked was before workspace protocol, now I took a quick look and groups looks like it, I think
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
coldfeet has quit [Remote host closed the connection]
ity has quit [Quit: WeeChat 4.4.4]
<Consolatis>
right, the general idea behind the groups is to either have a single one across all outputs or every output having its own group and independent set of workspaces. groups can not be configured by clients so its up to the compositor to implement it in a way that best suits its behavior
<dviola>
I got a sway crash today on archlinux which is very uusual, right after I started keepassxc (xwayland)
<dviola>
[813025.541618] sway[652]: segfault at 61d7902827d3 ip 0000717d61dc3110 sp 00007ffdbb35c3a0 error 4 in libwayland-server.so.0.23.1[a110,717d61dbe000+8000] likely on CPU 8 (core 5, socket 0)