JDK-5063681 : GNOME association files can be left behind after RPM uninstall...
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 5.0
  • Priority: P4
  • Status: Closed
  • Resolution: Not an Issue
  • OS: linux
  • CPU: generic
  • Submitted: 2004-06-16
  • Updated: 2004-06-18
  • Resolved: 2004-06-18
Related Reports
Relates :  
The files used by GNOME to associate the JAR and JNLP file extensions/mime-types can be left behind after all JRE/JDK RPM installations have been removed on Linux.  This can occur if Tiger is installed on a system that also has 1.4.2 installed.  It is caused by uninstalling Tiger, and then uninstalling 1.4.2.  It does not occur if Tiger or a higher JRE/JDK version is the last version uninstalled.

WORK AROUND Remove the GNOME association files for JAR and JNLP file extensions/mime-types by hand. This will require root privileges on most systems. For example: rm -f ${GNOMEDIR}/share/mime-info/java-archive.keys rm -f ${GNOMEDIR}/share/mime-info/java-archive.mime rm -f ${GNOMEDIR}/share/application-registry/java-archive.applications rm -f ${GNOMEDIR}/share/mime-info/java-web-start.keys rm -f ${GNOMEDIR}/share/mime-info/java-web-start.mime rm -f ${GNOMEDIR}/share/application-registry/java-web-start.applications Note: the environment variable GNOMEDIR is not defined on all systems. If the variable is not defined, use the default GNOME installation location of /usr.

EVALUATION This bug will be resolved by adding a Release Note to Tiger. Closing as 'not-a-bug'. ###@###.### 2004-06-18