Bug 378250 - desktopparser searches for wrong service file types
Summary: desktopparser searches for wrong service file types
Status: RESOLVED DUPLICATE of bug 386509
Alias: None
Product: frameworks-kpackage
Classification: Frameworks and Libraries
Component: default (other bugs)
Version First Reported In: 5.32.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-29 18:33 UTC by Kishore Gopalakrishnan
Modified: 2020-12-01 18:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kishore Gopalakrishnan 2017-03-29 18:33:30 UTC
I get this error when I run 'plasmapkg -l' on my system.

kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/kwin-script.desktop, tried ("/home/kishore/.local/share", "/usr/share", "/usr/local/share")

The relevant desktop file is '/usr/share/kservicetypes5/kwinscript.desktop' (without the dash). It seems to be searching for the wrong file.
Comment 1 Kishore Gopalakrishnan 2017-03-29 18:39:22 UTC
(In reply to kishore96 from comment #0)
> I get this error when I run 'plasmapkg -l' on my system.
> 
> kf5.kcoreaddons.desktopparser: Could not locate service type file
> kservicetypes5/kwin-script.desktop, tried ("/home/kishore/.local/share",
> "/usr/share", "/usr/local/share")
> 
> The relevant desktop file is '/usr/share/kservicetypes5/kwinscript.desktop'
> (without the dash). It seems to be searching for the wrong file.

Correction: The error occurs when I run 'plasmapkg2 -l'. 

I also get the same error when I run 'kpackagetool5 -l'.
Comment 2 Kishore Gopalakrishnan 2017-03-29 18:58:57 UTC
Should this bug have been filed under the 'frameworks-kpackage' component?
Comment 3 Michael Pyne 2017-03-30 00:14:05 UTC
I suspect it's either a Plasma bug of some type (whether it's plasmapkg2 from plasma-framework or kpackagetool5 from kpackage, who knows?) or old installed files from previous KF5 git installations that you may have forgot to clean out (I have that happen a lot myself).

Either way it's not kcoreaddons, we're just the messenger in this case.

I'll reassign to kpackage for now since it's the currently-approved method for handling Plasma packages and the Plasma devs can reassign from there if I got it wrong.
Comment 4 Kishore Gopalakrishnan 2017-03-30 01:49:03 UTC
(In reply to Michael Pyne from comment #3)
> . . . old
> installed files from previous KF5 git installations that you may have forgot
> to clean out (I have that happen a lot myself).


I can reproduce this in a KDE Neon live session after installing a kwin script (to test, I used the 'sticky window snapping' [https://store.kde.org/p/1112552] script, and the 'maximise to new virtual desktop' [https://store.kde.org/p/1171196] script), so I don't think it is due to left over files.
Comment 5 Kishore Gopalakrishnan 2017-03-30 02:12:51 UTC
(In reply to kishore96 from comment #4)
> (In reply to Michael Pyne from comment #3)
> > . . . old
> > installed files from previous KF5 git installations that you may have forgot
> > to clean out (I have that happen a lot myself).
> 
> 
> I can reproduce this in a KDE Neon live session after installing a kwin
> script (to test, I used the 'sticky window snapping'
> [https://store.kde.org/p/1112552] script, and the 'maximise to new virtual
> desktop' [https://store.kde.org/p/1171196] script), so I don't think it is
> due to left over files.

Correction. This was in another Arch installation in a VM. Sorry for the mistake. I keep on forgetting which VM I'm in.
Comment 6 Nate Graham 2020-12-01 18:26:20 UTC
Ah I think this is the issue of plasmapkg2 not installing the desktop file to the right place

*** This bug has been marked as a duplicate of bug 386509 ***