Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#108 closed defect (worksforme)

Can't start shifter_server in Debian Lenny: missing gio

Reported by: R4v3n Owned by: Antoine Martin
Priority: critical Milestone: 0.10
Component: Server Keywords:
Cc:

Description (last modified by Antoine Martin)

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/controller.py", line 939, in main
    server.start()
  File "/usr/lib/python2.5/shifter/server/controller.py", line 216, in start
    self.start_menu_monitor()
  File "/usr/lib/python2.5/shifter/server/controller.py", 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 !

Change History (3)

comment:1 Changed 9 years ago by Antoine Martin

Owner: changed from Antoine Martin to Antoine Martin
Status: newaccepted

Hmm, will need to fallback to a polling timer when gio is missing.

In the meantime, you could just try to remove the call to start_menu_monitor, although I expect something else to break further down (in shifter/virt/*)...

comment:2 Changed 9 years ago by Antoine Martin

Resolution: worksforme
Status: acceptedclosed
Summary: Can't start shifter_server in Debian LennyCan't start shifter_server in Debian Lenny: missing gio

added ability to run without gio: r2790

Can be tested by running client or server with "--disable-gio"

Caveats:

  • disables session prelaunch: "without gio, we would eat up too much CPU polling preloaded session files"
  • delayed_start.py uses a 1-second polling loop... which could cause problems (high cpu usage, etc...) - should replace this with a signal handler (SIGUSR1?) so the server can ping it when it has updated the session file

To test it, you must use svn head until I make a beta release of 0.10.0

Last edited 8 years ago by Antoine Martin (previous) (diff)

comment:3 Changed 8 years ago by Antoine Martin

Description: modified (diff)
Note: See TracTickets for help on using tickets.