xpra icon
Bug tracker and wiki

Opened 5 weeks ago

Closed 5 weeks ago

Last modified 5 weeks ago

#2151 closed defect (fixed)

xpra initialization error: display is not set!

Reported by: stdedos Owned by: Antoine Martin
Priority: major Milestone: 2.5
Component: server Version: 2.4.x
Keywords: Cc:

Description

On

$ lsb_release -rd
Description:	Ubuntu 16.04.5 LTS
Release:	16.04

I tried to (locally) start an xpra shadow, and I get:

$ cat /run/user/1000/xpra/:0.log
2019-02-15 17:45:57,653 created unix domain socket: /run/user/1000/xpra/sntentos-precision-t3620-0
2019-02-15 17:45:57,653 created unix domain socket: /run/xpra/sntentos-precision-t3620-0
2019-02-15 17:45:57,657 removing socket /run/user/1000/xpra/sntentos-precision-t3620-0
2019-02-15 17:45:57,657 removing socket /run/xpra/sntentos-precision-t3620-0
xpra initialization error:
 display is not set!
  File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 85, in main
    return run_mode(script_file, err, options, args, mode, defaults)
  File "/usr/lib/python2.7/dist-packages/xpra/scripts/main.py", line 403, in run_mode
    return run_server(error_cb, options, mode, script_file, args, current_display)
  File "/usr/lib/python2.7/dist-packages/xpra/scripts/server.py", line 553, in run_server
    return do_run_server(error_cb, opts, mode, xpra_file, extra_args, desktop_display)
  File "/usr/lib/python2.7/dist-packages/xpra/scripts/server.py", line 1016, in do_run_server
    app = make_shadow_server()
  File "/usr/lib/python2.7/dist-packages/xpra/scripts/server.py", line 388, in make_shadow_server
    from xpra.platform.shadow_server import ShadowServer
  File "/usr/lib/python2.7/dist-packages/xpra/platform/shadow_server.py", line 9, in <module>
    platform_import(globals(), "shadow_server", True, "ShadowServer")
  File "/usr/lib/python2.7/dist-packages/xpra/platform/__init__.py", line 154, in platform_import
    platform_module = __import__(module, {}, {}, imports)
  File "/usr/lib/python2.7/dist-packages/xpra/platform/xposix/shadow_server.py", line 7, in <module>
    from xpra.x11.shadow_x11_server import ShadowX11Server
  File "/usr/lib/python2.7/dist-packages/xpra/x11/shadow_x11_server.py", line 9, in <module>
    from xpra.x11.x11_server_core import X11ServerCore
  File "/usr/lib/python2.7/dist-packages/xpra/x11/x11_server_core.py", line 18, in <module>
    from xpra.server.server_uuid import save_uuid, get_uuid
  File "/usr/lib/python2.7/dist-packages/xpra/server/server_uuid.py", line 7, in <module>
    from xpra.x11.gtk_x11.prop import prop_set, prop_get
  File "/usr/lib/python2.7/dist-packages/xpra/x11/gtk_x11/prop.py", line 19, in <module>
    from xpra.x11.prop_conv import prop_encode, prop_decode, unsupported, PROP_TYPES
  File "/usr/lib/python2.7/dist-packages/xpra/x11/prop_conv.py", line 23, in <module>
    X11Window = X11WindowBindings()
  File "xpra/x11/bindings/window_bindings.pyx", line 406, in xpra.x11.bindings.window_bindings.X11WindowBindings
  File "xpra/x11/bindings/core_bindings.pyx", line 85, in xpra.x11.bindings.core_bindings._X11CoreBindings.__cinit__

I even tried to install a previous version (2.5-20181021r20740-1) or

sudo apt-get install --reinstall -o Dpkg::Options::="--force-confask,confnew,confmiss" xpra=2.5-20181021r20740-1
sudo apt-get install --reinstall -o Dpkg::Options::="--force-confask,confnew,confmiss" xpra

If I do it the client (Win10), it waits until timeout, with no output what-so-ever

Change History (5)

comment:1 Changed 5 weeks ago by Antoine Martin

Resolution: fixed
Status: newclosed

Thanks for the report, this is already fixed in r21640. (was broken since r21627)
I assume you're running a version between those two revisions.

New beta builds will be posted in the next couple of days.

comment:2 in reply to:  1 Changed 5 weeks ago by stdedos

Replying to Antoine Martin:

Thanks for the report, this is already fixed in r21640. (was broken since r21627)
I assume you're running a version between those two revisions.

I am not sure why this would affect me since, in the end, I tried to downgrade (and fully reset the package) with:

sudo apt-get install --reinstall -o Dpkg::Options::="--force-confask,confnew,confmiss" xpra=2.5-20181021r20740-1

Anyway, I hope that it has been / will be fixed :/

It is also annoying that I cannot "just" write xpra --version to get the xpra version, and instead I depend on dpkg -l xpra shenanigans to figure out if I have downgraded or not :/

comment:3 Changed 5 weeks ago by Antoine Martin

It is also annoying that I cannot "just" write xpra --version to get the xpra version, and instead I depend on dpkg -l xpra shenanigans to figure out if I have downgraded or not :/

Why is that? xpra --version should work and show you the full version number? Does it not?

comment:4 in reply to:  3 Changed 5 weeks ago by stdedos

Replying to Antoine Martin:

It is also annoying that I cannot "just" write xpra --version to get the xpra version, and instead I depend on dpkg -l xpra shenanigans to figure out if I have downgraded or not :/

Why is that? xpra --version should work and show you the full version number? Does it not?

It does ... sort of.

I just think it's weird that regardless of the xpra package state:

sudo apt-get install --reinstall -o Dpkg::Options::="--force-confask,confnew,confmiss" xpra=2.5-20181021r20740-1
sudo apt-get install --reinstall -o Dpkg::Options::="--force-confask,confnew,confmiss" xpra # now at 2.5-20190212r21639-1

xpra --version is saying v2.5-r21639 at both states.

I know that there is this "magic package" xpra that pulls python2-xpra (and then there is python3-xpra), but I don't understand "how they work together".
Is it possible they are independant packages, and changing one does not affect another?
I could understand the reasoning for having separate packages, but do I need to manually change "everything" when trying to downgrade?

comment:5 Changed 5 weeks ago by Antoine Martin

xpra --version is saying v2.5-r21639 at both states.

AFAICT, you're only changing the version of the metapackage, not the actual sub-packages. See:

dpkg --list | grep xpra
  • xpra-common is shared between the python2 and python3 builds
  • python2-xpra is probably what you wanted to downgrade

The version shown with xpra --version should always match the package version - bar any very minor version differences (ie: the packaging files are also stored in svn, changes to those may not be reflected in the xpra --version as that's only for the xpra source)

Note: See TracTickets for help on using tickets.