http://bugzilla.opensuse.org/show_bug.cgi?id=982243 Bug ID: 982243 Summary: home:ecsos/MediathekView: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: ecsos@schirra.net Reporter: w.pelser@web.de QA Contact: opensuse-communityscreening@forge.provo.novell.com Found By: --- Blocker: --- I'm running Tumbleweed. MediathekView 11.0-13.2 does not start. Error message is: @noname:/usr/bin> MediathekView.sh /usr/bin/MediathekView.sh: Unable to determine Java version Java virtual machine used: /usr/lib64/jvm/jre/bin/java classpath used: /usr/bin/build-classpath: Unable to determine Java version main class used: mediathek.Main flags used: options used: '-Xms128M' '-Xmx1G' arguments used: Fehler: Hauptklasse mediathek.Main konnte nicht gefunden oder geladen werden "/usr/lib64/jre" (there is no "usr/lib/jre/bin/java"!) is pointing to: "/etc/alternatives/jre". "etc/alternatives/jre" is pointing to "/usr/lib64/jvm/jre-1.9.0-openjdk" This is the wrong java version. If i change "usr/lib64/jvm/jre-1.9.0-openjdk" to "/usr/lib64/jvm/jre-1.8.0-openjdk" it is running. There are always problems, as version 1.9.0 is the default on Tumbleweed. When I work with the zip version, I have to do this: noname:~ # update-alternatives --config java There are 3 choices for the alternative java (providing /usr/bin/java). Selection Path Priority Status ------------------------------------------------------------ * 0 /usr/lib64/jvm/jre-1.9.0-openjdk/bin/java 1905 auto mode 1 /usr/lib64/jvm/jre-1.7.0-openjdk/bin/java 1705 manual mode 2 /usr/lib64/jvm/jre-1.8.0-openjdk/bin/java 1805 manual mode 3 /usr/lib64/jvm/jre-1.9.0-openjdk/bin/java 1905 manual mode Press <enter> to keep the current choice[*], or type selection number: 2 update-alternatives: using /usr/lib64/jvm/jre-1.8.0-openjdk/bin/java to provide /usr/bin/java (java) in manual mode to make it run. Sometimes after an update, I have to repeat it. -- You are receiving this mail because: You are on the CC list for the bug.