When I install winswitch on Centos 6.4, I get the following error. Installation went fine, no issues. (Windows version worked fine too, no issues.) I'm assuming it needs something similar to the following added:

        try:
            glib.threads_init()
        except AttributeError:
            #old versions of glib may not have this method
            pass
        try:
            gobject.threads_init()
        except AttributeError:
            #old versions of gobject may not have this method
            pass

Here is the actual error message I'm getting:

$ winswitch_server
[DD] 2013/13/03 16:34:58.449676 main_loop.loop_init(False)
Traceback (most recent call last):
  File "/usr/bin/winswitch_server", line 5, in <module>
    server_wrapper.main()
  File "/usr/lib/python2.6/site-packages/winswitch/server/server_wrapper.py", line 50, in main
    from winswitch.server.controller import WinSwitchServer
  File "/usr/lib/python2.6/site-packages/winswitch/server/controller.py", line 20, in <module>
    reactor = loop_init(False)
  File "/usr/lib/python2.6/site-packages/winswitch/util/main_loop.py", line 21, in loop_init
    glib.threads_init()
AttributeError: 'module' object has no attribute 'threads_init'

If you try to start an application on a Fedora 24 server using WindowSwitch? 0.12.21, you get the following error dialog:

You have requested an xpra session but this server does not support it.

Attempting to start an xpra session directly using: xpra start ssh:localhost:100 --start-child=xchat

actually produces an application.

xpra is installed in the same location that winswitch thinks it is.

For software installed from source, it is essential to be able to specify the installation directory tree (eg /usr/local) in order to avoid conflicts with OS installed software from packages.

And for those of us that manage installed local software with GNU stow,

(see ​https://www.gnu.org/software/stow if not familiar with the approach)

it is even more important that files get installed under the specified directory tree.

Now winswitch does this for most of the install if --prefix is used

/usr/bin/python "/usr/src/build/winswitch-0.12.23/setup.py" install --prefix="/usr/local/stow/Network/winswitch-0.12.23/usr/local"

creating /usr/local/stow/Network/winswitch-0.12.23/usr/local/lib/python2.7/site-packages/winswitch
creating /usr/local/stow/Network/winswitch-0.12.23/usr/local/lib/python2.7/site-packages/winswitch/ui
copying build/lib.linux-i686-2.7/winswitch/ui/window_fake_tray.py -> /usr/local/stow/Network/winswitch-0.12.23/usr/local/lib/python2.7/site-packages/winswitch/ui
...
byte-compiling /usr/local/stow/Network/winswitch-0.12.23/usr/local/lib/python2.7/site-packages/winswitch/ui/window_fake_tray.py to window_fake_tray.pyc
...

but for a number of items the install process ignores the prefix and installs directly under system directories /etc and /usr/lib

creating /etc/winswitch

and

creating /usr/lib/winswitch

For installs under "/usr/local" these should instead be accessible under /usr/local/etc/winswitch and /usr/local/lib/winswitch respectively when installation is complete.

Now after checking the setup.py file, it seems a non-standard (?) method of specifying the destination for installs works, by specifying the environmental variable PREFIX="prefix_dir" get the etc/winswich and lib/winswitch installed under the prefix dir BUT --prefix prefix_dir is still needed to get all the other items to the prefix directory.

Please ensure that the --prefix prefix_dir variable is applied to all items being installed without the need for adding the environmental variable, or at the very minimum, mention this double requirement in the README file.

Thank you for your assistance in resolving this issue.