lsb_release crashed with ImportError in <module>()

Bug #383646 reported by Martin Erik Werner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lsb (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: lsb

During upgrade (apt-get upgrade), lsb_release crashed, meaning that when apport tried to collect the problem, it invoked lsb_release, which again crashed, and so on... Problem disappeared after upgrade was completed (which allowed sending this report).
Unfortunately it was 101 packages that was being upgrades, but I'm supplying relevant dpkg.log for reference.

ProblemType: Crash
Architecture: amd64
Date: Thu Jun 4 16:48:22 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/lsb_release
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: lsb-release 4.0-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/lsb_release -sir
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-7.8-generic
PythonArgs: ['/usr/bin/lsb_release', '-sir']
SourcePackage: lsb
Title: lsb_release crashed with ImportError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/lsb_release", line 26, in <module>
     import lsb_release
 ImportError: No module named lsb_release
Uname: Linux 2.6.30-7-generic x86_64
UserGroups:

Revision history for this message
Martin Erik Werner (arand) wrote :
visibility: private → public
tags: removed: need-duplicate-check
Revision history for this message
JMFTheVCI (jmfthevci) wrote :

I also saw these messages during the install. Is it possible that these errors cause the re-introduction of https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/325973

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

Other bug subscribers

Bug attachments

Remote bug watches

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