ltsp-manager crashes

Bug #73560 reported by Fridtjof Busse
56
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ltsp-manager (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: ltsp-manager

On Edgy, the ltsp-manager crashes immediatly:
$ ltsp-manager

(ltsp-manager:8676): libglade-WARNING **: could not find glade file './ltsp-manager.glade'
Traceback (most recent call last):
  File "/usr/bin/ltsp-manager", line 409, in ?
    base = LTSPManager()
  File "/usr/bin/ltsp-manager", line 18, in __init__
    self.wTree=gtk.glade.XML ("./ltsp-manager.glade")
RuntimeError: could not create GladeXML object

Revision history for this message
yanu (yanu) wrote :

  in file /usr/bin/ltsp-manager change line 18
      self.wTree=gtk.glade.XML ("./ltsp-manager.glade")
  to
      self.wTree=gtk.glade.XML ("/usr/share/ltsp-manager/ltsp-manager.glade")

Changed in ltsp-manager:
assignee: nobody → gepatino
status: Unconfirmed → In Progress
Revision history for this message
Gabriel Patiño (gepatino) wrote :

I'm uploading the patch with the solution proposed by yanu.

This patch has been made using ltsp-manager-0.0.1 (edgy package).

Bug #85950, marked as duplicate to this, reports the same problem but in ltsp-manager-0.0.2 (maybe a feisty package?) so this patch could also apply to that version.

Changed in ltsp-manager:
assignee: gepatino → nobody
status: In Progress → Confirmed
Changed in ltsp-manager:
importance: Undecided → Medium
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Has this fix made it into feisty?

Revision history for this message
santiago (santiagozky) wrote :

I dont think so, Im using feisty and have the same problem. changing /usr/bin/ltsp-manager gave me this:

/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
Traceback (most recent call last):
  File "/usr/bin/ltsp-manager", line 254, in <module>
    base = LTSPManager()
  File "/usr/bin/ltsp-manager", line 33, in __init__
    self.fulfill_prereq()
  File "/usr/bin/ltsp-manager", line 56, in fulfill_prereq
    pathlist = self.get_root_path()
  File "/usr/bin/ltsp-manager", line 102, in get_root_path
    pathlist = os.listdir('/opt/ltsp/')
OSError: [Errno 2] No such file or directory: '/opt/ltsp/'

why is it looking for something at /opt ?

Revision history for this message
Serge Matveenko (lig) wrote :

latest gutsy have the same problem

Revision history for this message
Barry deFreese (bddebian) wrote :

I've uploaded this change. The OSError seems to stem from ltsp-client-setup not being run. I think ltsp-manager should fail more gracefully if ltsp is not set up yet.

Changed in ltsp-manager:
status: Confirmed → Fix Committed
Revision history for this message
Barry deFreese (bddebian) wrote :

ltsp-manager (0.0.2-0ubuntu3) gutsy; urgency=low

  * Update compat / debhelper b-d to 5
  * Hardcode ltsp-manager.glade path (LP: #73560)
  * Update maintainer per spec.

 -- Barry deFreese <email address hidden> Sun, 30 Sep 2007 15:31:26 -0400

Changed in ltsp-manager:
status: Fix Committed → Fix Released
Revision history for this message
Peter Kvan (peterkvan) wrote :

ltsp-manager (0.0.2-0ubuntu3) hardy

I had exact the same Tracebacks as Santiago Garcia Pimentel R.G. wrote on 2007-08-22
I was wondering too about why the program wanted a ltsp folder in /opt, but OK for me I just gave it the desired Folder.

The crash was the same but I had new tracebacks:

peter@peter-desktop:~$ ltsp-manager
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
Traceback (most recent call last):
  File "/usr/bin/ltsp-manager", line 254, in <module>
    base = LTSPManager()
  File "/usr/bin/ltsp-manager", line 33, in __init__
    self.fulfill_prereq()
  File "/usr/bin/ltsp-manager", line 61, in fulfill_prereq
    if len(pathlist) > 1:
TypeError: object of type 'int' has no len()

Anyone knowing what to do?

(Sorry but I did'nt understand Barry deFreese post on 2007-09-30)

Revision history for this message
Simon Schmidig (schmidig) wrote :

It crash on start / hardy:

simon@ltsp:~$ sudo ltsp-manager
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.