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 (94 - 96 of 2683)

Ticket Resolution Summary Owner Reporter
#126 fixed Certain keypresses in SAS which ring the bell cause xpra client to crash Antoine Martin alis
Description

While running the Linux SAS 9.2 GUI application in xpra (Linux xpra server and Linux xpra client), most things work fine. However, certain keypresses which the application considers "invalid," such as pressing the up arrow when already at the top of a text area, cause the xpra client to crash and disconnect. The application continues running in the server and can be re-attached to without any problems, until another "invalid" keystroke crashes the xpra client again.

The problem appears to occur when the application attempts to ring the bell in response to the invalid keypress. The error given is: 'XI_BadDevice (invalid Device parameter)'. (Details: serial 214105 error_code 160 request_code 147 minor_code 3)

When run with --debug=all, the relevant portions seem to be (full log attached):

~> xpra --debug=all attach ssh:pt-sas06:100
set default window icon to /usr/bin/../share/xpra/icons/xpra.png
bell_toggled((<gtk.CheckMenuItem object at 0xd6ebe0 (GtkCheckMenuItem at 0xa750d0)>,)) bell_enabled=True
cursors_toggled((<gtk.CheckMenuItem object at 0xd6ec80 (GtkCheckMenuItem at 0xa75190)>,)) cursors_enabled=True

[...]

handle_key_action(<gtk.gdk.Event at 0x10119e0: GDK_KEY_PRESS keyval=Up>,<ClientWindow object at 0x10d81e0 (xpra+client+ClientWindow at 0xf8a610)>,True)
key_action(<gtk.gdk.Event at 0x10119e0: GDK_KEY_PRESS keyval=Up>,<ClientWindow object at 0x10d81e0 (xpra+client+ClientWindow at 0xf8a610)>,True) modifiers=['mod2'], name=Up, state=<flags GDK_MOD2_MASK of type GdkModifierType>, keyval=65362, string=, keycode=111
scheduling key repeat for Up: delay=400, interval=5 (from 500 and 28)
key repeat: starting timer for Up / 111 with delay 400 and interval 5
read thread: got data 'Bm\x14\x1b\x9b\x01\xd3zRjNN&h\xf7\x120\xa5\x83k\\\x10\x1bD\x80\x91\x81U*\x00\x00\x00\xff\xff'
_process_bell(['bell', 0, 1, 50, 400, 100, 0, 0, '']) gdkwindow=<gtk.gdk.Window object at 0x10c7c30 (GdkWindow at 0xa78120)>
The program 'xpra' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadDevice (invalid Device parameter)'.
  (Details: serial 1388 error_code 160 request_code 147 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
#127 fixed CFLAGS changes Antoine Martin Antoine Martin
Description

CFLAGS have been changed to use O2 in r866

This ticket is here to record this change, and back it up with (marginal) performance numbers.

#128 fixed SyntaxError: Non-ASCII character Antoine Martin Norman Rasmussen
Description
SyntaxError: Non-ASCII character '\xc2' in file xpra/server.py on line 2208, but no encoding declared;}}}
see [http://www.python.org/peps/pep-0263.html pep 0263] for details

This was introduced in Changeset 780.  server.py needs to have a header added (like {{{xpra/platform/client_extras_base.py}}} has), or the µs should be escaped.
Note: See TracQuery for help on using queries.