If amarok is run while the environment variable KDEDIRS is not set, it will open a dialog with the following text: Amarok could not find any sound-engine plugins. Amarok is now updating the KDE configuration database. Please wait a couple of minutes, then restart Amarok. If this does not help, it is likely that Amarok is installed under the wrong prefix, please fix your installation using: $ cd /path/to/amarok/source-code/ $ su -c "make uninstall" $ ./configure --prefix=`kde-config --prefix` && su -c "make install" $ kbuildsycoca $ amarok More information can be found in the README file. For further assistance join us at #amarok on irc.freenode.net. At this point, it tries to run kbuildsycoca, which fails if /usr/kde/3.5/bin is not in the user's PATH, which it probably isn't. This happens when amarok is the only program installed that relies on a lot of KDE stuff. IMO, the amarok ebuild should check the user's environment for KDEDIRS and, if not found, print a warning that he must run "source /etc/profile" in order to use it in any existing session. Reproducible: Always Steps to Reproduce:
(In reply to comment #0) > If this does not help, it is likely that Amarok is installed under the wrong > prefix, please fix your installation using: > > $ cd /path/to/amarok/source-code/ > $ su -c "make uninstall" > $ ./configure --prefix=`kde-config --prefix` && su -c "make install" > $ kbuildsycoca > $ amarok The idea applications may only be installed in the KDE prefix path is fundamentally mistaken. Unset KDEDIRS is simply not supported - which is a bit of a problem with the KDE 3 to 4 conversion, see also http://lists.kde.org/?l=kde-core-devel&m=120569044704554&w=2 > At this point, it tries to run kbuildsycoca, which fails if /usr/kde/3.5/bin is > not in the user's PATH, which it probably isn't. This happens when amarok is > the only program installed that relies on a lot of KDE stuff. IMO, the amarok > ebuild should check the user's environment for KDEDIRS and, if not found, print > a warning that he must run "source /etc/profile" in order to use it in any > existing session. Oh, if this is the whole problem, I'm inclined to say: "Sorry, non-issue." We'd have to do this for all KDE applications not just Amarok and there's no point in spamming the logs. Gentoo simply isn't a newbie distro,like Ubuntu or Suse. On the other hand, it wouldn't be bad, if we had a bit more KDE specific documentation, discussing issues like this one.
Well, I bring it up because this has bitten me several times. "Log out and log back in" is not the first solution that comes to mind when you install something and it doesn't work. Also, a fair amount of googling the contents of the dialog reveal lots of people with this problem but not the solution. I'm no newbie, but this problem is seriously difficult to track down, especially given the bizarre contents of the dialog box. The only reason I figured it out this time is because, for some reason, I decided to try running it as root, and it worked. Do you mean spam in the changelogs? Surely that's not a serious concern. I suspect there aren't that many projects where this would be necessary, anyway, as it's only really relevant for apps that people would want to run without kde installed. Maybe as a middle ground, something could be added such that every ebuild that uses "inherit kde" gets the warning. Also, there are plenty of other projects that print a warning just like this: see ati-drivers, adesklets, and sbcl, to name a few.
(In reply to comment #2) > Well, I bring it up because this has bitten me several times. "Log out and log > back in" is not the first solution that comes to mind when you install > something and it doesn't work. Also, a fair amount of googling the contents of > the dialog reveal lots of people with this problem but not the solution. I'm no > newbie, but this problem is seriously difficult to track down, especially given > the bizarre contents of the dialog box. The only reason I figured it out this > time is because, for some reason, I decided to try running it as root, and it > worked. > > Do you mean spam in the changelogs? Surely that's not a serious concern. I > suspect there aren't that many projects where this would be necessary, anyway, > as it's only really relevant for apps that people would want to run without kde > installed. Maybe as a middle ground, something could be added such that every > ebuild that uses "inherit kde" gets the warning. Also, there are plenty of > other projects that print a warning just like this: see ati-drivers, adesklets, > and sbcl, to name a few. > remerge kdebase-startkde resolve the problem
That is not a solution to the problem. I don't have kdebase-startkde installed at all, and I don't want it. Actually, I don't even want amarok, but people keep reporting bugs to me about it. At any rate, there's no amount of software you can install that will change the environment variables in an existing session. In a new session, the variables are set automatically, so no additional software is needed. QED
Does anyone know how to resolve this issue because: > remerge kdebase-startkde resolve the problem doesn't help. I still get this messsage: Amarok could not find any sound-engine plugins. Amarok is now updating the KDE configuration database. Please wait a couple of minutes, then restart Amarok. If this does not help, it is likely that Amarok is installed under the wrong prefix, please fix your installation using: $ cd /path/to/amarok/source-code/ $ su -c "make uninstall" $ ./configure --prefix=`kde-config --prefix` && su -c "make install" $ kbuildsycoca $ amarok More information can be found in the README file. For further assistance join us at #amarok on irc.freenode.net.
(In reply to comment #5) > Does anyone know how to resolve this issue because: > > > remerge kdebase-startkde resolve the problem > > doesn't help. I still get this messsage: There is a script named kde3 in kdelibs that helps to run KDE3 applications in non-KDE3 environment. You can try to start amarok by this script, i.e. kde3 amarok . It should work.
> > ebuild should check the user's environment for KDEDIRS and, if not found, print > > a warning that he must run "source /etc/profile" in order to use it in any > > existing session. > > Oh, if this is the whole problem, I'm inclined to say: "Sorry, non-issue." We'd > have to do this for all KDE applications not just Amarok and there's no point > in spamming the logs. Gentoo simply isn't a newbie distro,like Ubuntu or Suse. > On the other hand, it wouldn't be bad, if we had a bit more KDE specific > documentation, discussing issues like this one. Considering this doesn't work, it's not the whole problem.
This should not happen anymore, since we have all kde apps in one prefix and for kde4 we dont use KDEDIRS schema. Please confirm.
It's fixed in kde-env-4.2.3-r1 - so please update your systems.
@reavertm: it is fixed, so close it :P @everybody else: this is fixed for both kde3 and kde4 amarok, if this problem persists for anyone please reopen. thanks
