Ubuntu
software-center package

update-software-center crashed with ImportError in /usr/share/software-center/softwarecenter/utils.py: No module named gmenu

Bug #720324 reported by sid on 2011-02-16

This bug report is a duplicate of: Bug #701641: update-software-center crashed with ImportError in /usr/lib/pymodules/python2.7/gtk-2.0/glib/__init__.py: No module named _glib. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	software-center (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: software-center

software center crash reported after logging in. Xorg and libnotify were also reported to have crashed simultaneously.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: software-center 3.1.18
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic i686
Architecture: i386
Date: Tue Feb 15 14:22:55 2011
ExecutablePath: /usr/share/software-center/update-software-center
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-software-center --triggered /usr/share/locale-langpack
ProcCwd: /
ProcEnviron:
PATH=(custom, user)
LANG=en_CA.utf8
SHELL=/bin/bash
PythonArgs: ['/usr/sbin/update-software-center', '--triggered', '/usr/share/locale-langpack']
SourcePackage: software-center
Title: update-software-center crashed with ImportError in /usr/share/software-center/softwarecenter/utils.py: No module named gmenu
UserGroups:

Tags:

Revision history for this message

sid (skattoju) wrote on 2011-02-16:

Traceback.txt Edit (433 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-02-16: 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 #701641, 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.