[winswitch] xpra coordinate mapping error with dual screen

Antoine Martin antoine at nagafix.co.uk
Wed Jun 5 05:35:52 BST 2013


On 06/05/2013 08:23 AM, Martin Ebourne wrote:
> On Tue, 2013-06-04 at 22:01 +0700, Antoine Martin wrote:
>> Please post your server log.
>> It sounds like your vfb is using the wrong dimensions or that the
>> windows are mapped in the wrong place.
>> The first one should show up in the standard server log, for the second
>> one you will need to run the server in debug mode (-d all).
>>
>> This could be related to this bug:
>> http://xpra.org/trac/ticket/349
>>
> 
> Yes it happened today exactly when I plugged in the external monitor to
> my laptop, thus increasing the screen dimensions. Yesterdays probably
> also coincided with that though it must have taken a while to notice as
> I didn't associate the events whereas today it was obvious. I'm not sure
> about the couple of times in previous weeks.
> 
> As I said before, there is nothing in my log from when I plugged the
> screen in about resolution changes, but it is correctly negotiated when
> I reconnect.
Can you please try this change:
http://xpra.org/trac/changeset/3581/xpra
from:
http://xpra.org/trac/ticket/349#comment:2

If that fixes it I will backport to v0.9.x

Thanks
Antoine

> 
> Here's the excerpt, the problem occurred a couple of minutes before
> 01:16 when I reconnected, there is nothing in the log at this time.
> 
> 2013-06-05 00:55:32,114 New connection received: SocketConnection(/home/USERNAME/.xpra/HOSTNAME-101)
> 2013-06-05 00:55:32,132 Handshake complete; enabling connection
> 2013-06-05 00:55:32,134 Python/Gtk2 Linux client version 0.9.4 connected from 'CLIENTNAME'
> 2013-06-05 00:55:32,134 using png as primary encoding
> 2013-06-05 00:55:32,134 max client resolution is 1920x1080 (from [[1920, 1080]]), current server resolution is 4800x1200
> 2013-06-05 00:55:32,152 new resolution matching 1920x1080 : screen now set to 1920x1080
> 2013-06-05 00:55:32,156 setting key repeat rate from client: 500ms delay / 30ms interval
> 2013-06-05 00:55:32,162 setting keymap: rules=evdev, model=evdev, layout=us,us
> 2013-06-05 00:55:32,498 setting full keymap definition from client via xkbcomp
> 2013-06-05 00:55:32,784 sending updated screen size to clients: 1920x1080 (max 5120x3200)
> 2013-06-05 00:55:32,895 using sound codec opus
> 2013-06-05 00:55:33,173 starting sound using pulseaudio device null.monitor
> 2013-06-05 00:55:33,245 unknown tag message: <gst.Message taglist, source-pad=(GstPad)"\(GstPad\)\ src"; from opusenc8 at 0xa6101f60>
> 2013-06-05 00:55:33,246 pipeline warning: Internal data flow problem.
> 2013-06-05 00:55:33,246 pipeline warning: ['gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstPipeline:pipeline8/GstAppSink:sink:\nReceived buffer without a new-segment. Assuming timestamps start from 0.']
> 2013-06-05 01:16:49,395 read connection reset for SocketConnection(/home/USERNAME/.xpra/HOSTNAME-101)
> 2013-06-05 01:16:49,447 connection lost: read connection reset: [Errno 104] Connection reset by peer
> 2013-06-05 01:16:49,448 connection closed after 34968 packets received (1049376 bytes) and 78932 packets sent (249723961 bytes)
> 2013-06-05 01:16:49,449 Connection lost
> 2013-06-05 01:16:49,455 xpra client disconnected.
> 2013-06-05 01:16:57,592 New connection received: SocketConnection(/home/USERNAME/.xpra/HOSTNAME-101)
> 2013-06-05 01:16:57,617 Handshake complete; enabling connection
> 2013-06-05 01:16:57,763 Python/Gtk2 Linux client version 0.9.4 connected from 'CLIENTNAME'
> 2013-06-05 01:16:57,763 using png as primary encoding
> 2013-06-05 01:16:57,763 max client resolution is 3840x1080 (from [[3840, 1080]]), current server resolution is 1920x1080
> 2013-06-05 01:16:57,948 new resolution matching 3840x1080 : screen now set to 4800x1200
> 
> Cheers,
> Martin
> 
> _______________________________________________
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
> http://lists.devloop.org.uk/mailman/listinfo/shifter-users
> 




More information about the shifter-users mailing list