If you’re like me, you run 64-bit Ubuntu, use Rhapsody, and also run the 64-bit Flash 10 library in Firefox.
If you do this you are in for a MADDENING experience much like mine. You can’t sign into Rhapsody. Rhapsody’s support team will only ask if you meet the minimum specs, and when you answer in the affirmative, they will then admit that they’re clueless about where to proceed from there. Using WINE, IEs4Linux’ IE6 and Flash 9 have a memory leak that eventually crashed IE on my box.
Unfortunately the fix for Firefox/Linux is almost as bad as the problem: Remove the 64-bit Flash 10 library and install the nspluginwrapper 32-bit Flash 10 library. This package is usually called flashplugin-nonfree or flashplugin-installer. Users of Karmic Koala, you may have an additional problem: The flashplugin-install brings in a 64-bit library that propagates the exact same problem.
How did I come to this conclusion? In my quest to fly a finger to Rhapsody’s support team, I installed VMs of Ubuntu 32 and 64-bit for Hardy, Karmic, and Lucid, for a total of six. I then installed flashplugin-installer and tested them all on Rhapsody.com. Talk about a time sink. Good god. Every single one of them worked except for Karmic. I ran `file` on /usr/lib/flashplugin-installer/lib*.so and it informed me that the library was ELF 64-bit… the only significant difference between this non-working system and the other perfectly-working systems.
Anyway, Rhapsody works now and all I have to worry about are the grey screens again. Grey screens being why I got rid of the ridiculous nspluginwrapper crap in the first place.
Ugh.
-LightningCrash
Tags: flash, nspluginwrapper, rhapsody, ubuntu