When you used the installer, did you use the "user install" option? I guess you did. In this case, your system-wide directories are somehow broken, whereas you personal directories used by "user install" should be OK.
I still think you have parts of the old installation left which are affecting the new; the error message is pretty clear. But it's hard to tell what it is. If you ever get access to another Fedora box I'm certain that you will have the same experience as the other 8 or so success stories on F18 in this thread. But that's not much of a help, I know.
One thing you could do is to run (in the installer dir)
# rm -rf /usr/share/spotify-client /usr/lib64/spotify-client /usr/share/spotify /usr/lib64/spotify $ ./configure --prefix=/usr --libdir=/usr/lib64
# make install
# make register $ /usr/bin/spotify
This is basiclally the same thing as the rpm does, but with a little more control. After that, you should have a fresh installation in /usr/share/spotify-client and /usr/lib64/spotify-client and it should work. It will not affect the personal installation you did earlier.
Look carefully for error messages when running ./configure!
Have you installed any symlinks in /usr/lib64 when using the previous rpm? if so, remove them!
To test out, I just did as you suggested and used the installer with prefix=/usr and libdir=/usr/lib64. That also gives the same "out-of-sync" error as the RPM install was giving.
But then if I run the install to /usr/local (./configure with no options), then Spotify works fine!
Something about /usr and/or /usr/lib64 that is not making it happy but I'm stumped as to what it could be!
It's really bizarre, I have checked /usr/lib64 and /usr/share for spotify "remnants" and found nothing. All the symlinks that I had created to make 0.8.4 work have been removed (and I did run "ldconfig" to refresh the cache afterward). There is nothing with "spotify" in the name when I do a "find" on the /usr directory.
Bizarre is the word. But the basic conclusion seems to be that this not about what's installed, but where.
A hint might be that the new version has a $ORIGIN rpath. It means that it loads it's libraries from the same directory as the binary is in (falling back to ld.so's other paths if not found there). So, when installing in /usr/local/ it will prefer the libs in /usr/local/lib/spotify-client to the libs in /usr/lib64. Same is true for a personal install.
If this is the problem, it should be visible in the ldd output from the different cases. But that requires some serious grepping, I guess. But this seems like a hard problem...
I'm not wanting to be an ass or anything, but I could not care less about any licensing at this point. As someone that does not want to have to build an RPM themselves, i'd rather it already be done and working so I don't screw something up. I don't think anyone really cares at all. I'm paying 10 bucks a month for this, so it's not like I'm stealing work.
As for the licensing issues, these are basically between you and Spotify. They are capable of explaning their position on this, as done in several threads recently (look in the sticky threads on top of this page.)
That said, I don't think you should have any worries about rolling your own RPM using these instructions. In this 6-page thread noone have so far reported any problems building the RPMs. On the other hand, if you download RPM:s from some place out there there is always a risk that someone uses these RPM:s to install trojans or worse. Remember, when installing RPM:s you are acting as root, without safety nets.
Actually, the only safe way is the user-mode install described in this thread. Using that, everything is installed and run by a regular user without using root permissions at all. As long as you trust Spotify not to deliver trojans (I certainly do that) you are also safe when building your own RPM:s as described here.
First of all, great guide. Built the RPM with no problem. Installed it with no issue, but spotify won't run without root. I used chown to change the /etc/share/spotify-client so that my regular user is the owner, but no dice. Here is what is output when I run Spotify without root:
Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started ICE default IO error handler doing an exit(), pid = 23288, errno = 0
Any idea how to make it so I can launch it from a regular user?
Edit: I also tried the scripts you so thoughtfully provided on github, but I had the same problem. Still need root permissions to run.
"My Spotify" is what the github script installed. The Rpm should show up as Spotify, but there might be a bug (feature?) which makes the github installation "mask" the rpm one. Anyway, if you run 'my-spotify' on the command line it will invoke the "github" version whereas 'spotify" will run the RPM one.
That it works is fine. It would be even better to know what's working :). I suggest that you uninstall the github version and reinstall the rpm, just to get a defined state. The mechanics:
$ cd ~/.local/share/spotify-client
$ make uninstall
# yum reinstall ~/rpmbuild/RPMS/x86_64/spotify-client*
Having a clean rpm installation like this wil make upgrades much easier
Hm... it might make sense to check this audio group membership in the launcher on Fedora... might fix that.