xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.


Changes between Initial Version and Version 1 of Ticket #2607, comment 15


Ignore:
Timestamp:
03/07/20 04:21:48 (19 months ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2607, comment 15

    initial v1  
    1 Replying to [comment:12 Antoine Martin]:
    2 > > > One thing you can try is to run the '''client''' with {{{XPRA_SAVE_CURSORS=1 xpra attach ...}}}.
    3 > > > This will save cursors as PNG images using the filename {{{cursor-$SERIAL.png}}} (so the same serial may overwrite the cursor file - though they should be identical in that case?)
    4 > > >
    5 > > > Another thing which may affect the cursors is scaling:
    6 > > > {{{
    7 > > > make_cursor: has-name=True, has-cursor-types=True, xscale=1.25, yscale=1.25, USE_LOCAL_CURSORS=True
    8 > > > }}}
    9 > > > Can you reproduce the problem with scaling disabled?
    10 > >
    11 > > Scaling? What scaling? I didn't activate such thing.
    12 > It is activated automatically because your client display is so large.
    13 > > For some reason, connections from/to Xenial server have this message:
    14 > >
    15 > > {{{
    16 > > 2020-03-06 10:18:38,790 Warning: Invalid Scale Factor
    17 > > 2020-03-06 10:18:38,791  cannot scale by 100% x 100% or lower
    18 > > 2020-03-06 10:18:38,792  the scaled client screen 6400 x 1440 -> 6400 x 1440
    19 > > 2020-03-06 10:18:38,792   would overflow the server's screen: 5760 x 2560
    20 > > }}}
    21 > >
    221> > but not when I connect from the Windows 10 client to the Xenial server. I don't understand why you pick such a big display (6400 x 1440), and why do you need to scale it down (5760 x 2560) since the screen size is an "imaginary" screen size (seamless i.e. only the windows are drawn)
    232> The server's virtual screen must be configured to match the client's display area.