[Get to the bottom before you decide this is "unrelated" unSpawn.]
This is kinda funny and maybe we need a break from all this seriousness.
On my system, amarok can't find the audiocd or can't mount it or something and the Device Notifier settings don't do a darned thing. Even if I set device notifier to to run kscd instead of amarok, amarok still tries to run and still can't find the audiocd.
Same thing happens on both Kubuntu and openSUSE.
So in openSUSE I downloaded the amarok src rpm.
One of the patches adds a file that doesn't exist. The patches don't work anyway (they have to be patched by hand, some of the source/dest listings appear to be reversed as well.) so I
tried compiling without the patches, just to get to the point where I could start figuring out what they were trying to do.
I'll tell you right now, I never did figure that out. :-)
I noticed these missing dependencies for the amarok build.
gettext-tools-0.18.1.1-4.1 # this one adds an obscure file you wouldn't expect here but the whole build depends on it.
The asterisked one should cause those who understand this stuff to crack a smile.
Those in turn automatically add about 120 other files. This is not troubling, believe it or not, because it's quite hard to strip your system down to bare bones every time you compile just in order to get an accurate list of dependencies and once you identify the missing files (and there usually aren't many) things tend to go pretty smoothly.
[Well... depending on what sources you are compiling.]
So let's give a guy a break. Anyone can screw up or take a shortcut and as long as it is compilable and results in the correct build, it's functionally "open source" and we
have no real gripe.
What is troubling is that after compilation and manual installation amarok won't run.
But when uninstalled it runs again.
[Did I forget to uninstall the older version? Yup. Uninstalled and retested...]
Amarok still won't work.
One could say that I didn't install the amarok src rpm the way I was supposed to, and I could not argue with that other than to say, how else would I have seen the bad patches and missing files (such as ksuseinstall.h which is added by a patch and breaks the compilation at 46% of the way through)?
I can see what was supposed to happen during the installation in the spec file. Pre/post, all of it. No config files get updated or created.
[And YOU can too! Take a look at the short script for extracting rpms above.]
Solution: download the "opaque source" binary package.
And I might do that just to look at the install scripts in the opaque package that DOES install.
But I would think that anyone saying openSUSE rpms are "reliable" so "trust me" is either a fool or something substantially worse.
Kubuntu has some problems too but there is not this consistent pattern of broken source package that looks almost deliberate.
Now you might say, "What does this have to do with modern linuxes being windows-friendly and linux-unfriendly" and my answer in the context of this note would be another question:
How deep is Novell's involvement with Microsoft (the creators of the "nsa_key" backdoors)?
PS. And this wraps it up for me if you're happy to let it end here, unSpawn.