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
cvmn has joined #wayland
Brainium has joined #wayland
caveman has quit [Ping timeout: 480 seconds]
genpaku has quit [Remote host closed the connection]
genpaku has joined #wayland
Brainium has quit [Remote host closed the connection]
Brainium has quit [Quit: Konversation terminated!]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
Company has quit [Quit: Leaving]
kts has joined #wayland
yetoo has quit [Read error: Connection reset by peer]
kts has quit [Quit: Leaving]
yetoo has joined #wayland
kts has joined #wayland
maxzor has quit [Ping timeout: 480 seconds]
naveenk2 has joined #wayland
naveenk2 has quit []
naveenk2 has joined #wayland
ngortheone has quit [Ping timeout: 480 seconds]
ngortheone has joined #wayland
ngortheone has quit [Remote host closed the connection]
ngortheone has joined #wayland
kts has quit [Quit: Leaving]
kts has joined #wayland
ppascher has joined #wayland
hardening has joined #wayland
floof58 is now known as Guest514
floof58 has joined #wayland
Guest514 has quit [Ping timeout: 480 seconds]
dcz_ has joined #wayland
rv1sr has joined #wayland
maxzor has joined #wayland
rasterman has joined #wayland
mvlad has joined #wayland
Lucretia has quit [Read error: No route to host]
Lucretia has joined #wayland
maxzor has quit [Ping timeout: 480 seconds]
Shimmy04003 has quit []
Shimmy04003 has joined #wayland
Shimmy04003 has quit []
Shimmy04003 has joined #wayland
maxzor has joined #wayland
maxzor has quit [Ping timeout: 480 seconds]
molinari has joined #wayland
thevar1able has quit [Remote host closed the connection]
fmuellner has joined #wayland
thevar1able has joined #wayland
thevar1able has quit [Remote host closed the connection]
thevar1able has joined #wayland
molinari has quit [Quit: Leaving]
junaid has joined #wayland
mxz has quit [Quit: cya]
mxz has joined #wayland
peekaboo has joined #wayland
bookworm has quit []
bookworm has joined #wayland
jmdaemon has quit [Ping timeout: 480 seconds]
Hypfer has quit [Quit: Ping timeout (120 seconds)]
Hypfer has joined #wayland
kts has quit [Quit: Leaving]
fmuellner has quit [Ping timeout: 480 seconds]
junaid has quit [Ping timeout: 480 seconds]
hendry has joined #wayland
gusnan has quit [Ping timeout: 480 seconds]
dcz_ has quit [Ping timeout: 480 seconds]
dcz_ has joined #wayland
Szadek has quit [Quit: WeeChat 3.7.1]
Szadek has joined #wayland
gusnan has joined #wayland
kts has joined #wayland
junaid has joined #wayland
mjt has joined #wayland
___nick___ has joined #wayland
sozuba has joined #wayland
junaid has quit [Remote host closed the connection]
___nick___ has quit []
agd5f has quit [Remote host closed the connection]
___nick___ has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
maxzor has joined #wayland
naveenk2 has quit []
dcz_ has quit [Ping timeout: 480 seconds]
agd5f has joined #wayland
<mjt>
what's the difference for X11 applications between running under Xwayland and running under Xorg? I've an example app here (xfreerdp) which has terrible graphics performance under Xwayland but works okay under Xorg
<mjt>
coming from X11 background with x11 video drivers, I was surprized Xwayland does not have any video driver packages. Maybe I'm missing somethihng and Xwayland should provide the same level of performance when given some driver?
<any1>
There's also wlfreerdp
<mjt>
yeah. it doesn't have multimon support
<mjt>
(which is needed here)
<any1>
Is xfreerdp slow or do you have poor image quality?
<mjt>
it's slow. Especially it is noticeable when scrolling
<mjt>
shows a lot of flickering - under xwayland only. under xorg, with everything else the same, it's smooth
<mjt>
(runnig from a tty, either sway=>foot or startx xterm - without any DE, window manager or the like)
<mjt>
under xorg, even the vesa driver is enough for whole thing to work fine - which come as a surprize too
<any1>
it's not a graphics driver problem
<mjt>
since I don't understand [X]wayland architecture at all, and since only Xwayland exposes problem for me, I'm asking here :)
<any1>
Could be a few things. Maybe Xwayland doesn't support some feature, so a sub-optimal code path is chosen, or maybe it's just frame scheduling mismatch.
<mjt>
I see
<any1>
Ahh, looks like an issue with damage tracking.
Shimmy04003 has quit []
<mjt>
is there a way to do something with that? :)
<any1>
Make sure you're running the newest software? It might have been fixed already
<mjt>
yeah that's my first thought already after you mentioned that "looks like" :)
<mjt>
1.20.11 vs 22.1. It's worth to try
<mjt>
(it's a nice numbering jump :)
naveenk2 has joined #wayland
kts has quit [Quit: Leaving]
fmuellner has joined #wayland
Shimmy04003 has joined #wayland
Shimmy04003 has left #wayland [#wayland]
molinari has joined #wayland
Shimmy has joined #wayland
sozuba has quit [Ping timeout: 480 seconds]
ybogdano has quit [Ping timeout: 480 seconds]
naveenk2 has quit []
ybogdano has joined #wayland
Szadek has quit [Ping timeout: 480 seconds]
Szadek has joined #wayland
Szadek has quit []
Szadek has joined #wayland
<mjt>
ok, so 22.1 works significantly better
__nick__ has joined #wayland
___nick___ has quit [Ping timeout: 480 seconds]
flibitijibibo has joined #wayland
Arnavion has quit []
Arnavion has joined #wayland
__nick__ has quit [Ping timeout: 480 seconds]
Brainium has joined #wayland
radu24284303951534727071489559 has joined #wayland
agd5f has quit [Read error: Connection reset by peer]
rasterman has quit [Quit: Gettin' stinky!]
rv1sr has quit []
molinari has quit [Ping timeout: 480 seconds]
radu24284303951534727071489559 has quit [Ping timeout: 480 seconds]
radu24284303951534727071489559 has joined #wayland
molinari has joined #wayland
jmdaemon has joined #wayland
floof58 is now known as Guest561
floof58 has joined #wayland
mvlad has quit [Remote host closed the connection]