menulibre crashed with SIGABRT in g_assertion_message()

[Sergio Benjamim]

Menulibre crashes with a corrupted file ~/.config/menus/xfce-applications.menu. You have to delete or rename this file to get the menulibre working again.

ERROR:/build/buildd/gnome-menus-3.10.1/./libmenu/gmenu-tree.c:4022:preprocess_layout_info: assertion failed: (!directory->preprocessed)
Aborted (core dumped)

Diff between the old config file (broken) and one new: http://pastebin.com/RfUNE32k

version 2.0.4-1

PS: there is other report, Bug #1310662, i don't know if this report is a duplicate of that.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: menulibre 2.0.4-1~ubuntu14.04.1
Uname: Linux 3.14.17-031417-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Mon Aug 25 16:19:42 2014
ExecutablePath: /usr/bin/menulibre
InstallationDate: Installed on 2014-05-26 (91 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
InterpreterPath: /usr/bin/python3.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/menulibre
Signal: 6
SourcePackage: menulibre
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libgnome-menu-3.so.0
 ?? () from /usr/lib/libgnome-menu-3.so.0
 ?? () from /usr/lib/libgnome-menu-3.so.0
Title: menulibre crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sbuild sudo vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1310662, 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.