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 (61 - 63 of 2683)

Ticket Resolution Summary Owner Reporter
#64 worksforme xpra server dies on client's connection attempt Antoine Martin Yary
Description

I've just downloaded & built xpra on an OpenBSD system with Python 2.6

In one xterm, I run:

$ ''python install/bin/xpra start :13''
$ ''export DISPLAY=:13''
$ ''cat ~/.xpra/pinky.yary.ack.org-13.log''
Xlib:  extension "RANDR" missing on display ":13.0".
Xlib:  extension "RANDR" missing on display ":13.0".
Xlib:  extension "RANDR" missing on display ":13.0".
Randr not supported: X server does not support required extension Randr
randr enabled: False
failed to load dbus notifications forwarder: No module named dbus.service

xpra is ready.
 $ ''ps|grep -i xp''
21818 ??  S       0:00.60 /usr/local/bin/python install/bin/xpra start :13
31898 ??  S       0:01.09 Xvfb-for-Xpra-:13 +extension Composite -screen 0 3840
 $ ''xclock &''

In another xterm, I try to attach, hoping to see the xclock. $ ''install/bin/xpra attach :13''

cannot import pynotify wrapper (turning notifications off) : No module named dbus.glib
cannot import pynotify wrapper (turning notifications off) : No module named pynotify
'['setxkbmap', '-print']' failed with exit code 252
your keyboard mapping will probably be incorrect unless you are using a 'us' layout
'['setxkbmap', '-query']' failed with exit code 252
connection lost: Error writing to connection: [Errno 32] Broken pipe
Connection lost
 $ ''ps|grep -i xp''
31898 ??  S       0:01.24 Xvfb-for-Xpra-:13 +extension Composite -screen 0 3840

It appears that trying to attach is killing the xpra server (but not xvfb- perhaps that should be another ticket, Xvfb should go away if xpra does). There are some warnings but I don't know which are information vs fatal. Can you help me?

Thanks

#65 fixed error with jpeg encoding Antoine Martin Timo Juhani Lindfors
Description
Unhandled error while processing packet from peer
Traceback (most recent call last):
  File "python/xpra/protocol.py", line 238, in _process_packet
    self._process_packet_cb(self, decoded)
  File "python/xpra/client.py", line 1023, in process_packet
    self._packet_handlers[packet_type](self, packet)
  File "python/xpra/client.py", line 908, in _process_draw
    window.draw(x, y, width, height, coding, data)
  File "python/xpra/client.py", line 214, in draw
    self._backing.draw_rgb_image(gc, x, y, width, height, gtk.gdk.RGB_DITHER_NONE, data)
IndexError: rgb_buf is not large enough

when trying --encoding jpeg --jpeg-quality 60

#66 fixed "mdocml" cannot process xpra.1 Antoine Martin Yary
Description

Hi- I just got the latest revision of the xpra man page because the one I had was not readable by "mandoc", and the current xpra.1 has the same issue. Which is: xpra.1:368:2: FATAL: line scope broken, syntax violated Line 368 is .PP Just trying to get the different options to disable while debugging. I can use "groff" to get some human readable output, though it is a hard-to-read format.

Note: See TracQuery for help on using queries.