alacarte crashes while loading
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
alacarte (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: alacarte
Description: Ubuntu Natty (development branch)
Release: 11.04
Installed: 0.13.2-1ubuntu2
Candidate: 0.13.2-1ubuntu2
Version table:
*** 0.13.2-1ubuntu2 0
500 http://
100 /var/lib/
alacarte menu editor will not load when clicking on the icon in the dock-like bar on the left
when launching alacarte from terminal it also crashes and displays the following text:
Traceback (most recent call last):
File "/usr/bin/
main()
File "/usr/bin/
app = MainWindow(datadir, version, sys.argv)
File "/usr/share/
self.editor = MenuEditor()
File "/usr/share/
self.
File "/usr/share/
self.
File "/usr/lib/
return expatbuilder.
File "/usr/lib/
result = builder.
File "/usr/lib/
parser.
xml.parsers.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: alacarte 0.13.2-1ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Wed Mar 9 09:58:32 2011
ExecutablePath: /usr/bin/alacarte
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python -OOt /usr/bin/alacarte
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: alacarte
Title: alacarte crashed with ExpatError in parseFile(): not well-formed (invalid token): line 1, column 0
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
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 #356188, 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.