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
Company has quit [Quit: Leaving]
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
julio7359 has quit [Remote host closed the connection]
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
vyryls has joined #wayland
vyryls has quit [Quit: WeeChat 3.8]
neobrain has quit [Ping timeout: 480 seconds]
Leopold_ has quit [Ping timeout: 480 seconds]
ybogdano1 has quit []
ybogdano has joined #wayland
ybogdano has quit [Remote host closed the connection]
ybogdano has joined #wayland
floof58 is now known as Guest6024
floof58 has joined #wayland
Guest6024 has quit [Ping timeout: 480 seconds]
ybogdano is now known as Guest6029
ybogdano has joined #wayland
Guest6029 has quit [Ping timeout: 480 seconds]
nnm_ has joined #wayland
nnm_ has quit [Remote host closed the connection]
nnm_ has joined #wayland
nnm_ has quit []
nnm_ has joined #wayland
nnm has quit [Ping timeout: 480 seconds]
hardening has joined #wayland
mtretter has joined #wayland
mtretter is now known as mtr[stw]
mtr[stw] has quit []
molinari has joined #wayland
kts has joined #wayland
rasterman has joined #wayland
rv1sr has joined #wayland
kts has quit [Quit: Konversation terminated!]
pH5 has joined #wayland
danvet has joined #wayland
MajorBiscuit has joined #wayland
manuel1985 has joined #wayland
nyn has quit [Ping timeout: 480 seconds]
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #wayland
dcz_ has joined #wayland
pochu has joined #wayland
tzimmermann has joined #wayland
neobrain has joined #wayland
jess has quit [Quit: Lost terminal]
jess has joined #wayland
<pq>
swick[m], I have much more comments for the mastering display info request, but we should agree on the terminology first before I can write proper comments.
kts has joined #wayland
kts has quit []
devilhorns has joined #wayland
junaid has joined #wayland
cool110 has quit [Remote host closed the connection]
junaid has quit [Remote host closed the connection]
<DodoGTA>
Why does setting the primary screen in xrandr do nothing with XWayland?
<pq>
DodoGTA, xrandr on Xwayland is strictly read-only. It cannot be used to reconfigure the Wayland compositor.
<pq>
OTOH, I think Xwayland does support faking video mode changes via RandR, to let apps think they changed it. In reality, video mode does not change.
<emersion>
hm i think it's supposed to work DodoGTA
<emersion>
some sway users have a script to set the X11 primary output via xrandr
<emersion>
(this doesn't affect the Wayland compositor in any way)
<pq>
DodoGTA, what exactly did you expect to see?
alatiera4 is now known as alatiera
tzimmermann has quit [Quit: Leaving]
tzimmermann has joined #wayland
anarsoul|2 has quit [Read error: Connection reset by peer]
anarsoul has joined #wayland
Moprius has joined #wayland
Moprius has quit []
DodoGTA has quit [Quit: DodoGTA]
DodoGTA has joined #wayland
Company has joined #wayland
DodoGTA has quit []
DodoGTA has joined #wayland
floof58 is now known as Guest6060
floof58 has joined #wayland
Guest6060 has quit [Ping timeout: 480 seconds]
Paul33 has joined #wayland
kts has joined #wayland
jmdaemon has quit [Ping timeout: 480 seconds]
neobrain has joined #wayland
kts has quit [Quit: Konversation terminated!]
molinari has quit [Ping timeout: 480 seconds]
molinari has joined #wayland
nerdopolis has quit [Remote host closed the connection]
nerdopolis has joined #wayland
Paul33 has quit [Ping timeout: 480 seconds]
agd5f_ has joined #wayland
<DodoGTA>
pq: So how can I force an Xorg app to run on a specific screen without changing the primary screen in KDE?
<DodoGTA>
Specifically a fullscreen one
<pq>
can't you just... move it there?
<pq>
or does it force itself to a wrong output?
agd5f has quit [Ping timeout: 480 seconds]
<pq>
I have no idea how KDE works there, user interfaces are up to each DE. The Wayland compositor always has the last say in the matter, so you need to somehow tell it what you want.
<DodoGTA>
pq: KDE can weirdly change the XRandR primary screen, but XRandR can't
agd5f has joined #wayland
<DodoGTA>
The particular app does start on that primary screen by default with no way to change it
<zzag>
DodoGTA: for kwin specifically, you could use a window rule; if you have control over source code of the app, you could just make sure that the app sets the corresponding hints so kwin places the window on some specific output
agd5f_ has quit [Ping timeout: 480 seconds]
Moprius has joined #wayland
Moprius has quit []
<pq>
DodoGTA, maybe kwin just immediately undoes what you do with xrandr? In the end, kwin decides what the primary output is anyway.
<pq>
xrandr is never the authoritative configuration tool, not even on Xorg. You need to have the DE specifically adapt to what you might change with xrandr - it's just that on Xorg, the DE cannot stop you from messing with xrandr.
<pq>
well, "never" is an overstatement. On non-DE environments xrandr might be only thing driving the monitor configuration.
<zzag>
That's a deprecated protocol, but you shouldn't use neither kde-primary-output-v1 no kde-output-order-v1
<zzag>
nor*
<zzag>
Those are for plasma
<zzag>
You shouldn't use xrandr command to change the primary output either
<pq>
we can always rightfully blame the app, and that doesn't help the end user...
molinari has joined #wayland
<zzag>
pq: if you want a window to be shown on a particular output, change the relevant window geometry hints. changing the primary output may help you to achieve your goal, but one could argue that there are better options
<pq>
DodoGTA, ^
kts has joined #wayland
<DodoGTA>
zzag: I've tried to change the position window rule in KDE but that does nothing in fullscreen mode