ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
nerdopolis has quit [Ping timeout: 480 seconds]
<i509vcb>
What is the intended use for a xdg-toplevel resize edge of none?
fmuellner has quit [Ping timeout: 480 seconds]
co1umbarius has joined #wayland
nerdopolis has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
tesjhg has joined #wayland
sevz has joined #wayland
nerdopolis has quit [Remote host closed the connection]
nerdopolis has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
tesjhg has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
jtbx_ has joined #wayland
jtbx has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
d42 has quit [Ping timeout: 480 seconds]
d42 has joined #wayland
tzimmermann has joined #wayland
tzimmermann has quit [Remote host closed the connection]
tzimmermann has joined #wayland
Fischmiep has quit [Ping timeout: 480 seconds]
Fischmiep has joined #wayland
jlco has quit [Ping timeout: 480 seconds]
mblenc1 has joined #wayland
rv1sr has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
mblenc has joined #wayland
mblenc1 has quit [Ping timeout: 480 seconds]
jlco has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
mblenc has quit [Ping timeout: 480 seconds]
jlco has quit [Ping timeout: 480 seconds]
jlco has joined #wayland
mvlad has joined #wayland
rasterman has joined #wayland
rgallaispou has joined #wayland
sevz has quit [Quit: WeeChat 4.0.4]
Kerr has quit [Remote host closed the connection]
leon-anavi has joined #wayland
Company has joined #wayland
pochu has joined #wayland
vyivel has quit [Read error: Connection reset by peer]
vyivel has joined #wayland
iomari891 has joined #wayland
mblenc has joined #wayland
tjaden has quit [Ping timeout: 480 seconds]
junaid has joined #wayland
vova has joined #wayland
<vova>
Hi
<vova>
Do you think it's possible to do screensharing in wayland without using pipewire ?
<soreau>
yes
<soreau>
of course it might depend on what compositor you're using
<vova>
Currently I'm using river
<soreau>
then you can use wf-recorder, I believe
ascent12 has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
<vova>
Except for screensharing (via xdg-desktop-portal ?), pipewire is required for what else on wayland ?
ascent12 has joined #wayland
<YaLTeR[m]>
depending on your definition of wayland, from "nothing" to "remote desktop, cameras, audio playback and recording, ..."
<soreau>
pipewire isn't required for anything afaik, but it can handle audio (like pulseaudio)
<soreau>
so in practice, if you remove it, you might need to install pulseaudio to have apps that use pulseaudio to output sound
<vova>
I always thought that pipewire was required for screensharing/webcam access/etc. I asked that question because tbh just alsa is enough for my use case, so having to install pipewire+wireplumber just to do screensharing seemed a little bit too much. But screensharing with wf-recorder seems to work just fine !
junaid has quit [Remote host closed the connection]
co1umbarius has quit [Ping timeout: 480 seconds]
co1umbarius has joined #wayland
junaid has joined #wayland
junaid has quit [Remote host closed the connection]
Company has quit [Remote host closed the connection]
fmuellner has joined #wayland
cmichael has joined #wayland
d42 has quit []
Zeroine_ has joined #wayland
Zeroine has quit [Read error: Connection reset by peer]
DodoGTA has quit [Remote host closed the connection]
d42 has joined #wayland
mohit815 has quit [Quit: mohit815]
mohit815 has joined #wayland
vyivel has quit [Ping timeout: 480 seconds]
vyivel has joined #wayland
crazybyte has quit [Quit: Bye]
crazybyte has joined #wayland
tjaden has joined #wayland
haise01 has joined #wayland
pbsds has quit [Ping timeout: 480 seconds]
pbsds has joined #wayland
Fxzxmic has joined #wayland
DodoGTA has joined #wayland
AnuthaDev has joined #wayland
luna__ has joined #wayland
luna__ has quit []
<Max1>
Is it a known issue that Weston doesn't reposition popups correctly? e.g. if you maximize Chromium in Weston, the submenus of the three dot menu are positioned outside of the screen
vyivel has quit [Remote host closed the connection]
<dottedmag>
Max1: sounds like a Weston bug?
larunbe has joined #wayland
Moprius has joined #wayland
alarumbe has quit [Ping timeout: 480 seconds]
Fxzx_mic has joined #wayland
Fxzxmic has quit [Ping timeout: 480 seconds]
<pq>
Max1, if you make sure there is an issue filed, then it would be known. Mention whether Chromium runs through Xwayland or as Wayland native, and what the steps to reproduce that are, please.
eighthours has quit [Remote host closed the connection]
disapper3nce has joined #wayland
disapper3nce has quit []
iomari891 has quit [Ping timeout: 480 seconds]
Company has joined #wayland
mblenc1 has joined #wayland
Moprius has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
exp80 has quit [Ping timeout: 480 seconds]
rahl has quit [Quit: Lost terminal]
nerdopolis has quit [Ping timeout: 480 seconds]
rv1sr has quit []
<bunni>
using the desktop shell in weston, is there any concept of a desktop icon, or, a way to increase the launcher bar size to make the icons a bit more obvious and easier to click on a touchscreen?
<bunni>
or are there any other alternatives to get similar functionality of large-ish icons that can be pressed
<aleasto>
why does mutter send the preferred_fractional_scale only after a buffer is attached and the surface state commited? i create a surface with xdg_toplevel role, maximized, and i know mutter knows which output to put the surface on because it sends a configure with the correct maximized size, so surely it knows the preferred scale too at this point
<aleasto>
i don't understand why i should commit a buffer with the wrong scale before mutter can tell me the right scale
<kchibisov>
aleasto: it all depends on the role of the surface.
<aleasto>
eh i wrote a lot of text but it's in there :D
<aleasto>
it's an xdg_toplevel
<aleasto>
maximized
<kchibisov>
I understand.
<kchibisov>
I'm answering the "why" part.
<kchibisov>
So the logic mutter has might be not tuned for surface roles.
<kchibisov>
xdg_shell(protocol) suggests that you should send state(including scaling) the way you expect.
<kchibisov>
but mutter does nothing wrong from the correctness pov, it just isn't optimal for clients.
<aleasto>
yea...
<aleasto>
i have not checked whether the same behaviour happens for the wl_surface preferred_buffer_scale (integer)
<kchibisov>
I had similar issue, but because 'order' is not defined or suggested.
<kchibisov>
Which is true, because you can't define order.
<kchibisov>
unless you know the exact role of the object.
<kchibisov>
So if you take arbitrary wl_surface you can't send scaling early on.
<aleasto>
i see your change is merged. so compositors should comply and send it immediatly?
<kchibisov>
It just says that it will.
<kchibisov>
So sort of, but compositors can violate.
<kchibisov>
Though, I don't see a reason to violate that.
<aleasto>
fwiw i know kwin does what i expect
<kchibisov>
I mean, bug mutter.
mblenc1 has quit [Ping timeout: 480 seconds]
<kchibisov>
The reason the change you're seing is merged and was submitted, because we have a "every frame is perfect", yet until you follow what I wrote in MR you can't do that.
<aleasto>
yea i'll open a ticket against mutter. thanks!
<aleasto>
i feel lucky i caught you reading
<kchibisov>
You can get lucky by searching the bug tracker.
<kchibisov>
There's an issue about this first frame not being perfect on HiDPI.
<kchibisov>
it's still open, because we have cursors.
gallo has quit [Remote host closed the connection]