alacarte crashed with ExpatError in parseFile()

Bug #356188 reported by Alexander Charykov on 2009-04-06
This bug affects 14 people
Affects Status Importance Assigned to Milestone
alacarte (Ubuntu)

Bug Description

Binary package hint: alacarte

When Editing menu, menu have been cleaned. When try to edit again, this error occured.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/alacarte
InterpreterPath: /usr/bin/python2.6
Package: alacarte 0.11.10-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python -OOt /usr/bin/alacarte
 PATH=(custom, user)
PythonArgs: ['/usr/bin/alacarte']
SourcePackage: alacarte
Title: alacarte crashed with ExpatError in parseFile()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Alexander Charykov (acharykov) wrote :
visibility: private → public
tags: removed: need-duplicate-check
Pedro Villavicencio (pedro) wrote :

ma you tell us a few steps in order to reproduce this?

Changed in alacarte (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Alexander Charykov (acharykov) wrote :

I've tryed to remove wine menus, after removing it. When I try to open alacarte it crashed and cleared menus. When tryed to edit new menus it crashes again.

Ubuntu's was in default settings, installed in vmware, software - standart, then I install wine + qip.

That's all.

Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Is this reproducible with Ubuntu 9.10 the Karmic Koala? Please test and provide us of feedback about it, Thanks in advance..

Changed in alacarte (Ubuntu):
importance: Medium → Low
YannUbuntu (yannubuntu) wrote :

I had this crash on Lucid 32bits (see Bug #600520).

WORKAROUND : emptying ~/.config/menus fixes the issue : Alacarte works again !

Changed in alacarte (Ubuntu):
status: Incomplete → Confirmed
Pedro Villavicencio (pedro) wrote :
Changed in alacarte (Ubuntu):
importance: Low → Medium
status: Confirmed → Triaged
summary: - Crashing alacarte
+ alacarte crashed with ExpatError in parseFile()
Changed in alacarte:
status: Unknown → New
Changed in alacarte:
importance: Unknown → Critical
tags: added: bugpattern-needed
dino99 (9d9) wrote :

bug #806987
alacarte crashed with ExpatError in parseFile(): not well-formed (invalid token): line 3, column 2

dino99 (9d9) wrote :

oem@oem-desktop:~$ alacarte
Traceback (most recent call last):
  File "/usr/bin/alacarte", line 37, in <module>
  File "/usr/bin/alacarte", line 33, in main
    app = MainWindow(datadir, version, sys.argv)
  File "/usr/share/alacarte/Alacarte/", line 49, in __init__
    self.editor = MenuEditor()
  File "/usr/share/alacarte/Alacarte/", line 36, in __init__
  File "/usr/share/alacarte/Alacarte/", line 60, in __loadMenus
    self.settings.dom = xml.dom.minidom.parse(self.settings.path)
  File "/usr/lib/python2.7/xml/dom/", line 1914, in parse
    return expatbuilder.parse(file)
  File "/usr/lib/python2.7/xml/dom/", line 924, in parse
    result = builder.parseFile(fp)
  File "/usr/lib/python2.7/xml/dom/", line 207, in parseFile
    parser.Parse(buffer, 0)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 3, column 2

Robert Roth (evfool) wrote :

Looks like bug #97449, might be a duplicate.
Ubuntu Bug Squad volunteer triager

dino99 (9d9) wrote :

Comment about #7 & #8 above:
with oneiric i386 b2 i dont get this issue since a few weeks now. Seems it was a transitional issue and might be declared as 'invalid' now or 'fixed'.

dino99 (9d9) wrote :

Fixed now into Precise/Quantal

Changed in alacarte (Ubuntu):
status: Triaged → Invalid
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

dino99 (9d9) on 2012-08-30
affects: alacarte → ubuntu
Changed in ubuntu:
importance: Critical → Undecided
Changed in ubuntu:
status: New → Confirmed
dino99 (9d9) on 2012-08-30
Changed in ubuntu:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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