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

Bug #460220 reported by gilvorhoff
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

Within first minute after login of first boot with upgrade 9.10rc (from 9.04 using alternate desktop i386/32 cd plus internet)...
I'm on a MacBook 1,1 with 2GB RAM.
I had just disabled my wireless which had connected automatically (I was still on the ethernet I used for the upgrade).
I had just moused over the icons on the menubar at the top edge of the desktop.
There is one garbled icon (a red "no-entry" symbol) where the FireFox icon should be.
(I'm submitting this via FireFox, which opened automatically as part of the spontaneous crash report prompting--Nifty!)
According to Synaptic, I don't have landscape-client installed.
I do have landscape-common v. 1.3.2.4-0ubuntu0.9.10.0.
Evidently some script called landscape-client instead of landscape-common, or else the installer forgot to give me the client?

Thanks for your help!

ProblemType: Crash
Architecture: i386
Date: Sun Oct 25 04:50:02 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/landscape-sysinfo
InterpreterPath: /usr/bin/python2.6
Package: landscape-common 1.3.2.4-0ubuntu0.9.10.0
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/landscape-sysinfo
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/sh
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/bin/landscape-sysinfo']
SourcePackage: landscape-client
Title: landscape-sysinfo crashed with ImportError in <module>()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

Revision history for this message
gilvorhoff (gilvorhoff) wrote :
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 #459798, 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.