JabRef error on launch
up vote
2
down vote
favorite
I have just upgraded to 18.10. I was using JabRef, installed through Apt. Now, JabRef won't launch. When I try to launch it from the command line I get this error:
Error occurred during initialization of boot layer
java.lang.module.FindException: Module java.se.ee not found
What is going on?
18.10
add a comment |
up vote
2
down vote
favorite
I have just upgraded to 18.10. I was using JabRef, installed through Apt. Now, JabRef won't launch. When I try to launch it from the command line I get this error:
Error occurred during initialization of boot layer
java.lang.module.FindException: Module java.se.ee not found
What is going on?
18.10
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have just upgraded to 18.10. I was using JabRef, installed through Apt. Now, JabRef won't launch. When I try to launch it from the command line I get this error:
Error occurred during initialization of boot layer
java.lang.module.FindException: Module java.se.ee not found
What is going on?
18.10
I have just upgraded to 18.10. I was using JabRef, installed through Apt. Now, JabRef won't launch. When I try to launch it from the command line I get this error:
Error occurred during initialization of boot layer
java.lang.module.FindException: Module java.se.ee not found
What is going on?
18.10
18.10
asked Oct 20 at 10:26
twsh
1204
1204
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
2
down vote
accepted
Error is caused by the upgrade of java runtime enviroment to version 11. On my system, after upgrade I had both openjdk-8-jre and openjdk-11-jre. The version 11 is favored by the /etc/alternatives settings, and jabref fails.
If you remove the jdk-11 packages and keep only the version 8, then the jabref starts as usual.
Why is this happening now? The jabref starter script provided by Ubuntu packaging (/usr/bin/jabref) has this
if ! ( echo "$JAVA_VERSION" | grep -q '1.8.0' ) ; then
# We need some options to start this version on openjdk9 and later
# See http://discourse.jabref.org/t/cannot-start-jabref-3-7-3-6-using-java-9-on-ubuntu-16-04/361/8
JABREF_JAVA_OPTS=${JABREF_JAVA_OPTS-"--add-modules=java.se.ee --add-opens=java.desktop/java.awt=ALL-UNNAMED"}
fi
However, the se-ee modules were deprecated in JDK 9 so they are not present in JDK 11.
https://jaxenter.com/jdk-11-java-ee-modules-140674.html
I'm still checking on how the jabref (as packaged for Ubuntu) can be fixed.
The short term fix is to run it with Java 8.
On our RedHat linux systems, we have run into the problem and the tech assistant here says that if you get the full Java packages from Oracle, they still have the needed components, but I don't know where the truth lies. I'll keep checking.
Just for those who also had to google how to remove all jdk-11 files:sudo apt-get remove "openjdk-11-*"
(quotes required for zsh).
– Felix
Nov 27 at 4:09
add a comment |
up vote
0
down vote
You can install openjdk-11 and openjdk-8 together on ubuntu 18.10, I just modify /usr/bin/jabref as below:
#!/bin/sh
JAVA_CMD=/usr/lib/jvm/java-8-openjdk-amd64/bin/java
...
That means, just point JAVA_CMD to openjdk-8, not openjdk-11.
This not hurt all other openjdk-11 related applications.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1085502%2fjabref-error-on-launch%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Error is caused by the upgrade of java runtime enviroment to version 11. On my system, after upgrade I had both openjdk-8-jre and openjdk-11-jre. The version 11 is favored by the /etc/alternatives settings, and jabref fails.
If you remove the jdk-11 packages and keep only the version 8, then the jabref starts as usual.
Why is this happening now? The jabref starter script provided by Ubuntu packaging (/usr/bin/jabref) has this
if ! ( echo "$JAVA_VERSION" | grep -q '1.8.0' ) ; then
# We need some options to start this version on openjdk9 and later
# See http://discourse.jabref.org/t/cannot-start-jabref-3-7-3-6-using-java-9-on-ubuntu-16-04/361/8
JABREF_JAVA_OPTS=${JABREF_JAVA_OPTS-"--add-modules=java.se.ee --add-opens=java.desktop/java.awt=ALL-UNNAMED"}
fi
However, the se-ee modules were deprecated in JDK 9 so they are not present in JDK 11.
https://jaxenter.com/jdk-11-java-ee-modules-140674.html
I'm still checking on how the jabref (as packaged for Ubuntu) can be fixed.
The short term fix is to run it with Java 8.
On our RedHat linux systems, we have run into the problem and the tech assistant here says that if you get the full Java packages from Oracle, they still have the needed components, but I don't know where the truth lies. I'll keep checking.
Just for those who also had to google how to remove all jdk-11 files:sudo apt-get remove "openjdk-11-*"
(quotes required for zsh).
– Felix
Nov 27 at 4:09
add a comment |
up vote
2
down vote
accepted
Error is caused by the upgrade of java runtime enviroment to version 11. On my system, after upgrade I had both openjdk-8-jre and openjdk-11-jre. The version 11 is favored by the /etc/alternatives settings, and jabref fails.
If you remove the jdk-11 packages and keep only the version 8, then the jabref starts as usual.
Why is this happening now? The jabref starter script provided by Ubuntu packaging (/usr/bin/jabref) has this
if ! ( echo "$JAVA_VERSION" | grep -q '1.8.0' ) ; then
# We need some options to start this version on openjdk9 and later
# See http://discourse.jabref.org/t/cannot-start-jabref-3-7-3-6-using-java-9-on-ubuntu-16-04/361/8
JABREF_JAVA_OPTS=${JABREF_JAVA_OPTS-"--add-modules=java.se.ee --add-opens=java.desktop/java.awt=ALL-UNNAMED"}
fi
However, the se-ee modules were deprecated in JDK 9 so they are not present in JDK 11.
https://jaxenter.com/jdk-11-java-ee-modules-140674.html
I'm still checking on how the jabref (as packaged for Ubuntu) can be fixed.
The short term fix is to run it with Java 8.
On our RedHat linux systems, we have run into the problem and the tech assistant here says that if you get the full Java packages from Oracle, they still have the needed components, but I don't know where the truth lies. I'll keep checking.
Just for those who also had to google how to remove all jdk-11 files:sudo apt-get remove "openjdk-11-*"
(quotes required for zsh).
– Felix
Nov 27 at 4:09
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Error is caused by the upgrade of java runtime enviroment to version 11. On my system, after upgrade I had both openjdk-8-jre and openjdk-11-jre. The version 11 is favored by the /etc/alternatives settings, and jabref fails.
If you remove the jdk-11 packages and keep only the version 8, then the jabref starts as usual.
Why is this happening now? The jabref starter script provided by Ubuntu packaging (/usr/bin/jabref) has this
if ! ( echo "$JAVA_VERSION" | grep -q '1.8.0' ) ; then
# We need some options to start this version on openjdk9 and later
# See http://discourse.jabref.org/t/cannot-start-jabref-3-7-3-6-using-java-9-on-ubuntu-16-04/361/8
JABREF_JAVA_OPTS=${JABREF_JAVA_OPTS-"--add-modules=java.se.ee --add-opens=java.desktop/java.awt=ALL-UNNAMED"}
fi
However, the se-ee modules were deprecated in JDK 9 so they are not present in JDK 11.
https://jaxenter.com/jdk-11-java-ee-modules-140674.html
I'm still checking on how the jabref (as packaged for Ubuntu) can be fixed.
The short term fix is to run it with Java 8.
On our RedHat linux systems, we have run into the problem and the tech assistant here says that if you get the full Java packages from Oracle, they still have the needed components, but I don't know where the truth lies. I'll keep checking.
Error is caused by the upgrade of java runtime enviroment to version 11. On my system, after upgrade I had both openjdk-8-jre and openjdk-11-jre. The version 11 is favored by the /etc/alternatives settings, and jabref fails.
If you remove the jdk-11 packages and keep only the version 8, then the jabref starts as usual.
Why is this happening now? The jabref starter script provided by Ubuntu packaging (/usr/bin/jabref) has this
if ! ( echo "$JAVA_VERSION" | grep -q '1.8.0' ) ; then
# We need some options to start this version on openjdk9 and later
# See http://discourse.jabref.org/t/cannot-start-jabref-3-7-3-6-using-java-9-on-ubuntu-16-04/361/8
JABREF_JAVA_OPTS=${JABREF_JAVA_OPTS-"--add-modules=java.se.ee --add-opens=java.desktop/java.awt=ALL-UNNAMED"}
fi
However, the se-ee modules were deprecated in JDK 9 so they are not present in JDK 11.
https://jaxenter.com/jdk-11-java-ee-modules-140674.html
I'm still checking on how the jabref (as packaged for Ubuntu) can be fixed.
The short term fix is to run it with Java 8.
On our RedHat linux systems, we have run into the problem and the tech assistant here says that if you get the full Java packages from Oracle, they still have the needed components, but I don't know where the truth lies. I'll keep checking.
answered Oct 20 at 21:39
pauljohn32
2,199822
2,199822
Just for those who also had to google how to remove all jdk-11 files:sudo apt-get remove "openjdk-11-*"
(quotes required for zsh).
– Felix
Nov 27 at 4:09
add a comment |
Just for those who also had to google how to remove all jdk-11 files:sudo apt-get remove "openjdk-11-*"
(quotes required for zsh).
– Felix
Nov 27 at 4:09
Just for those who also had to google how to remove all jdk-11 files:
sudo apt-get remove "openjdk-11-*"
(quotes required for zsh).– Felix
Nov 27 at 4:09
Just for those who also had to google how to remove all jdk-11 files:
sudo apt-get remove "openjdk-11-*"
(quotes required for zsh).– Felix
Nov 27 at 4:09
add a comment |
up vote
0
down vote
You can install openjdk-11 and openjdk-8 together on ubuntu 18.10, I just modify /usr/bin/jabref as below:
#!/bin/sh
JAVA_CMD=/usr/lib/jvm/java-8-openjdk-amd64/bin/java
...
That means, just point JAVA_CMD to openjdk-8, not openjdk-11.
This not hurt all other openjdk-11 related applications.
add a comment |
up vote
0
down vote
You can install openjdk-11 and openjdk-8 together on ubuntu 18.10, I just modify /usr/bin/jabref as below:
#!/bin/sh
JAVA_CMD=/usr/lib/jvm/java-8-openjdk-amd64/bin/java
...
That means, just point JAVA_CMD to openjdk-8, not openjdk-11.
This not hurt all other openjdk-11 related applications.
add a comment |
up vote
0
down vote
up vote
0
down vote
You can install openjdk-11 and openjdk-8 together on ubuntu 18.10, I just modify /usr/bin/jabref as below:
#!/bin/sh
JAVA_CMD=/usr/lib/jvm/java-8-openjdk-amd64/bin/java
...
That means, just point JAVA_CMD to openjdk-8, not openjdk-11.
This not hurt all other openjdk-11 related applications.
You can install openjdk-11 and openjdk-8 together on ubuntu 18.10, I just modify /usr/bin/jabref as below:
#!/bin/sh
JAVA_CMD=/usr/lib/jvm/java-8-openjdk-amd64/bin/java
...
That means, just point JAVA_CMD to openjdk-8, not openjdk-11.
This not hurt all other openjdk-11 related applications.
answered Nov 30 at 23:43
Baochen Su
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1085502%2fjabref-error-on-launch%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown