Display update problems with Xorg extension
martin f krafft
Hello there,
I've just configured two Debian laptops to use the X.org extension. X.org server is 1.20.11-1, and the TigerVNC module version is 1.11.0, though it announces itself as 1.0.0 in the log:
[ 1285.129] (II) Module vnc: vendor="TigerVNC Project"
[ 1285.129] compiled for 1.20.10, module version = 1.0.0
[ 1285.129] Module class: X.Org Server Extension
[ 1285.129] ABI class: X.Org Server Extension, version 10.0 Both laptops are running Xfce 4.16 from Debian bullseye.
On one laptop, it works just fine (resolution 1600×900), but on the other laptop (1920×1080), the VNC display is completely screwed up. Check it out here, when I try to move a window: https://stuff.madduck.net/scratch/tigervnc-weirdness.gif
Note that this persists across different VNC clients, so I conclude it's a server-side problem.
Now, if I change the resolution to 1600×900 on that laptop, it works fine, and so at first I was thinking that TigerVNC just cannot handle the big resolution, but I noticed that LightDM displays just fine at 1920×1080, and so does a session with the AwesomeWM window manager.
Has anyone seen this before? What does Xfce on this laptop do to make TigerVNC not be able to properly work?
Thanks,
@martinkrafft | https://matrix.to/#/#madduck:madduck.net
"women, when they are not in love,
have all the cold blood of an experienced attorney."
-- honoré de balzac
spamtraps: madduc...@madduck.net
Pierre Ossman
>
> Has anyone seen this before? What does Xfce on this laptop do to make
> TigerVNC not be able to properly work?
>
https://github.com/TigerVNC/tigervnc/issues/1218
Could you check if glamor seems to be active on this device?
Regards
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
martin f krafft
Thanks for your response, Pierre!
Could you check if glamor seems to be active on this device?
Yes, the module is being loaded during Xorg start. I've tried to Disable it, but Load overrides Disable, and something explicitly loads it. So I renamed the module file itself, and consequently, glamoregl fails to load, and — tadaaa — the problem is gone.
Well spotted!
Now I am wondering what the best solution is. What do I need Glamor for?
Pierre Ossman
> Thanks for your response, Pierre!
>
>> Could you check if glamor seems to be active on this device?
>
> Yes, the module is being loaded during Xorg start. I've tried to
> `glamoregl` fails to load, and — tadaaa — the problem is gone.
>
> Well spotted!
>
> Now I am wondering what the best solution is. What do I need Glamor for?
>
want. Unfortunately we can't fix it in our end, and we aren't aware of
any workaround. So this needs to be reported to your distribution so
someone has a look at fixing the glamor code.
martin f krafft
Regarding the following, written by "Pierre Ossman" on 2021-08-27 at 15:42 Uhr +0200:
It handles all your hardware acceleration, so it's something you really want. Unfortunately we can't fix it in our end, and we aren't aware of any workaround. So this needs to be reported to your distribution so someone has a look at fixing the glamor code.
As far as I understand, the bug is already reported upstream, so there's little point in filing a bug against Debian stable, which has just been released.
Thanks for your help!
Pierre Ossman
>
> As far as I understand, the bug is already reported upstream, so there's
> little point in filing a bug against Debian stable, which has just been
> released.
>
> Thanks for your help!
>
prioritise a fix if they don't know that users are affected by it.