Parsing errors log shows invalid errors

Bug #1788814 reported by Juan Simón on 2018-08-24
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MenuLibre
Fix Released
Undecided
Unassigned

Bug Description

Arch Linux
MenuLibre 2.2.0

Every time I execute this program shows this in Parsing errors log:
"/usr/share/applications/org.gnome.ChromeGnomeShell.desktop
Exec key not found"

$ cat /usr/share/applications/org.gnome.ChromeGnomeShell.desktop
[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=GNOME Shell integration
Comment=Provides integration with GNOME Shell and the corresponding extensions repository https://extensions.gnome.org.
Icon=org.gnome.ChromeGnomeShell
DBusActivatable=true
NoDisplay=true

The Exec key is not mandatory in a .desktop file (https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-1.0.html#recognized-keys).
In this case this key isn't used and it's ok.

Juan Simón (simonbcn) on 2018-08-24
description: updated
description: updated
Sean Davis (bluesabre) wrote :

Thanks for the bug report. Resolved with the below commit.

https://git.launchpad.net/menulibre/commit/?id=ace6058a090ccd9e6671cebf9e106905ed6b4f64

Changed in menulibre:
status: New → Fix Committed
Sean Davis (bluesabre) on 2019-05-31
Changed in menulibre:
milestone: none → 2.2.1
status: Fix Committed → Fix Released
Mike Ferreira (mafoelffen) wrote :

The commit was 2019.05.31. It's 2019.12.15...

New install on system was this week. Still have this problem.

Mike Ferreira (mafoelffen) wrote :

To confirm i is just looking at/for an Exec Key, I added one:

# Exec: echo ' ' > /dev/null 2>&1

...and menulibre starts without any parse errors. So the committed fix (2019.05.31) is either not available to me yet or doesn't fix this specific system.

Mike Ferreira (mafoelffen) wrote :

*** Correction/Edit on #3: ***

To confirm menulibre was just looking at/for an Exec Key, I added one:

Added line>> Exec:echo ' ' > /dev/null 2>&1

...and menulibre then started without any parse errors.

So the committed fix (2019.05.31) is either not available to me yet or doesn't fix this specific system.
*** End Edit ***

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers