Xpra: Ticket #642: all blank windows for a particular session on reboot/win-switch restore

session restore:

reboot windows, win-switch comes up, restores sessions, xpra icon stuck at "1 clipboard request in progress", windows all recreated, but one session's windows are all black and not communicating.

Once this happens, sending it to another PC (like the server) does not seem to work at all, nor does attempting to restore it from the original client.



Tue, 19 Aug 2014 15:39:55 GMT - Eric Blade: attachment set

zip from xpra client bug report


Tue, 19 Aug 2014 15:51:59 GMT - Eric Blade:

difficulty: I don't see any relevant server logs. My last log in ~/.xpra was updated on Aug 6th, so I'm going to clear my .xpra and .winswitch dirs on both sides, and reboot, and hope for the best. :-)

I don't think this problem occurred when I was running 0.13.7 on server, and 0.14.0 on client for a few days, but i also think the clipboard communication was broken with that combination .. i'm not entirely certain though that the "1 clipboard request in progress" is relevant or just a red herring.


Tue, 19 Aug 2014 15:59:32 GMT - Eric Blade:

It might be possible this may have something to do with a little app that I use called "msjnc", I'm not certain if this window was in all of the sessions that have not properly resumed.. but it may have been, because I usually have it running all the time, so it's really nice to have it in an xpra session so that it will always be running ..

http://mad-scientist.us/juniper.html


Wed, 20 Aug 2014 10:37:20 GMT - Antoine Martin: owner changed

Without clear steps for me to reproduce this, it is very very hard for me to do anything about this.


Wed, 20 Aug 2014 21:05:33 GMT - Eric Blade:

@antoine .. sadly, the only steps that i have are "reboot my pc", winswitch starts up automatically, attempts to restore all open sessions on the server, and sometimes i end up with a session where everything is blank and nothing works.


Thu, 21 Aug 2014 01:11:24 GMT - Antoine Martin:

Next time it occurs, please capture the xpra info for that session or better: use the bug report tool from the system tray.


Thu, 21 Aug 2014 04:15:09 GMT - Eric Blade:

bug report zip is attached already :-)


Thu, 21 Aug 2014 04:18:33 GMT - Antoine Martin:

Ooops, my bad - sorry!

I don't see the server info in there, so either you ran the tool separately from the session instead of from the xpra tray, or somehow there was a problem with the server (bug or other). Can you tell us which? Obviously, that's the one we really want!

Since the clipboard thing is suspicious, maybe you can disable clipboard support (easiest thing would be on the server), and see if that fixes things? (at least to try to identify the problem - I know the clipboard is very useful to have..)


Thu, 21 Aug 2014 10:04:23 GMT - Eric Blade:

I ran the bug report from the tray on the Windows client. It hasn't cropped up since I filed the bug, but I've only put the machine to sleep once since then.

I wonder if it might be possible that it's some kind of interaction between Synergy+'s clipboard activity and Xpra's? I pretty much run Win-Switch/Xpra? and Synergy+ on everything I've got these days, on autostart, since I work from multiple locations with multiple laptops and desktops.

I guess I need to have a look at the config files and see what can be played with in there .. maybe tomorrow i can sleep/shutdown several times in a row and see if that makes it any easier to repro.


Thu, 21 Aug 2014 10:22:53 GMT - Antoine Martin:

That's odd, when launching from the tray it should have included the server info.

It is definitely something clipboard related if you use synergy+ and you see that message. Both xpra and synergy+ will compete for synchronizing the clipboard and it will all end in tears.

Not sure what can be done from our end or from synergy for that matter. You just can't synchronize from all of them at once.


Fri, 29 Aug 2014 19:23:00 GMT - Eric Blade:

Something that I've noticed, is that it only seems to happen for sessions that include at least one terminal window (using gnome-terminal) .. i've been running seperate chromium-browser and pidgin sessions for several days without a hiccup in it, but i frequently get locked up when trying to sync with a session that has gnome-terminals, always having the "1 clipboard request in progress". Still needs more analysis on my part, I think, to put together some sort of sane explanation. When I get back to my home office this week, I'll be disabling synergy on both sides for a while, and see if it still happens.


Thu, 04 Sep 2014 18:52:04 GMT - Eric Blade:

@totaam:

Ran into this on a machine that doesn't have Synergy on. Bug report tool says "Server Info (not available)". Attaching new zip.


Thu, 04 Sep 2014 18:52:52 GMT - Eric Blade: attachment set


Fri, 05 Sep 2014 02:34:22 GMT - Antoine Martin:

Without synergy... OK, so that's not the cause. Maybe the "clipboard in progress" is a red herring.

The most important bit of debug information is the "Server Info", the fact that it is missing does tell us something. My guess is that the server connection is dead. Can you attach the server log file (use ps to locate it and its log file).


Sun, 07 Sep 2014 18:55:35 GMT - Eric Blade: attachment set


Sun, 07 Sep 2014 19:37:11 GMT - Eric Blade:

ok, got it immediately on starting a terminal window today. bug report zip is attached as xprastuck.zip, zip of the server's ~/.winswitch/server/sessions/68 is included inside it. nothing located in ~/.xpra about it.

Once it happens, the winswitch buttons for disconnect, stop, and then resume, re-connect, seem to do absolutely nothing.


Fri, 13 Feb 2015 06:26:35 GMT - Antoine Martin:

I don't see the xpra info in that zip file, which is odd. Maybe the server is deadlocked? Does it eventually disconnect with a timeout?

Do you have sound enabled? See #669. If so, try turning that off. ie:

speaker=no

in /etc/xpra/xpra.conf.


Tue, 14 Apr 2015 15:53:31 GMT - Antoine Martin: status changed; resolution set

Not heard back. Closing.


Sat, 23 Jan 2021 05:01:43 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/642