Same issues here but with an upgrade to Lucid, so that I kept my Sun Java JDK installation from Karmic (the upgrade appears to have automatically added the partner repo that Ekr had to do manually, which makes sense). Somehow I had the OpenJDK visualvm package installed (presumably by the upgrade process), even though the OpenJDK JRE or JDK wasn't installed....
We need to be clear about the issue though because I had slightly different symptoms (maybe Ekr can clarify). With the standard OpenJDK installation and its visualvm (packages default-jdk and visualvm), jvisualvm starts up for me with the Fluid error. However, I can still then look at running or launched Java apps. I presume the Fluid stuff is just doing the calibration like the Sun one does. Ekr's workaround is to switch to the Sun jvisualvm and JDK, and so isn't actually working round the OpenJDK jvisualvm bug as such (i.e. it's really switching apps, not working round the bug). I can confirm his issue with the Sun install not changing the jvisualvm symlink. I assume that this should be a separate bug then (**but can a dev please confirm that this is what they'd prefer and what project it should be under; sorry, I'm a bit of a noob!**). Since there are update- alternatives entries for java, javac, javadoc, rmiregistry, etc. (but not for jvisualvm), I assume the correct fix is for a jvisualvm update- alternatives to be added and incorporated into the Sun package install process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/577958 Title: VisualVM cannot load profiler (64 bit) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
