Thank you for taking the time to report this bug and helping to make
Ubuntu better.
However, according to this report, you are not using the most recent
version of this package for your Ubuntu release. Please upgrade to the
most recent version and let us know if you are still having this issue.
Thanks Olivier,
I confirm your test results: ignoring the DocumentView$1.class is fine
with both openjdk-10 and openjdk-11.
I agree that JEP-181 is the most probable cause as to why this access
bridge class is no longer generated - there's a small discussion on why
access bridge classes were
** Summary changed:
- Glassfish is useless, please remove
+ Please remove glassfish from Cosmic
** Description changed:
+ glassfish has been removed from Debian, is in cosmic/universe, and
+ reverse-depends reports zero packages for depends and build-depends.
+
+
+ [Original description]
** Bug watch added: Debian Bug tracker #910773
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910773
** Also affects: clojure1.8 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910773
Importance: Unknown
Status: Unknown
--
You received this bug notification
debdiff with a upstream fix [1] for clojure1.8
[1]
https://github.com/clojure/clojure/commit/68d8b83138437c18f1d5cf9ba46c056aa2701d23
** Summary changed:
- clojure fails to run with openjdk-11
+ clojure autopkgtest fails to run with openjdk-11
** Patch added:
** Package changed: clojure (Ubuntu) => clojure1.8 (Ubuntu)
** Changed in: clojure1.8 (Ubuntu)
Importance: Undecided => High
** Changed in: clojure1.8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796985
Title:
clojure fails to run with openjdk-11
To manage notifications about this bug go to:
Public bug reported:
closure autopkgtest fails with openjdk-11 with the following message:
autopkgtest [06:21:34]: test run-clojure: - - - - - - - - - - stderr - - - - -
- - - - -
Exception in thread "main" java.lang.ExceptionInInitializerError
at clojure.main.(main.java:20)
Caused by:
Yes, sorry, I should have updated this bug earlier. We decided to drop
the delta for now and recheck how the gradle packages will behave. We
will keep tracking for build failures on gradle dependent package to
decide whether a new discussion with Debian is required - more
information the java api
** Patch added: "gradle_4.4-3_debdiff_4.4-3ubuntu1.patch"
https://bugs.launchpad.net/debian/+source/gradle/+bug/1795767/+attachment/5196248/+files/gradle_4.4-3_debdiff_4.4-3ubuntu1.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
gradle 4.4-3 FTBFS when built with openjdk-11. Only gradle 4.8 added
support for being built with openjdk-11 but as of gradle 4.5 it requires
kotlin for the build which is not yet packaged in either Debian or
Ubuntu.
The proposed patch backports 4 commits that allows gradle
List of packages that have been added today, so they were not in the
list that was reviewed and neither the in packages listed in Steve's
comment.
** Attachment added: "package-list-not-yet-reviewed-20181003"
** Description changed:
Asking for a FFe exception to keep in sync (or merging) with Java
packages as uploaded to Debian, until the 18.10 release. As outlined in
https://lists.ubuntu.com/archives/ubuntu-
release/2018-March/004359.html
we are planning to update to the next so
** Description changed:
Asking for a FFe exception to keep in sync (or merging) with Java
packages as uploaded to Debian, until the 18.10 release. As outlined in
https://lists.ubuntu.com/archives/ubuntu-
release/2018-March/004359.html
we are planning to update to the next so
We are now ok to sync gradle from Debian instead of merging. There are
pending patches for building it with openjdk-11, but those are to get
into Debian soon anyway. If they don't I will propose them in a separate
bug.
** Summary changed:
- Please merge gradle 4.4-2 from Debian
+ Please sync
Debdiff from Debian 4.4-2 which includes the patch for openjdk-11
support.
** Patch added: "gradle_4.4-2_debdiff_4.4-2ubuntu2.patch"
https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1794129/+attachment/5193777/+files/gradle_4.4-2_debdiff_4.4-2ubuntu2.patch
--
You received this bug
Did the testcase verification again for the new 0.130ubuntu3.5 bionic-
proposed upload and I confirm again that it works as expected.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a
Verified that initramfs-tools 0.130ubuntu3.5 in bionic-proposed now
works as expected after following through the testcase.
As expected orphaned old-dkms files are properly removed and no other
files are affected.
** Tags removed: verification-needed verification-needed-bionic
** Tags added:
Debdiff from Debian 2.4.15-3.
** Patch added: "groovy_2.4.15-3_debdiff_2.4.15-3ubuntu2.patch"
https://bugs.launchpad.net/ubuntu/+source/groovy/+bug/1794135/+attachment/5193757/+files/groovy_2.4.15-3_debdiff_2.4.15-3ubuntu2.patch
--
You received this bug notification because you are a member
Debdiff from version 2.4.15-1ubuntu1.
** Patch added: "groovy_2.4.15-1ubuntu1_debdiff_2.4.15-3ubuntu2.patch"
https://bugs.launchpad.net/ubuntu/+source/groovy/+bug/1794135/+attachment/5193726/+files/groovy_2.4.15-1ubuntu1_debdiff_2.4.15-3ubuntu2.patch
--
You received this bug notification
Debdiff from the previous one in cosmic-proposed (2.4.15-3ubuntu1).
** Patch added: "groovy_2.4.15-3ubuntu1_debdiff_2.4.15-3ubuntu2.patch"
https://bugs.launchpad.net/ubuntu/+source/groovy/+bug/1794135/+attachment/5193727/+files/groovy_2.4.15-3ubuntu1_debdiff_2.4.15-3ubuntu2.patch
--
You
I have prepared a new merge proposal that includes the right version
check in the postinst for Bionic. This has been uploaded to the Bionic
queue as 0.130ubuntu3.5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verification failed on Bionic when following the test case, the postinst
script has a bad check for the previous version of initramfs-tools it
expected - it is testing against a version from Xenial, not the Bionic
version.
** Tags removed: verification-needed verification-needed-bionic
** Tags
Verification done in Xenial and Bionic as per the test case. It works
fine and will prevent update-initramfs from being stuck in the described
scenarios.
** Tags removed: verification-needed-bionic verification-needed-xenial
** Tags added: verification-done-bionic verification-done-xenial
**
Verification done on Xenial by following the test case.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791959
one
* Standards-Version updated to 4.1.5
* Switch to debhelper level 11
* Use salsa.debian.org Vcs-* URLs
* Track and download the new releases from GitHub
-- Tiago Stürmer Daitx Fri, 21 Sep 2018
12:45:48 +
** Changed in: maven-compiler-plugin (Ubuntu)
Status: New =>
* Merge from Debian unstable. Remaining changes: (LP: #1794129)
- Replace HTTP URLs with local files: LP: #1765885.
- debian/control: build depends on -doc packages so javadoc can
properly link the apis.
- debian/patches/10_fix_javadoc_links.patch: include javadoc apis
locally, since
* Merge from Debian unstable. Remaining changes: (LP: #1794132)
- debian/rules: set JAVA_HOME to prevent compiler test failure.
- debian/patches/01-fix-wrong-junit-path.patch: patch wrong junit path in
compiler test.
** Patch added:
Public bug reported:
maven-compiler-plugin is currently at 3.6.2-2ubuntu2 in Cosmic and
Debian has released 3.8.0-1.
** Affects: maven-compiler-plugin (Ubuntu)
Importance: Undecided
Status: New
** Tags: cosmic patch upgrade-software-version
** Tags added: cosmic
Public bug reported:
groovy is currently at version 2.4.15-1ubuntu1 in Cosmic and Debian has
released 2.4.15-3.
** Affects: groovy (Ubuntu)
Importance: Undecided
Status: New
** Tags: cosmic upgrade-software-version
** Tags added: cosmic upgrade-software-version
--
You received
Public bug reported:
gradle is currently at 3.4.1-7ubuntu1 in Cosmic and Debian has released
4.4-2.
** Affects: gradle (Ubuntu)
Importance: Undecided
Status: New
** Tags: cosmic patch upgrade-software-version
** Tags added: cosmic upgrade-software-version
--
You received this
* Merge from Debian unstable. Remaining changes: (LP: #1794129)
- debian/patches/docs.patch: use default-jdk-doc instead of default-jdk
path for javaApiUrl in subprojects/docs/docs.gradle. LP: #1765866.
(Closes: #896436)
* debian/patches/gnu-style-release-flag-jdk9.patch: removed,
* Merge from Debian unstable. Remaining changes: (LP: #1794122)
- debian/control: add runtime dependency to default-jdk-doc.
- src/main/java/org/debian/gradle/DebianHelperPlugin.java: replace
javadoc link with default-jdk-doc directory instead of default-jdk.
LP: #1765883.
** Patch
Public bug reported:
gradle-debian-helper is currently at version 1.6ubuntu1 but Debian has
released 2.0.1. The Ubuntu patches causes a merge conflict with the new
version.
** Affects: gradle-debian-helper (Ubuntu)
Importance: Undecided
Status: New
** Tags: cosmic patch
> I have verified the fix with the latest stable jenkins release.
> It was in fact changed and local libjni/jna is no longer required.
Great, thanks for the feedback.
> Since the bug is fixed the only remaining question is if the handing
> of the system.so approach is a good idea and I think
** Changed in: libjna-java (Ubuntu Xenial)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662813
Title:
Libjna-jni uses wrong path on package installation on s390x
To
A few questions:
- Could you please provide the output of the apt-get purge call?
- If update-initramfs is called in it, could you please manually call it with
the verbose flag (-v) and attach the output?
- Does this only happen on the half-configured scenario?
I'm moving the status to
** Changed in: initramfs-tools (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792189
Title:
linux-firmware does not depend on initramfs-tools
To manage
> It seems that this issue was fixed on 1.136 (https://jenkins.io/changelog/)
> The s390x libs haven't been included in the shipped library prior to, a
> system install was required at that time.
Right, that would explain why it would not work prior to that.
> Anyhow, the locally installed
I installed jenkins 2.138.1 from http://pkg.jenkins.io/debian-stable and
while I was unable to reproduce the issue. I looked at its structure and
found out that they package their own jna.jar with its own
libjnidispatch.so libraries inside.
Their jna jar file is located at
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Could you please provide additional information on how to reproduce this
bug and the environment you are running it in?
For jitsi:
- where are you getting it from?
- how are you running it?
For the environment:
** Merge proposal unlinked:
https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355188
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791959
Title:
SRU as a merge proposal for both this and bug 1667512 available at
Bionic:
https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355189
Xenial:
https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355190
** No
SRU as a merge proposal for both this and bug 1791959 available at
Bionic:
https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355189
Xenial:
https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355190
--
You
** Summary changed:
- update-initramfs hangs on upgrade, dpkg unusable, unbootable system
+ [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg
unusable, unbootable system
** Summary changed:
- [SRU] update-initramfs should sync only the initram hangs on upgrade, dpkg
** Description changed:
- At least four users, including myself, are having an issue with update-
- initramfs hanging while updating ubuntu 16.04. The bug has been
- documented while attempting an update to multiple kernel versions (
- 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get
attaching cosmic patch
** Patch added: "initramfs-tools_0.131ubuntu10_debdiff_0.131ubuntu11.patch"
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187984/+files/initramfs-tools_0.131ubuntu10_debdiff_0.131ubuntu11.patch
--
You received this bug notification because
attaching bionic sru patch
** Patch added: "initramfs-tools_0.130ubuntu3.3_debdiff_0.130ubuntu3.4.patch"
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187983/+files/initramfs-tools_0.130ubuntu3.3_debdiff_0.130ubuntu3.4.patch
** Tags added: bionic
--
You received
attaching xenial sru patch
** Description changed:
[Impact]
If a dkms package is installed which has REMAKE_INITRD or the same setting
has been manually configured by a user then when a kernel is removed its
possible for an ".old-dkms" file to be left in /boot with no associated kernel.
** Summary changed:
- remove /boot/initrd.img-*.old-dkms files left behind
+ [SRU] remove orphaned initrd old-dkms files in /boot
** Description changed:
[Impact]
If a dkms package is installed which has REMAKE_INITRD or the same setting
has been manually configured by a user then when a
** Changed in: dkms (Ubuntu Xenial)
Status: New => Invalid
** Changed in: dkms (Ubuntu Bionic)
Status: New => Invalid
** Description changed:
[Impact]
If a dkms package is installed which has REMAKE_INITRD or the same setting
has been manually configured by a user then when a
** Changed in: dkms (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791959
Title:
remove /boot/initrd.img-*.old-dkms files left behind
To manage
** Changed in: dkms (Ubuntu)
Importance: Undecided => Medium
** Changed in: dkms (Ubuntu)
Status: New => Confirmed
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed
** Description changed:
[Impact]
If a dkms package is installed which has REMAKE_INITRD or the same setting
has be manually configured by a user then when a kernel is removed its possible
for an ".old-dkms" file to be left in /boot with no associated kernel.
bug 1515513 dealt with
Public bug reported:
[Impact]
If a dkms package is installed which has REMAKE_INITRD or the same setting has
be manually configured by a user then when a kernel is removed its possible for
an ".old-dkms" file to be left in /boot with no associated kernel.
bug 1515513 dealt with removing
Public bug reported:
Asking for a FFe exception to keep in sync (or merging) with Java
packages as uploaded to Debian, until the 18.10 release. As outlined in
https://lists.ubuntu.com/archives/ubuntu-
release/2018-March/004359.html
we are planning to update to the next so called OpenJDK LTS
** Summary changed:
- FFe: sync java packages from Debian to fix OpenJDK 9/10 issues
+ FFe: sync java packages from Debian to fix OpenJDK 9/10 issues in Bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> Regarding issue 2: I'm able to set up a fresh system
> with Jenkins on s390x.
> What information would you need to be able to
> reproduce this issue?
I need to know what java application you are trying to run, where was it
fetched from, how it was installed, and how it is being run. For each
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug is being tracked and a fix has been proposed to
the openjdk-lts package.
The package fix comments out
'assistive_technologies=org.GNOME.Accessibility.AtkWrapper'
in
Your last comment indicated 2 different errors:
1) The link to libjnidispatch.so
Is the aforementioned link to libjnidispatch.so created by a supported Ubuntu
package? If so, which package? You should run "dpkg -S " to check
that. This link this not seem to be setup by libjna, so I wonder how
Public bug reported:
maven relies on surefire for running tests and surefire depends on
libcommons-lang3-java. So whenever libcommons-lang3-java is updated
there are 2 versions in the classpath during the testing: the old
version in the deb package from surefire's dependency and the new
version
attaching debdiff that prevents tests from being run during the build
** Patch added: "libcommons-lang3-java_3.7-1_debdiff_3.7-1ubuntu1.patch"
** Tags added: bionic xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667512
Title:
update-initramfs hangs on upgrade, dpkg unusable, unbootable system
To manage notifications about this bug
** Tags added: bionic cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785896
Title:
testng fails due to missing guava dependency
To manage notifications about this bug go to:
** Bug watch added: Debian Bug tracker #905675
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905675
** Also affects: testng (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905675
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Public bug reported:
While running OpenJDK 10 tests I noticed that quite a few tests that
depend on testng fail due to a missing guava class.
The package libguava-java has the class but it is not declared as a
dependency.
The bug has been reported upstream back in 2016 [1] and fixed a few days
Public bug reported:
Debian has updated lshw from 02.18-0.1 to 02.18.85-0.1 and the result
should be merged into Ubuntu.
Please take care of the need to set the VERSION variable when calling
make, otherwise the version is set as unknown (bug 1752523).
Since the new version sources do not
I tested lshw 02.18-0.1ubuntu6.18.04.1 in a Bionic schroot and can
confirm that the proposed package fixes both issues reported in this
SRU, as per the test case.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
** Bug watch added: Debian
Hi Lukasz,
I agree that depending on someone setting it manually on the rules file
is not optimal while way better than "unknown".
This is not really an issue right now: if you look at the rules file you
will notice that 'uver' is used to set the 'srcdir', which would cause
the package to FTBFS
Using the test case I confirm that the PATH and JAVA_HOME are now
working as expected and no longer set to invalid values.
The test cases in bug 1771363 and bug 1769013 are also working
correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771815
Title:
Please merge
Using the tested I confirm that a previous PKCS12 keystore cacerts was
successfully converted to a JKS format. Other users reported the same in
bug 1770553.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, the report indicates that an error report from openjdk was created at
/hs_err_pid8655.log, could you please attach any hs_err log files that you
Public bug reported:
>From https://lists.launchpad.net/openjdk/msg13098.html
Hello,
I maintain an Oracle Java 10 PPA [1] (based on Andrew's scripts from
webupd8.org but modified for Oracle Java 10) and I noticed that OpenJDK
packages in Debian and Ubuntu have "Conflicts:
** Description changed:
- There's a new ca-certificates-java package in debian unstable versioned
- 20180516 which conflicts with Ubuntu's delta in cosmic, version
- 20180413ubuntu1 [1], and requires a merge.
+ [Original Merge Description]
+ There's a new ca-certificates-java package in debian
** Description changed:
[Impact]
Any user doing a new install can be affected as soon as they install any
openjdk-11 package.
[Cause]
The ca-certificate-java version 20170930 (or earlier) used OpenJDK's default
keystore to create /etc/ssl/certs/java/cacerts - if the file already
** Description changed:
+ [Impact]
+ Any user already affected by the issue described in bug 1739631 won't benefit
from the fix as that fix only prevents the issue from happening in new installs.
+
+ [Cause]
+ Same as described in bug 1739631 and copied here.
+
+ The ca-certificate-java
** Description changed:
- There's a new ca-certificates-java package in debian unstable versioned
- 20180413 which conflicts with cosmic's version 20170930ubuntu1 [1] and
- requires a merge.
+ [Original Merge description]
+ There's a new ca-certificates-java package in debian unstable versioned
** Description changed:
- I ran into a problem after doing approximately the following on an
- install of Ubuntu 17.10:
+ [Impact]
+ Any user doing a new install can be affected as soon as they install any
openjdk-11 package.
+
+ [Cause]
+ The ca-certificate-java version 20170930 (or earlier)
By default the package install libjnidispatch under /usr/lib/s390x-
linux-gnu/jni/libjnidispatch.system.so and as far as I can see there's
no reason to have a file/link in /usr/lib/s390x-linux-
gnu/libjnidispatch.so.
Still, I was able to reproduce the error which indicates that you might
have a
Before removing the "dangling" file you might want to check if it is by
any change associated with a package by calling "dpkg -S ".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662813
Title:
This is going to be included in OpenJDK together with the 10.0.2
security update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776332
Title:
[POWER9][Ubuntu 18.04] OpenJDK 10+ can halt when
Unfortunately, we cannot work on this bug because your description
didn't include enough information on how this affects OpenJDK-8. We'd be
grateful if you would then provide a more complete description of the
problem. For now settings this as invalid for OpenJDK-8.
** Changed in: openjdk-8
Could you please add:
1. the specific steps to reproduce this bug
2. which Ubuntu versions that are affected
for now I'm going to set this as incomplete.
** Changed in: libjna-java (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Attaching debdiff from Cosmic current version (ie. contains only the
changelog entry).
** Patch added:
"ca-certificates-java_20180516ubuntu1_debdiff_20180516ubuntu1.18.04.1.patch"
Uploading new debdiff with the ca-certificate-java backport from Cosmic
current version (20180516ubuntu1) to Bionic. This backport has been
versioned as 20180516ubuntu1.18.04.1. The only change from Cosmic is a
changelog entry to update the version and a mention to the backport.
The debdiff was
** Patch added:
"ca-certificates-java_20170930ubuntu1_debdiff_20180516ubuntu1.18.04.1.patch"
https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1770553/+attachment/5163377/+files/ca-certificates-java_20170930ubuntu1_debdiff_20180516ubuntu1.18.04.1.patch
--
You received this
Attaching debdiff containing the fixes for the Bionic SRU.
** Description changed:
- == Comment: #0 - PAVITHRA R. PRAKASH - 2018-03-01
00:30:14 ==
- ---Problem Description---
+ [Impact]
- Ubuntu 18.04 [ P9 WSP DD2.2 ]: lshw version is displayed as "unknown"
- and -json option is not
debdiff for Cosmic that includes:
- patch for '-json' help parameter
- patch for getting the version from a build variable
- change in debian/rules to set the VERSION variable
** Patch added: "shw_02.18-0.1ubuntu6_debdiff_02.18-0.1ubuntu7.patch"
Attaching the bt full backtrace provided by the Huehner to the IcedTea
bug.
It indicates that the bug is triggered in the file
hotspot/src/share/vm/classfile/classLoaderDependencies.cpp:43 which is
exclusive to jdk7u [1] and was introduced by the backport of "8189123:
More consistent
I installed tomcat7 and tested a couple of very simple hibernate samples
from around the web, none were able to trigger this issue.
Please see if you can find a simpler reproducer and update the bug with
the required steps to reproduce it. I'm setting it as incomplete for
now.
** Changed in:
I have been able to reproduce this on amd64 and i386 using the zero
package. I tried to reproduce it on a powerpc vm but as I was unable to
boot anything other than a single-core vm, which was way too slow to do
any testing - just the ubuntu install took way too long, there would be
no way I would
** Changed in: openjdk-7 (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/1777933
Title:
openjdk-7 7u181-2.6.14-0ubuntu0.1 zerovm causes eclipse to crash
To
IcedTea 2.6.14 has backported a fix for the exec guard issue and will be
available in Trusty's openjdk-7 version 7u181-2.6.14-0ubuntu0.1.
The fix for OpenJDK-8 will be included in the next security update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Verified that the build works on bionic for ceph 12.2.4-0ubuntu1.1
(currently in bionic-proposed).
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Verified that the test case works in a bionic chroot for ceph
12.2.4-0ubuntu1.1 (currently in bionic-proposed).
Tested both openjdk-11 and openjdk-8 and got the expected:
FAILURES!!!
Tests run: 27, Failures: 4
message. Also verified that failures are the same as in the test case.
--
You
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766998
Title:
[SRU] ceph: replace
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I have been trying to track down which component/application is actually
responsible for creating and maintaining /com/ubuntu/user-interface
/scale-factor, but so far no luck.
It seems to be related to Unity
The bug was opened at the main bugs.java.com bug tracking.
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8203627
Please note that only OpenJDK Authors (and above) and sign in and update
the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have reported it under https://bugreport.java.com and got the bug
number 9053855 - it is now under review by Oracle, I will update it here
when they make the report public.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
201 - 300 of 839 matches
Mail list logo
