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

[Nitram]

Binary package hint: landscape-client

It crashed on ubuntu while running update manager

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/landscape-sysinfo
InterpreterPath: /usr/bin/python2.6
Package: landscape-common 1.0.29.1-0ubuntu0.9.04.0
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/landscape-sysinfo
ProcEnviron:
 LANGUAGE=de_DE:de
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/sh
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.28-11-generic i686
UserGroups:

[Michael Vogt (mvo)]

What happens if you run (in a terminal):
$ python -c 'from twisted.internet import reactor'

Did that message happen during a release upgrade?

[Darxus (darxus)]

I just submitted the duplicate.

$ python -c 'from twisted.internet import reactor'

No output.

Yes, that happened during an upgrade. I verified that the crash timestamp was before the reboot at the end of the upgrade.

[Darxus (darxus)]

I was upgrading to the Karmic beta.

[Thomas Herve (therve)]

landscape-sysinfo runs as a cronjob in the background. During the upgrade, as twisted is upgraded, it's unimportable for a certain amount of time. Thus making the cronjob crash. I'm not sure where the problem relies: should we catch ImportError in landscape-sysinfo and don't do anything if the error happens?

[kc7zzv (kc7zzv)]

1) I upgrade from 9.04 to 9.10.
2) I checked for new updates with Synaptic Package Manager.
3) It found 3 and I installed them.
4) During the update or right afterword, Synaptic Package Manager crashed.

[piratemurray (mez-pahlan)]

Same for me too only I'm running 64bit. Cheers

[Maddmaxx (maddmaxx666)]

FYI, It happened to me on the first reboot, after upgrading from Jaunty to the beta. I wasn't running anything yet... Perhaps the first check done by the automatic update daemon?