Custom Query (230 matches)


Show under each result:

Results (178 - 180 of 230)

Ticket Resolution Summary Owner Reporter
#108 worksforme Can't start shifter_server in Debian Lenny: missing gio Antoine Martin R4v3n

Hi guys, I installed shifter from the debian lenny repository (v 0.9.19) on my Lenny. The application start, but I can't start the shifter_server because of the GIO module of python, because GIO is introduce in PyGTK 2.14, and Lenny run with the 2.12.

To be sure, I paste the error :

*** Caught exception: <type 'exceptions.ImportError'>: No module named gio
Traceback (most recent call last):
  File "/usr/lib/python2.5/shifter/server/", line 939, in main
  File "/usr/lib/python2.5/shifter/server/", line 216, in start
  File "/usr/lib/python2.5/shifter/server/", line 337, in start_menu_monitor
    import gio
ImportError: No module named gio
2010/30/06 16:24:51 ShifterController.stop_reactor() Can't stop reactor that isn't running.

So, is there a solution, or I need to upgrade to testing to use the winswitch_server ?

Thanks !

#205 notabug winswitch server restarts xpra session and adds --bind-tcp=<port> [was security risk..] Antoine Martin Optionator

starting an xpra session manually and then remotely connecting to it with the winswitch cleint for Windows results in change of xpra session to use --bind-tcp=<port>, which is a "major security risk" (xpra(1)).

Reproduction steps:

In the remote host run

$ ps aux | grep winswitch # no winswitch_server running
$ ps aux | grep xpra # no xpra running
$ xpra start :666
$ ps aux | grep xpra # see the command line and PID
1000     18905  2.5  0.2 188412 21976 ?        S    21:26   0:00 /usr/bin/python /usr/bin/xpra start :666

Now run the Window Switch client for Windows and connect to that remote host using ssh tunneling. It will show an "unknown" session. You won´t even need to resume it via the tray icon, the damage is already done:

On the remote host again:

$ ps aux | grep xpra
1000     19549  0.1  0.2 213020 23404 ?        S    21:32   0:00 /usr/bin/python /usr/bin/xpra --bind-tcp= --password-file=/home/ocm-admin/.winswitch/server/sessions/666/session.pass --no-daemon --no-pulseaudio --session-name=unknown start :666 --use-display

$ ps aux | grep winsw
1000     19479  0.1  0.1 101708 15536 ?        Ss   21:31   0:00 /usr/bin/python /usr/bin/winswitch_stdio_socket
1000     19485  0.2  0.0      0     0 ?        Z    21:32   0:00 [winswitch_serve] <defunct>
1000     19533  0.2  0.3 323548 29688 ?        S    21:32   0:00 /usr/bin/python /usr/bin/winswitch_server --daemon
1000     19549  0.1  0.2 213020 23404 ?        S    21:32   0:00 /usr/bin/python /usr/bin/xpra --bind-tcp= --password-file=/home/ocm-admin/.winswitch/server/sessions/666/session.pass --no-daemon --no-pulseaudio --session-name=unknown start :666 --use-display

$ netstat --inet -nlp 2>/dev/null | grep 19549
tcp        0      0 *               LISTEN      19549/python

So there you are, apparently winswitch_server restarted xpra, see the different PIDs, and now it is listening on all IPs. Found no documentation about this, just stumbled upon it. No obvious way to change it in any config files. Plus this should never be the default behaviour!

For some more info, I am using Debian squeeze/stable and have installed from the official repository.

$ cat /etc/debian_version
$ apt-cache policy winswitch xpra
  Installiert: 0.12.14-1
  Kandidat:    0.12.14-1
 *** 0.12.14-1 0
        990 squeeze/main amd64 Packages
        100 /var/lib/dpkg/status
  Installiert: 0.3.2-2
  Kandidat:    0.3.2-2
 *** 0.3.2-2 0
        990 squeeze/main amd64 Packages
        100 /var/lib/dpkg/status
$ winswitch_server --version
winswitch version 0.12.14
Release Build
Built on by root on the 2012-06-04
SVN revision unknown with unknown local modifications
$ xpra --version
xpra v0.3.2

I did not change any config files on the remote host.

The windows client version is: Window Switch 0.12.14 Built on xp-pro by XP_Pro. 2012-06-04 (release build) (svn revision 4908 with 0 local changes)

if the client version matters at all, this should clearly be changed on the server.

#231 invalid Debian: xpra v0.8.1 attempts to start Xvfb despite not depending on it Optionator

I am using your deb repository on a Debian 6.0.6 system and just upgraded xpra to v0.8.1. Xvfb got removed, because it was not depended on anymore. xserver-xorg-input-void and xserver-xorg-video-dummy were installed to fulfill dependencies.

Attempting to start xpra:

$ xpra start :999
cannot load vpx codec: /usr/lib/python2.6/dist-packages/xpra/vpx/ undefined symbol: vpx_codec_enc_config_default
No handlers could be found for logger "xpra.sound.gstreamer_util"
Entering daemon mode; any further errors will be reported to:
$ cat ~/.xpra/Squeezy-999.log
Error starting Xvfb: [Errno 2] No such file or directory
2013-02-05 14:00:13,957 removing socket /home/user/.xpra/Squeezy-999

I installed xvfb manually and now xpra works like it did before, but since the depencies changed, I believe, that´s not the intended behaviour.

Note: See TracQuery for help on using queries.