alacarte crashed with AttributeError in split()

[gmoore777]

Binary package hint: alacarte

I noticed on one of my 64-bit LucidLynx machines, an added manual menu item was not appearing under Applications.
I then learned of the System-->Preferences-->MainMenu application.
I do see the Menu item that I added. I check it. But it doesn't appear.

So then, I go back to my LucidLynx machine, where I do see that manual menu item.
I go to System-->Preferences-->MainMenu application in order to understand what really
happens (what file gets changed on the system) when a user checks or unchecks an item
so as to go fix that other machine.
Unchecking my manually created menu item cause this crash and hence this generated bug report.

I have all the latest and greatest packages installed on both machines as of last night.

(manually generated menu item is: i have edited /etc/xdg/menus/applications.menu with a menu entry
and then have plopped down two other files:
    /usr/share/desktop-directories/Omgeo.directory
    /usr/share/applications/omgeo_accurev_start.desktop
This has worked on HardyHeron and until recently has worked on LucidLynx.
)

ProblemType: Crash
Architecture: amd64
Date: Thu Feb 18 09:14:39 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/alacarte
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
InterpreterPath: /usr/bin/python2.6
Package: alacarte 0.12.4-1ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python -OOt /usr/bin/alacarte
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
PythonArgs: ['/usr/bin/alacarte']
SourcePackage: alacarte
Title: alacarte crashed with AttributeError in split()
Uname: Linux 2.6.32-13-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy galileo lpadmin plugdev tape video

[Apport retracing service (apport)]

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 #359771, 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.