Bug 399097 - Amarok fails to locate plugins after installation to non-default location, no useful feedback provided to user
Summary: Amarok fails to locate plugins after installation to non-default location, no...
Status: RESOLVED NOT A BUG
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.9.0
Platform: Other All
: NOR major
Target Milestone: kf5
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-26 09:43 UTC by Eyal Rozenberg
Modified: 2019-08-05 19:17 UTC (History)
0 users

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 Eyal Rozenberg 2018-09-26 09:43:09 UTC
I've just built Amarok v2.9.0 on my (Debian Stretch / Devuan ASCII) system, installing it under `/usr/local`. I've followed the instructions on the Amarok website, and installation was successful. But - when I start the app up, I get a message telling me:

  "Amarok could not find any plugins. The indicates an installation problem."

First, this should just not happen. If the installation succeeded, the app should come up. Otherwise, `make install` should have failed, and produced some message regarding what's missing. Alternatively, CMake should have checked for whatever it is amarok needs (plugins etc.) or determined the directories where those resources are found - or alternatively, fail to configure the build.

Even if the latter has not been done, the error message should tell the user:

* Which directories were searched for plugins
* What specific plugins are required which were not found
* Where the user should the missing necessary plugins
* How / where to get those plug-ins, or source code for building them
Comment 1 Eyal Rozenberg 2018-09-27 22:08:58 UTC
The plugins are found if I set the environment variable

KDEDIRS="/usr/local:/usr"

but I only found this out by talking to a developer on IRC.

I believe Amarok could be expected to use its CMake-configured installation as a KDEDIRS entry; and this would have avoided the issue manifesting. 

Regardless, had the information I suggested been reported to the user, it would have been almost trivial to resolve the problem with no developers/IRC channel member help.
Comment 2 Christoph Feck 2019-08-05 19:17:07 UTC
See bug 409966 comment 1.