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 (22 - 24 of 2683)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Ticket Resolution Summary Owner Reporter
#1612 duplicate --dpi: client fails with "local variable 'xdpi' referenced before assignment" Antoine Martin mviereck
Description

system: debian stretch with winswitch stable repository bug in xpra 2.1, currently xpra v2.1-r16525 not a bug in 2.0.3

Hello! With option --dpi xpra 2.1 client fails with

error preparing connection: local variable 'xdpi' referenced before assignment
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/xpra/client/client_base.py", line 317, in send_hello
    hello.update(self.make_hello())
  File "/usr/lib/python2.7/dist-packages/xpra/client/gtk2/client.py", line 287, in make_hello
    capabilities = GTKXpraClient.make_hello(self)
  File "/usr/lib/python2.7/dist-packages/xpra/client/gtk_base/gtk_client_base.py", line 418, in make_hello
    capabilities = UIXpraClient.make_hello(self)
  File "/usr/lib/python2.7/dist-packages/xpra/client/ui_client_base.py", line 1424, in make_hello
    self._last_screen_settings = (root_w, root_h, sss, ndesktops, desktop_names, u_root_w, u_root_h, xdpi, ydpi)
UnboundLocalError: local variable 'xdpi' referenced before assignment

I provide --dpi to server and client, if that matters. The server starts up fine, the client crashes with above message. (I did not test providing --dpi to only one of server or client.) The error does not happen in xpra 2.0.3.

#1810 invalid --exit-with-children broken Cigaes Cigaes
Description

The --exit-with-children option seems to be currently broken:

$ xpra --start-child=xterm --exit-with-children start ssh:aimlin:11   
2018-04-16 17:52:40,463 Xpra gtk2 client version 2.2.6-r19015 64-bit
2018-04-16 17:52:40,463  running on Linux Debian stable-updates sid
2018-04-16 17:52:42,138 GStreamer version 1.14.0 for Python 2.7.14 64-bit
2018-04-16 17:52:42,454 No OpenGL_accelerate module loaded: No module named OpenGL_accelerate
2018-04-16 17:52:42,620 OpenGL enabled with Mesa DRI Intel(R) Haswell
2018-04-16 17:52:42,630 failed to instantiate the dbus notification handler:
2018-04-16 17:52:42,630  you may need to start a notification service for 'org.freedesktop.Notifications'
2018-04-16 17:52:42,630  disable notifications to avoid this warning
2018-04-16 17:52:42,647  keyboard settings: rules=evdev, model=pc105, layout=fr
2018-04-16 17:52:42,648  desktop size is 1920x1080 with 1 screen:
2018-04-16 17:52:42,648   :0.0 (508x285 mm - DPI: 96x96) workarea: 1920x1020 at 0x60
2018-04-16 17:52:42,648     monitor 1 (480x270 mm - DPI: 101x101)
2018-04-16 17:52:43,250 Error: cannot watch for video device changes without pyinotify:
2018-04-16 17:52:43,250  No module named pyinotify
2018-04-16 17:52:44,249 xpra initialization error:
2018-04-16 17:52:44,249  --exit-with-children option does not take a value
2018-04-16 17:52:44,250 Error: printing disabled:
2018-04-16 17:52:44,250  No module named cups
2018-04-16 17:52:44,257 Connection lost

Notice I did not give a value to the option. The command succeeds if I remove the option entirely.

#1382 fixed --exit-with-children race condition (vs. --start-child) Alex Alex
Description

Hi,

the call 'xpra start --start-child="xterm -ls" --exit-with-children' works well with 0.17.3, but not with 1.0-x if the startup of the child is not fast enough. However, starting a session without '--exit-with-children' is successful.

It seems to be a race condition: xpra starts -> X11 starts -> xpra starts child -> xpra checks for running children -> child is up -> xpra terminates X11 -> xpra terminates itself.

In the log (e.g. /run/usr/$UID/xpra/:1.log) it looks like:

...
X.Org X Server 1.17.2
...
Using display number provided by xpra_Xdummy: :1
2016-12-16 17:22:59,084 created unix domain socket: /var/run/user/${UID}/xpra/${HOSTNAME}-1
2016-12-16 17:22:59,086 created unix domain socket: /home/${USER}/.xpra/${HOSTNAME}-1
...
2016-12-16 17:23:02,412 all children have exited and --exit-with-children was specified, exiting
2016-12-16 17:23:02,415 D-Bus notification forwarding is available
2016-12-16 17:23:02,422 started command 'xterm -ls' with pid 27233
2016-12-16 17:23:02,422 xpra X11 version 1.0-r14532 64-bit
2016-12-16 17:23:02,422  uid=...
2016-12-16 17:23:02,422  running with pid 26888 on Linux CentOS 7.3.1611 Core
2016-12-16 17:23:02,422  connected to X11 display :1
2016-12-16 17:23:02,445 stopping pulseaudio with pid 27046
xterm: cannot load font '-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1'
2016-12-16 17:23:02,464 xpra is ready.
2016-12-16 17:23:02,550 printer forwarding enabled using postscript and pdf
2016-12-16 17:23:02,550 62.7GB of system memory
2016-12-16 17:23:02,961 xpra is terminating.
2016-12-16 17:23:02,962 killing xvfb with pid 26889
2016-12-16 17:23:02,962 removing socket /var/run/user/${UID}/xpra/${HOSTNAME}-1
2016-12-16 17:23:02,962 removing socket /home/${USER}/.xpra/${HOSTNAME}-1
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
      after 74 requests (74 known processed) with 12 events remaining.
(II) Server terminated successfully (0). Closing log file.

MWE:

  • xpra v1.0-r14535 (on openSuse 13.1) or v1.0-r14532 (on CentOS 7.3)
  • call: 'xpra start --start-child="xterm -ls" --exit-with-children'
  • wait ~5s
  • call: 'xpra list'
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Note: See TracQuery for help on using queries.