** Also affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055280
Title:
openjdk-17-jre-headless 17.0.10+7-1~22.04.1:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openjdk-17 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055280
Title:
Security team advised that standard USN says
---
"This update uses a new upstream release, which includes additional bug
fixes. After a standard system update you need to restart any Java
applications to make all the necessary changes."
[1]
I will submit MR upstream to print a warning rather
Thank you for investigating this
I think we need to discuss the best way to fix it, e.g. maybe offer a
compatibility patch that will check if argc == 1 and try to check
contents of argv[0] in this case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Okay, I think the mystery might be solved.
The root cause is that unattended-upgrades (or some other apt upgrade)
does a openjdk-17 package update, while at the same time a java process
is running. After this minor upgrade, the protocol between the JRE's
forkAndExec JNI function and the
There isn't anything special as far as I know, it's just a plain Ubuntu
22.04 VM which is accessed by Jenkins over SSH. Note that we're using
the stable branch Jenkins, which is at 2.440.1, so it may be possible
that only that version is buggy.
I noticed a `_usr_lib_jvm_java-17-openjdk-
I agree - they do not check argc there, causing the startup segfault.
I have done the test in lxc container:
$lxc launch ubuntu-daily:noble
There i have installed jenkins weekly release:
---
sudo wget -O /usr/share/keyrings/jenkins-keyring.asc \
Possibly related: https://issues.jenkins.io/browse/JENKINS-72665
So the question is what the Jenkins agent does: I'm not sure it invokes
jspawnhelper directly, I assume it is going via the Java API, but there
could be some other bug that causes it to pass incorrect arguments to
jspawnhelper. It
Hi,
process spawning works (both jtreg tests and a small reproducer below):
---
public class Test {
public static void main(String[] args) throws Throwable {
Process p = new ProcessBuilder("ls", "-alrt", "/tmp").start();
p.waitFor();
}
}
---
but there were changes in
