I had the same results on two different systems. After moving the \home directory to a new partition, the Rhapsody plugin fails to work and will not install a second time after a complete removal. I tried starting with a new user, new ~/.mozilla , tried everything I could think of and a new Rhapsody plugin will not install and work properly.

I also installed Ubuntu/kubuntu in a "Virtualbox" and the Rhapsody plugin installs and works, but if that VDI is moved to another computer, the Rhapsody plugin doesn't work.

It seems like Rhapsody may be doing something to confirm the hardware, perhaps planting a hidden file somewhere, or reading soemthing that would let it know there were changes, making only 1 working install per machine possible. I do not wish to reinstall Ubuntu/Kubuntu. Has anyone else seen this? I can continue to access Rhapsody using a virgin copy of Ubuntu in a virtual box but would prefer to have it working with my orginal install.

Does anyone have a fix?




BTW: I do have an active, paid account with Rhapsody, I can log into my account but not the music unless I use the "virtualbox" install.


uname -ar:
Linux ubuntu 2.6.22-14-server #1 SMP Fri Feb 1 05:28:54 UTC 2008 i686 GNU/Linux

Assuming you are doing the plugin installation as a normal user, it can only write to your home directory and /tmp (am I forgetting something?) and /tmp gets wiped out at system boot. If I understand you correctly, you have the ability to install to a virtual machine, run a test, and then wipe it out? If so, you should be able to use the find command to find all files written by the installation process. Install the plugin and then

This will show all files whose status was changed in the last 5 minutes. Adjust the time to something appropriate and, of course, replace /home/user with your home directory.

This should work on a real installation and I am assuming it works on a virtual installation.

I hope this helps you troubleshoot the issue.

EDIT: I think Linux has ways of more directly observing what is happening with file access, but I am not familiar with these.

I am not sure what all was needed but did get it working.

I started by deleting the nprhapengine.so in ~/.mozilla/plugin and made sure it was not in /usr/lib/mozilla-firefox/plugins or /usr/lib/mozilla/plugins but was in /usr/lib/firefox/plugins . I also ran sudo chmod -Rv 755 /usr/lib/firefox/plugins, and made sure neither helix or realplay was installed. I would have to experiment to make sure what was actually needed.

it's ironic that I had to use /usr/lib/firefox/plugins rather than the home directory, but when it was only installed in the home directory it didn't show up in firefox about:plugins perhaps something with the way my system is set up.

Kubuntu Gutsy
KDE version: 3.5.8
System: Linux
Release: 2.6.24.2
Machine: i686