;summary.txt"), this way
it will only accept the smaller set of files when compared to accepting any
file.
** Affects: jtreg (Ubuntu)
Importance: Wishlist
Assignee: Tiago Stürmer Daitx (tdaitx)
Status: Confirmed
** Changed in: jtreg (Ubuntu)
Importance: Undecided =>
Public bug reported:
[Impact]
jtreg version 5.0 or later added a '-match' option that is basically the
reverse of '-exclude': it allows the user to set a file containing the tests
that should be run - files not on the list are 'excluded'.
As an OpenJDK maintainer I would like to have the option
> 7) Execute "gdb --ex 'file /bin/cat' --ex 'core-file /tmp/cat.core'
--ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug'"
Try setting the debug-file-directory first, it should work.
gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug'
--ex 'file /bin/cat' --ex 'core
I tried the testcase from comment #12 in Focal and Hirsute and it worked
just fine:
$ gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug'
--ex 'file /bin/cat' --ex 'core-file /tmp/cat.core'
Type "apropos word" to search for commands related to "word".
Reading symbols from
I was able to reproduce what Brian is reporting here.
If the -dbgsym for the package is installed, gdb works and reports that it is
reading from the /tmp/dbgsym path. When -dbgsym package is not installed then
it fails with the
'could not find '.gnu_debugaltlink' file for ...' message
--
You
So the issue is: if there is a .gnu_debugaltlink GDB will try to load
that file and throw an error if it can't. That path is absolute and GDB
does _not_ look for that path/file anywhere else, not even inside
'debug-file-directory'.
GDB seems to only look at section .gnu_debugaltlink in debug/.buil
@sergiodj many thanks for the help here
It was a dwz man page somewhere that made me think we might be misusing
.gnu_debugaltlink somehow (didn't even know about dh_dwz), but on a
quick search I couldn't understand how the path was supposed to look
like so I could test that idea with my replace-al
** 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 ma
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
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: open
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 classloading"
** Also affects: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Also affects: jtreg (Ubuntu Bionic)
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/1803628
Title:
jtreg fails to run under openjdk-8 due to api incompat
** Also affects: testng (Ubuntu Bionic)
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/1785896
Title:
testng fails due to missing guava dependency
To mana
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 /etc/java-11-openjdk/accessibility.prope
> 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 of
** 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.
https://bugs.launchpad.net
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 ve
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 initrd.
** 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 remov
** 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 i
** 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 notifica
** 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
** 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 ke
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 t
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.
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 yo
** 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 beca
** 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]
Bin
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 nece
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.
T
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 grad
** 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 call
** 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 call
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"
https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1791716/+attachment/519624
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 t
** 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 Ubun
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 d
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:
** 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:
https://bugs.launchpad.net/ubun
** 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 t
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: "clojure1.8_1.8.0-7_debdiff_1.8.0-7
Public bug reported:
[Impact]
openjdk-9 introduced a few api changes that result in runtime errors
when trying to run the java classes under openjdk 8 (or earlier) even
when -source/-target are properly set.
The fix is to build such code using the new openjdk-9 flag "--release"
instead of the "-
** Summary changed:
- jtreg fails due to api incompatibility with openjdk-9 or later
+ jtreg fails to run under openjdk-8 due to api incompatibility with openjdk-9
or later
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Debdiff with the fix for Cosmic.
** Bug watch added: Debian Bug tracker #913853
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913853
** Also affects: jtreg (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913853
Importance: Unknown
Status: Unknown
** Patch added
** Description changed:
[Impact]
-
- openjdk-9 introduced a few api changes that result in runtime errors
- when trying to run the java classes under openjdk 8 (or earlier) even
- when -source/-target are properly set.
+ openjdk-9 introduced a few api changes that result in runtime errors when
Hi Timo, thanks for helping move this SRU ahead.
I have tested it as per the testcase in a Cosmic chroot and I can confirm that:
1. jtreg 4.2-b13-1ubuntu0.1 fixes this issue when running under openjdk-8.
2. jtreg 4.2-b13-1ubuntu0.1 does not introduces regressions when running under
openjdk-11, as
** Also affects: openjdk-lts (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/1800792
Title:
Update to openjdk-8 8u181-b13-1ubuntu0.18.04.1 and open
** Summary changed:
- Update to 8u181-b13-1ubuntu0.18.04.1 breaks Maven builds
+ Update to openjdk-8 8u181-b13-1ubuntu0.18.04.1 and openjdk-lts
10.0.2+13-1ubuntu0.18.04.3 breaks Maven builds
** Description changed:
Today both the OpenJDK 8 and 11 packages were updated. In the case of
- OpenJD
*** This bug is a duplicate of bug 1800792 ***
https://bugs.launchpad.net/bugs/1800792
** This bug has been marked a duplicate of bug 1800792
Update to openjdk-8 8u181-b13-1ubuntu0.18.04.1 and openjdk-lts
10.0.2+13-1ubuntu0.18.04.3 breaks Maven builds
--
You received this bug notificatio
*** This bug is a duplicate of bug 1800792 ***
https://bugs.launchpad.net/bugs/1800792
** This bug has been marked a duplicate of bug 1800792
Update to openjdk-8 8u181-b13-1ubuntu0.18.04.1 and openjdk-lts
10.0.2+13-1ubuntu0.18.04.3 breaks Maven builds
--
You received this bug notificatio
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I have updated the status of the bug to reflect the affected Ubuntu
releases for both openjdk-8 (Xenial, Bionic, Cosmic, and Disco) and
openjdk-10 (Bionic). New packages are under test and will be released
soon by
** Changed in: livecd-rootfs (Ubuntu Bionic)
Status: New => In Progress
** Changed in: livecd-rootfs (Ubuntu Bionic)
Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: openjdk-lts (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: openjdk-lts (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** 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 upd
** 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
un
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 re
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 long
** 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
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:
-
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 ./WEB-INF/lib/jna-4.5.2.
> 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 libra
** 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
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 Incomplete
** 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
> 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 that
* 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 ad
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 upgrade-so
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 b
* 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, applied
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:
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 upgrade-software-
* 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: "maven-compiler-plugin_3.8.0-1_debdiff_3.8.0-1ubuntu1.pa
* 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
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 =>
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
Title
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
** Tags
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 add
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.
https://bugs.launchpad
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 rece
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 bec
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
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: veri
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 me
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 notif
** Changed in: tomcat9 (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823125
Title:
tomcat9 fails to install in 18.04
To manage notificat
Sebastian,
thank you for taking the time to report this bug and helping to make
Ubuntu better.
For a systemd service you can easily override it and to modify/add
options. As an example, you should be able to achieve a similar result
to what you describe by using:
/etc/systemd/system/tomcat.servi
*** This bug is a duplicate of bug 1770278 ***
https://bugs.launchpad.net/bugs/1770278
** This bug has been marked a duplicate of bug 1770278
Swing applications look strange with OpenJDK-11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 1807602 ***
https://bugs.launchpad.net/bugs/1807602
> The fix for LTS ()
> is still needed.
>
> Please start the SRU/whatever bug-fixing procedure for 18.04 (bionic beaver).
Notice that backport fixes might come only after they have been
confirmed to
Marked bug #1739476 as a duplicate of this one as both seem to be caused
by the same upstream bug - keeping this one open and marking the other
one as duplicate because this is the one tracked on the package's
changelog.
** Bug watch added: Debian Bug tracker #896118
https://bugs.debian.org/cgi
*** This bug is a duplicate of bug 1807602 ***
https://bugs.launchpad.net/bugs/1807602
It seems that this bug has been duplicated in bug #1807602, marking it
as such. Please reopen if they are not in fact the same.
** This bug has been marked a duplicate of bug 1807602
Scilab does not star
Could you please take a look at bug #1770278 and look if the screenshot
with the artifacts is the same/similar to what you are seeing here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821768
Title:
There has been some recent updates in the upstream bug [1,2] - too bad
that Launchpad cannot track it.
>From January 3rd:
"This is an issue with gtk version 3.20 and later. gtk has made some major
changes in their theme handling in gtk 3.20 and applications need to change to
adapt to those chang
Possible duplicate report of bug #1770278
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816791
Title:
18.04 backport doesn't properly display menu entries
To manage notifications about this bug go
A comparison between GTK3 (with and without the fix) and GTK 2.
Top: GTK3 running under OpenJDK 11 with the fix applied (see how JComboBox is
still broken)
Center: GTK3 without the fix (as originally reported)
Bottom: GTK2, looking ok
** Attachment added:
"bionic-jfilechooser-demo_gtk3-fix-top_g
Comparison of jabref from bionic-proposed running under openjdk-11 with
the upstream fix under GTK3 (top) and GTK2 (bottom).
$ apt policy jabref
jabref:
Installed: 3.8.2+ds-12~18.04
Candidate: 3.8.2+ds-12~18.04
Version table:
*** 3.8.2+ds-12~18.04 500
500 http://archive.ubuntu.com/u
I applied the fix, build a new openjdk for the test and saw a bit of an
improvement, but some widgets are still looking weird. JComboBox from
JFileChooser still looks wrong.
The jabref app has some weird spacing in various widgets, including its
toolbar. Meanwhile it also has the broken JComboBox
jabref general preferences window running under openjdk-11 with the upstream
fix applied:
top: gtk2
bottom: gtk3
** Attachment added: "bionic_jabreb_preferences-window-general.png"
https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1770278/+attachment/5249646/+files/bionic_jabreb_pref
jabref entrytable preferences window running under openjdk-11 with the
upstream fix applied, JTable is still badly draw (no left border, as if
cropped) and the select box has no borders.
top: gtk2
bottom: gtk3
** Attachment added: "bionic_jabref_preferences-table-window.png"
https://bugs.laun
Public bug reported:
When running scilab under openjdk-11 it fails to open the preferences windows
with the following error (see bellow for the full output):
ERROR: 'Could not compile stylesheet'
FATAL ERROR: 'The xsl:import element children must precede all other element
children of an xsl:st
1 - 100 of 760 matches
Mail list logo
