landscape-sysinfo crashed with ImportError in <module>()

Bug #441062 reported by Darxus
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
landscape-client (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: landscape-client

Just rebooted after upgrade from jaunty to karmic beta and got this crash report.

ProblemType: Crash
Architecture: i386
Date: Fri Oct 2 22:20:02 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/landscape-sysinfo
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: landscape-common 1.3.2.3-0ubuntu0.9.10.0
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/landscape-sysinfo
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/sh
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
PythonArgs: ['/usr/bin/landscape-sysinfo']
SourcePackage: landscape-client
Title: landscape-sysinfo crashed with ImportError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/landscape-sysinfo", line 10, in <module>
     from twisted.internet import reactor
 ImportError: No module named twisted.internet
Uname: Linux 2.6.31-11-generic i686
UserGroups:

Revision history for this message
Darxus (darxus) wrote :

$ landscape-sysinfo
  System load: 0.18 Swap usage: 0% Users logged in: 1
  Usage of /: 34.1% of 452.74GB Temperature: 40 C
  Memory usage: 25% Processes: 169

  Graph this data and manage this system at https://landscape.canonical.com/

No error...

From the last command:
reboot system boot 2.6.31-11-generi Fri Oct 2 23:18 - 23:27 (00:09)

So this crash happened before the reboot after the upgrade.

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #365371, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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