xpra icon
Bug tracker and wiki

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


Custom Query (2683 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (4 - 6 of 2683)

1 2 3 4 5 6 7 8 9 10 11 12
Ticket Resolution Summary Owner Reporter
#4 duplicate windows stay visible on the screen even if the server is killed Antoine Martin Timo Juhani Lindfors
Description

Currently if the server is killed the _to_server thread exits and closes both _client_conn and _server_conn. However, this does not cause the _to_client thread to stop. As a result an extra "xpra" process stays listed in the process list and users don't notice that the server has died. Only if you try to interactive with any of the windows will the proxy write something to the server socket and notice the problem.

This patch stops _to_client thread when _to_server thread exits and vice versa. Calling _Thread_stop() is bit ugly but the alternative would probably be to use some sort of polling mechanism instead of blocking read() in _copy_loop.

#5 fixed windows stay visible on the screen even if the server is killed Antoine Martin Timo Juhani Lindfors
Description

Currently if the server is killed the _to_server thread exits and closes both _client_conn and _server_conn. However, this does not cause the _to_client thread to stop. As a result an extra "xpra" process stays listed in the process list and users don't notice that the server has died. Only if you try to interactive with any of the windows will the proxy write something to the server socket and notice the problem.

This patch stops _to_client thread when _to_server thread exits and vice versa. Calling _Thread_stop() is bit ugly but the alternative would probably be to use some sort of polling mechanism instead of blocking read() in _copy_loop.

#6 worksforme Emacs Issues: xpra locks up, screen stops re-drawing Antoine Martin FredSRichardson
Description

I'm working with a recent version off the SVN repo (the date on the sources is 2011-08-02 19:36).

I've found two problems: one is occasional lockups and the other has to do with screen redrawing.

I'm not sure what causes the lockups, sometimes they are cured by minimizing and maximizing or by killing the xpra attach session and re-attaching.

The screen re-drawing is a consistent problem when scrolling through a lot of text. It looks as though emacs isn't keeping up with the redrawing somehow (a lot of "artifacts" are left in the buffer). This wasn't a problem in older versions of xpra, so I wonder if there's a setting that might help.

Here's output from the console:

$ xpra attach ssh:fdata1:14
'setxkbmap -query' failed with exit code 255
Missing window or missing property or wrong property type PULSE_SERVER (latin1)
Missing window or missing property or wrong property type PULSE_COOKIE (latin1)
Missing window or missing property or wrong property type PULSE_ID (latin1)
Attached (press Control-C to detach)
/usr/local/lib/python/xpra/xposix/xclipboard.py:227: GtkWarning: gdk_x11_atom_to_xatom_for_display: assertion `ATOM_TO_INDEX (atom) < virtual_atom_array->len' failed
  gtk.Invisible.do_selection_request_event(self, event)
1 2 3 4 5 6 7 8 9 10 11 12
Note: See TracQuery for help on using queries.