sun-java6-plugin does not create symlink in /usr/lib/mozilla/plugins
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sun-java6 (Mandriva) |
New
|
Undecided
|
Unassigned | ||
sun-java6 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: sun-java6-plugin
/usr/bin/
for reference:
https:/
states "Firefox now looks for plugins in /usr/lib/
all other plugins place a symlink there through update-
this causes some problems: seamonkey fails to detect java plugin, and problems on 64bit systems. here are the related bugs:
https:/
https:/
the fix is simple:
line 6 of the postinst script should read:
browser_
then the alternative would be installed in /usr/lib/
currently, the workaround is to manually create the symlink, or, more properly, to manually install an alternative there with the following command:
sudo update-alternatives --install /usr/lib/
However, this should be fixed and the postinst script should install the link in /usr/lib/
don't know if the 'policy' will allow this fix to come through as a karmic update, but this definitely should be fixed for lucid.
note also that this did /not/ use to be a problem on jaunty and earlier, where the postinst installed the alternative in a number of locations:
browser_
I don't know why these were taken out in karmic, but they shouldn't have been - at the very least, the 'mozilla' one shouldn't have.
Changed in sun-java6 (Ubuntu): | |
status: | New → Confirmed |
tags: | added: firefox java plugin |
tags: | added: patch |
Adding my endorsement to the fact that I lost Java in SeaMonkey 2.0.2 when I upgraded from 1.1.17, and it was only thanks to nanotube's above workaround that I was able to restore my Java. To avoid others running into the same problem, the above-proposed change to postinst script appears to be very necessary.