eselect java-vm list shows blackdown-jre-1.4.2 though not installed: [code] $ eselect java-vm list Available Java Virtual Machines: grep: /usr/share/java-config-2/vm/blackdown-jre-1.4.2: No such file or directory [1] blackdown-jre-1.4.2 [2] icedtea-bin-6 [3] icedtea-bin-7 system-vm user-vm [/code] But blackdown-jre is not installed - it does not even exist in portage. According to /var/log/emerge.log I unmerged blackdown-jre in Nov 07, 2009. [code] $ eix blackdown * dev-java/blackdown-jdk [1] Available versions: (1.4.2) ~1.4.2.03-r17^s {X alsa doc examples nsplugin odbc} Homepage: http://www.blackdown.org Description: Blackdown Java Development Kit [1] "java" /var/lib/layman/java [/code] Output of java-check-environment ist ok. And there is no problem with java-config: [code]$ java-config --list-available-vms The following VMs are available for generation-2: 1) IcedTea JDK 6.1.12.6 [icedtea-bin-6] *) IcedTea JDK 7.2.4.3 [icedtea-bin-7][/code] Where does this blackdown-jre entry in eselect java-vm come from and how do I get rid of it? Reproducible: Always Steps to Reproduce: Happens whenever eselect java-vm list is called.
This is caused by an orphaned symlink in /usr/lib/jvm. With recent changes those are now visible. Portage was fixed to not leave them behind several years ago. You will have to remove the symlink manually.
(In reply to Ralph Sennhauser from comment #1) Thank you.
