[kmenuedit] [Bug 321152] Desktop file not usable outside KDE due to empty incompatible field: Path[$e]=

Martin K. bugzilla_noreply at kde.org
Thu Jan 31 13:13:47 GMT 2019


https://bugs.kde.org/show_bug.cgi?id=321152

Martin K. <dev at 256k.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dev at 256k.de

--- Comment #3 from Martin K. <dev at 256k.de> ---
Thank you Ben for reporting this issue.

(In reply to Ben Armstrong from comment #2)
> Drop the "Path[$e]=" line [..] at least when it is empty
I fully agree.

(In reply to Ben Armstrong from comment #2)
> you might consider keeping it for kmenuedit's primary users on KDE itself
Well, an empty "Path[$e]=" line isn't necessary even for KDE/Plasma users.

-----

For the record, I ran into this issue like this:

* I created a new Desktop Entry using kmenuedit (a simple web browser wrapper)
* I set the default web browser using systemsettings5 > Applications > Default
Applications > Web Browser > "in the following browser"
* I recognized that the new default was not applied for all applications.

This is my debugging summary:

> $ xdg-mime query default x-scheme-handler/http
> my-web-browser-wrapper.desktop
(This is correct.)

> $ gvfs-mime --query x-scheme-handler/http
> Default application for 'x-scheme-handler/http': firefox-esr.desktop
> Registered applications:
>         firefox-esr.desktop
>         chromium.desktop
> Recommended applications:
>         firefox-esr.desktop
>         chromium.desktop
As you can see, "my-web-browser-wrapper.desktop" is not there.

> $ gvfs-mime --set x-scheme-handler/http my-web-browser-wrapper.desktop
> Failed to load info for handler 'my-web-browser-wrapper.desktop'
The solution, as already mentioned by Ben, is to simply remove the following
line
(in `$HOME/.local/share/applications/my-web-browser-wrapper.desktop`)

> Path[$e]=

Please fix this issue

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list