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 (52 - 54 of 2683)

Ticket Resolution Summary Owner Reporter
#71 fixed X Error when starting DDT debugger Antoine Martin angelv
Description

Hi,

I'm trying to run DDT under xpra, but I get the following error:

$ DISPLAY=:100 /home/angelv/ddt/bin/ddt
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  42 (X_SetInputFocus)
  Serial number of failed request:  22
  Current serial number in output stream:  24
$ 

This is in a Ubuntu 11.04 (x86_64) box, running xpra v0.0.7.33. I include below the xpra log, in case it can shed some light into the issue.

Thanks a lot, Ángel de Vicente

========================
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi/:unscaled, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/100dpi, removing from list!
[dix] Could not init font path element /usr/share/fonts/X11/75dpi, removing from list!
Xlib:  extension "RANDR" missing on display ":100".
Xlib:  extension "RANDR" missing on display ":100".
Xlib:  extension "RANDR" missing on display ":100".
Randr not supported: X server does not support required extension Randr
randr enabled: False
using notification forwarder

xpra is ready.
New connection received
Handshake complete; enabling connection
encoding set to rgb24, client supports ['rgb24', 'jpeg', 'png'], server supports ['rgb24', 'jpeg', 'png']
using client supplied mmap file=/tmp/xpra.5wk28s.mmap, size=134217728
client resolution is [2560, 1024], current server resolution is 3840x2560
setting key repeat rate from client: 500 / 33
['setxkbmap', '-rules', 'evdev', '-model', 'dellsk8125', '-layout', 'es']
['xkbcomp', '-', ':100'] with stdin=xkb_keymap {\n      xkb_keycodes  { ..
set_keycodes: no free keycodes!, cannot translate 231: [[65385, 'Cancel', 231, 0, 0]]
set_keycodes: no free keycodes!, cannot translate 233: [[269025026, 'XF86MonBrightnessUp', 233, 0, 0]]
set_keycodes: no free keycodes!, cannot translate 235: [[269025113, 'XF86Display', 235, 0, 0]]
set_keycodes: no free keycodes!, cannot translate 237: [[269025030, 'XF86KbdBrightnessDown', 237, 0, 0]]
/usr/lib/python2.7/dist-packages/wimpiggy/prop.py:165: GtkWarning: /build/buildd/gtk+2.0-2.24.4/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 8388609
  return str(get_pyatom(disp, struct.unpack("@I", d)[0]))
/usr/lib/python2.7/dist-packages/wimpiggy/prop.py:165: GtkWarning: /build/buildd/gtk+2.0-2.24.4/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 2047
  return str(get_pyatom(disp, struct.unpack("@I", d)[0]))
/usr/lib/python2.7/dist-packages/wimpiggy/prop.py:165: GtkWarning: /build/buildd/gtk+2.0-2.24.4/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 4157174968
  return str(get_pyatom(disp, struct.unpack("@I", d)[0]))
/usr/lib/python2.7/dist-packages/wimpiggy/prop.py:165: GtkWarning: /build/buildd/gtk+2.0-2.24.4/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 4180777408
  return str(get_pyatom(disp, struct.unpack("@I", d)[0]))
Unhandled error while processing packet from peer
Traceback (most recent call last):
  File "/usr/lib/xpra/xpra/protocol.py", line 286, in _process_packet
    self._process_packet_cb(self, decoded)
  File "/usr/lib/xpra/xpra/server.py", line 1838, in process_packet
    self._packet_handlers[packet_type](self, proto, packet)
  File "/usr/lib/xpra/xpra/server.py", line 1530, in _process_map_window
    window = self._id_to_window[id]
KeyError: 2
#72 fixed no keys with modifiers accepted anymore Antoine Martin pmarek
Description

I've had it now 3 times that no keys with modifiers are accepted anymore; ie. I can enter "abc", but no character like "!" (shift+1), "«" (AltGr+x), etc. These are simply not taken (xchat text input line).

I've now had that while running xpra with "-d all"; here's the (hopefully) relevant part of the log. I hope that this client log is enough.

I've marked a few lines with "==========" to explain the approximate state; perhaps having a timestamp every so often would be a good idea, too.

#73 fixed Error message when DNS goes wrong Antoine Martin pmarek
Description

If I try to connect too soon, ie. when DNS is not working (resolv.conf not done, etc.), I get this error:

$ xpra attach ssh:host:65
ssh: Could not resolve hostname host: Name or service not known
using dbusnotify: <class 'dbus.proxies.Interface'>(org.freedesktop.Notifications)
Exception in thread write_loop:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 505, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/xpra/xpra/protocol.py", line 171, in _write_thread_loop
    written = untilConcludes(self._conn.write, buf)
  File "/usr/lib/xpra/xpra/protocol.py", line 69, in untilConcludes
    return f(*a, **kw)
  File "/usr/lib/xpra/xpra/protocol.py", line 38, in write
    return os.write(self._writeable.fileno(), buf)
ValueError: I/O operation on closed file

connection lost: empty marker in read queue
Connection lost

Xpra 0.0.7.34, svn revision 453 with 0 local changes

Note: See TracQuery for help on using queries.