[Bug 1915009] Re: [MIR] libmd (dependency of libbsd)
** Changed in: libmd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915009 Title: [MIR] libmd (dependency of libbsd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmd/+bug/1915009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915009] Re: [MIR] libmd (dependency of libbsd)
** Description changed:
- [Summary]
- TODO: WRITE - The essence of the review result from the MIR POV
- TODO: This does need a security review, so I'll assign ubuntu-security
- TODO: List of specific binary packages to be promoted to main:
+ [Availability]
+ libmd has been on Universe since Xenial and builds on all supported archs.
Hirsute currently has 1.0.3-3.
- Notes:
- TODO: - add todos, issues or special cases to discuss
- Required TODOs:
- TODO - TBD
- Recommended TODOs:
- TODO - TBD
+ [Rationale]
+ libbsb has a new dependency on libmd since 0.11.1-1 (0.10 or earlier didn't)
+ - libbsd0 depends on libmd0
+ - libbsd build-depends on libmd-dev
- [Duplication]
- TODO: There is no other package in main providing the same functionality.
+
+ [Security]
+ - found no CVEs related to libmd on Mitre, Openwall, and Ubuntu CVE tracker
(main, universe, and tracker).
+ - no suid binaries on libmd0
+ - package provides no service files
+ - package does not require network (no open ports)
+
+
+ [Quality assurance]
+ - libmd0 1.0.3-3 depends only on libc6 (ie. no weird deps)
+ - libmd 1.0.3-3 build depends only on debhelper-compat
+ - no bug has ever been logged for libmd in both launchpad[1] and debian[2]
+ - homepage lists no upstream bug tracker [3]
+ - upstream maintainer is Guillem Jover
+ - package ships with a testsuite
+ - testsuite does not need network nor weird hardware
+ - testsuite is run during build
+ - has autopkgtests [4]
+ - autopkgtest fails on i386 (not a blocker)
+ - autopkgtest succeeded on amd64, ppc64el, s390x
+ - package has a debian/watch file
+ - 'lintian --pedantic' indicates no packaging issues
+
[Dependencies]
- OK:
- TODO - no other Dependencies to MIR due to this
- TODO (use tools: check-mir, seeded-in-ubuntu, reverse-depends)
- TODO - no -dev/-debug/-doc packages that need exclusion
+ - libmd0 1.0.3-3 depends: libc6
+ - libmd 1.0.3-3 build-depends: debhelper-compat
- TODO: Problems:
- [Embedded sources and static linking]
- OK:
- TODO: - no embedded source present
- TODO: - no static linking
+ [Standards compliance]
+ Package meets Debian Policy 4.5.1 (latest as of 2021-02-09).
+ Package meets FHS.
- TODO: Problems:
+ [Maintenance]
+ Package is small and well maintained in Debian by it's upstream main
developer (Guillem Jover).
- [Security]
- OK:
- TODO: - history of CVEs does not look concerning
- TODO: - does not run a daemon as root
- TODO: - does not use webkit1,2
- TODO: - does not use lib*v8 directly
- TODO: - does not parse data formats
- TODO: - does not open a port
- TODO: - does not process arbitrary web content
- TODO: - does not use centralized online accounts
- TODO: - does not integrate arbitrary javascript into the desktop
- TODO: - does not deal with system authentication (eg, pam), etc)
- TODO: Problems:
+ [Background information]
+ Package description is correct and succint:
+ 'The libmd library provides various
+ message digest ("hash") functions,
+ as found on various BSDs on a
+ library with the same name and with a
+ compatible API.'
- [Common blockers]
- OK:
- TODO: - does not FTBFS currently
- TODO: - does have a test suite that runs at build time
- TODO: - test suite fails will fail the build upon error.
- TODO: - does have a test suite that runs as autopkgtest
- TODO: - The package has a team bug subscriber
- TODO: - no translation present, but none needed for this case (user visible)?
- TODO: - not a python/go package, no extra constraints to consider int hat
regard
- TODO: - no new python2 dependency
- TODO: - Python package that is using dh_python
- TODO: - Go package that uses dh-golang
- TODO: Problems:
+ [References]
- [Packaging red flags]
- OK:
- TODO: - Ubuntu does not carry a delta
- TODO: - Ubuntu does carry a delta, but it is reasonable and maintenance under
control
- TODO: - symbols tracking is in place
- TODO: - symbols tracking not applicable for this kind of code.
- TODO: - d/watch is present and looks ok
- TODO: - Upstream update history is (good/slow/sporadic)
- TODO: - Debian/Ubuntu update history is (good/slow/sporadic)
- TODO: - the current release is packaged
- TODO: - promoting this does not seem to cause issues for MOTUs that so far
- TODO: maintained the package
- TODO: - no massive Lintian warnings
- TODO: - d/rules is rather clean
- TODO: - Does not have Built-Using
- TODO: - Go Package that follows the Debian Go packaging guidelines
- TODO: (see https://go-team.pages.debian.net/packaging.html)
+ [1]
+
https://bugs.launchpad.net/ubuntu/+source/libmd/+bugs?search=Search%3Alist=NEW%3Alist=OPINION%3Alist=INVALID%3Alist=WONTFIX%3Alist=EXPIRED%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=FIXCOMMITTED%3Alist=FIXRELEASED%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE_option=any_combinator=ANY
+ .status_upstream-empty-marker=1
- TODO: Problems:
-
- [Upstream red flags]
- OK:
- TODO: - no Errors/warnings during the build
- TODO: - no incautious
[Bug 1915009] Re: [MIR] libmd (dependency of libbsd)
** Description changed: - [MIR] libmd (dependency of libbsd) + [Summary] + TODO: WRITE - The essence of the review result from the MIR POV + TODO: This does need a security review, so I'll assign ubuntu-security + TODO: List of specific binary packages to be promoted to main: + + Notes: + TODO: - add todos, issues or special cases to discuss + Required TODOs: + TODO - TBD + Recommended TODOs: + TODO - TBD + + [Duplication] + TODO: There is no other package in main providing the same functionality. + + [Dependencies] + OK: + TODO - no other Dependencies to MIR due to this + TODO (use tools: check-mir, seeded-in-ubuntu, reverse-depends) + TODO - no -dev/-debug/-doc packages that need exclusion + + TODO: Problems: + + [Embedded sources and static linking] + OK: + TODO: - no embedded source present + TODO: - no static linking + + TODO: Problems: + + [Security] + OK: + TODO: - history of CVEs does not look concerning + TODO: - does not run a daemon as root + TODO: - does not use webkit1,2 + TODO: - does not use lib*v8 directly + TODO: - does not parse data formats + TODO: - does not open a port + TODO: - does not process arbitrary web content + TODO: - does not use centralized online accounts + TODO: - does not integrate arbitrary javascript into the desktop + TODO: - does not deal with system authentication (eg, pam), etc) + + TODO: Problems: + + [Common blockers] + OK: + TODO: - does not FTBFS currently + TODO: - does have a test suite that runs at build time + TODO: - test suite fails will fail the build upon error. + TODO: - does have a test suite that runs as autopkgtest + TODO: - The package has a team bug subscriber + TODO: - no translation present, but none needed for this case (user visible)? + TODO: - not a python/go package, no extra constraints to consider int hat regard + TODO: - no new python2 dependency + TODO: - Python package that is using dh_python + TODO: - Go package that uses dh-golang + + TODO: Problems: + + [Packaging red flags] + OK: + TODO: - Ubuntu does not carry a delta + TODO: - Ubuntu does carry a delta, but it is reasonable and maintenance under control + TODO: - symbols tracking is in place + TODO: - symbols tracking not applicable for this kind of code. + TODO: - d/watch is present and looks ok + TODO: - Upstream update history is (good/slow/sporadic) + TODO: - Debian/Ubuntu update history is (good/slow/sporadic) + TODO: - the current release is packaged + TODO: - promoting this does not seem to cause issues for MOTUs that so far + TODO: maintained the package + TODO: - no massive Lintian warnings + TODO: - d/rules is rather clean + TODO: - Does not have Built-Using + TODO: - Go Package that follows the Debian Go packaging guidelines + TODO: (see https://go-team.pages.debian.net/packaging.html) + + TODO: Problems: + + [Upstream red flags] + OK: + TODO: - no Errors/warnings during the build + TODO: - no incautious use of malloc/sprintf (as far as I can check it) + TODO: - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH + TODO: - no use of user nobody + TODO: - no use of setuid + TODO: - no important open bugs (crashers, etc) in Debian or Ubuntu + TODO: - no dependency on webkit, qtwebkit, seed or libgoa-* + TODO: - not part of the UI for extra checks + + TODO: Problems: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915009 Title: [MIR] libmd (dependency of libbsd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmd/+bug/1915009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914076] Re: Sync pdfsam 4.2.2-1 (universe) from Debian unstable (main)
This bug was fixed in the package pdfsam - 4.2.2-1 --- pdfsam (4.2.2-1) unstable; urgency=medium * New upstream version 4.2.2. -- Markus Koschany Sun, 31 Jan 2021 16:05:13 +0100 pdfsam (4.2.1-1) unstable; urgency=medium * New upstream version 4.2.1. * Declare compliance with Debian Policy 4.5.1. -- Markus Koschany Tue, 24 Nov 2020 01:26:23 +0100 pdfsam (4.2.0-2) unstable; urgency=medium * Fix stackoverflow error when closing the application. (Closes: #973125) -- Markus Koschany Mon, 09 Nov 2020 13:26:44 +0100 pdfsam (4.2.0-1) unstable; urgency=medium * New upstream version 4.2.0. * Remove obsolete sejda-injector symlink. * Drop sejda-4.1-compatibility.patch. Fixed upstream. -- Markus Koschany Sat, 07 Nov 2020 23:41:52 +0100 pdfsam (4.1.4-1) unstable; urgency=medium * New upstream version 4.1.4 * Switch to debhelper-compat = 13 * Declare compliance with Debian Policy 4.5.0. * Tighten build-dependency on libsejda-eventstudio-java. * Build-depend on libhibernate-validator4-java. -- Markus Koschany Mon, 26 Oct 2020 15:14:51 +0100 ** Changed in: pdfsam (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.net/bugs/1914076 Title: Sync pdfsam 4.2.2-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfsam/+bug/1914076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913476] Re: /usr/bin/update-manager:TypeError:/usr/bin/update-manager@118:start_update:start_available:refresh_cache:update:_make_groups:__contains__
Patch for Focal is ok, the one on Groovy had an unnecessary removal of .bzrignore so I didn't apply those bits. Build and lintian are ok for both Focal and Groovy. ** Changed in: update-manager (Ubuntu) Assignee: Tiago Stürmer Daitx (tdaitx) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913476 Title: /usr/bin/update-manager:TypeError:/usr/bin/update- manager@118:start_update:start_available:refresh_cache:update:_make_groups:__contains__ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1913476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913476] Re: /usr/bin/update-manager:TypeError:/usr/bin/update-manager@118:start_update:start_available:refresh_cache:update:_make_groups:__contains__
** Changed in: update-manager (Ubuntu) Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx) ** Changed in: update-manager (Ubuntu Focal) Status: New => In Progress ** Changed in: update-manager (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913476 Title: /usr/bin/update-manager:TypeError:/usr/bin/update- manager@118:start_update:start_available:refresh_cache:update:_make_groups:__contains__ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1913476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797101] Re: incompatibility with libxmlsec
** Also affects: xmlsec1 (Ubuntu) Importance: Undecided Status: New ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797101 Title: incompatibility with libxmlsec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1797101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912158] Re: undefined symbol: JVM_IsUseContainerSupport, version SUNWprivate_1.1
Thank you for taking the time to report this bug and helping to make Ubuntu better. The openjdk-11-jre-dcevm seems to quite often require updates to match the lastest openjdk-11 versions, but the released versions I can see from the archive are usually outdated. Please run the following command and add a comment with the output here so we can check exactly what versions you have been using: $ apt policy openjdk-11-jre openjdk-11-jre-dcevm Many thanks ** Changed in: openjdk-11-jre-dcevm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912158 Title: undefined symbol: JVM_IsUseContainerSupport, version SUNWprivate_1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-11-jre-dcevm/+bug/1912158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912158] Re: undefined symbol: JVM_IsUseContainerSupport, version SUNWprivate_1.1
** Bug watch added: Debian Bug tracker #942876 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942876 ** Also affects: openjdk-11-jre-dcevm (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942876 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912158 Title: undefined symbol: JVM_IsUseContainerSupport, version SUNWprivate_1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-11-jre-dcevm/+bug/1912158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761013] Re: java crashed with SIGABRT in ImageStrings::find()
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 1761013 and any other logs that are relevant for this particular issue, specially the generated core file. ** Changed in: openjdk-lts (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761013 Title: java crashed with SIGABRT in ImageStrings::find() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1761013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
@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-altlink-section-hack. And if GDB can support looking for .dwz on the debug-file-drectory even with hardcoded paths, all the better. Many, many thanks for taking the time to look at this and come up with these 2 solutions. We really appreciate it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818918 Title: gdb doesn't search in debug-file-directory for .gnu_debugaltlink To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
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/.build- id/nn/nn.debug, it does not seem to use that section from the binary at all. Due to that, another workaround is to modify that section to point to the 'right' place: 1) use objcopy to dump .gnu_debugaltlink from debug/.build-id/nn/nn.debug into a file 2) use sed to modify the path in the dump file 3) use objcopy to update .gnu_debugaltlink section in debug/.build-id/nn/nn.debug As in: $ objcopy --dump-section .gnu_debugaltlink=altlink /tmp/dbgsym/usr/lib/debug/.build-id/76/e9f820204912084fd156c593b2c92f1a4b51f1.debug $ sed -i 's:^:/tmp/dbgsym:' altlink $ objcopy --update-section .gnu_debugaltlink=altlink /tmp/dbgsym/usr/lib/debug/.build-id/76/e9f820204912084fd156c593b2c92f1a4b51f1.debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818918 Title: gdb doesn't search in debug-file-directory for .gnu_debugaltlink To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818918 Title: gdb doesn't search in debug-file-directory for .gnu_debugaltlink To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
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 /bin/cat... Reading symbols from /tmp/dbgsym/usr/lib/debug/.build-id/b3/57ed53c8c9cb1a312f83b28982304effae0135.debug... [New LWP 2094475] Core was generated by `/bin/cat'. Program terminated with signal SIGTSTP, Stopped (user). #0 0x77eb6142 in __GI___libc_read (fd=fd@entry=0, buf=buf@entry=0x77faa000, nbytes=nbytes@entry=131072) at ../sysdeps/unix/sysv/linux/read.c:26 # hirsute $ gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug' --ex 'file /bin/cat' --ex 'core-file /tmp/cat.core' Reading symbols from /bin/cat... Reading symbols from /tmp/dbgsym/usr/lib/debug/.build-id/fb/a7cee6aca864b8f79dfaa8a267855333b445c1.debug... [New LWP 14651] Core was generated by `/usr/bin/cat'. Program terminated with signal SIGTSTP, Stopped (user). #0 0x77edccb2 in __GI___libc_read (fd=fd@entry=0, buf=buf@entry=0x7791e000, nbytes=nbytes@entry=131072) at ../sysdeps/unix/sysv/linux/read.c:26 26 ../sysdeps/unix/sysv/linux/read.c: No such file or directory. If the dbgsym is installed and I use (with intentional typo): set debug-file-directory /tmp/dbgsym/usr/lib/debugnot:/usr/lib/debug it then loads symbols correctly from /usr/lib/debug Note, this was tested under Focal (host) and Hirsute (lxd container). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818918 Title: gdb doesn't search in debug-file-directory for .gnu_debugaltlink To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
> 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-file /tmp/cat.core' Still, this does not seem to invalidate the original bug report or the one in comment #4, as they are setting 'file' and 'core' last. It is just that comment #12 does not seem to indicate a valid reproducer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818918 Title: gdb doesn't search in debug-file-directory for .gnu_debugaltlink To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1818918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904072] [NEW] jtdiff on xenial and bionic should accept an include file list
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 to set a 'include' list of tests to be run, so I can easily separate tests between 'stable' and 'flaky' tests by defining a list of tests that are known to always pass (and where we actually care for regressions). [Test Case] 1) Create an inclusion list with a single line $ echo "compiler/aot/RecompilationTest.java" > /tmp/include-list 2) Run the openjdk-lts hotspot test with -watch $ jtreg -workDir:"/tmp/work" -reportDir:"/tmp/report" -jdk:/usr/lib/jvm/default-java -match:/tmp/include-list -dir:/tmp/openjdk-lts/test/hotspot/jtreg -listtests :hotspot_compiler Testsuite: /tmp/openjdk-lts/test/hotspot/jtreg compiler/aot/RecompilationTest.java Tests found: 1 jtreg from xenial and bionic currently fail as they have no support for '-match'. [Where problems could occur] This adds code that has been highly tested on jtreg 5.0+ to previous versions, so it could possibly trigger different code paths and regress in some corner cases. This would probably show up as previously excluded tests no longer being excluded, since exclusion is now defined as "!match". Any tool that directly calls 'jtreg -match' - instead of looking for its version - might consider this is a newer version of jtreg and assume it can also user other newer features, which would fail. [Other Info] ** Affects: jtreg (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/1904072 Title: jtdiff on xenial and bionic should accept an include file list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jtreg/+bug/1904072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904070] [NEW] jdiff should be less strict about the summary.txt filename
Public bug reported:
[Impact]
The jtdiff tool allows the user to point to a jtreg test report file, but it
will reject any file that is not named 'summary.txt'. This completely prevents
comparing 2 valid test summary files in the same directory, as they can't both
be named summary.txt.
As an OpenJDK maintainer I usually do comparisons between different test
runs and this restriction requires me to put each file under a separate
directory, which usually adds extra unnecessary logic to scripts that
automate such comparisons. I do use it in automated scripts in jenkins
and autopkgtests, so I would like to see this backported to Bionic,
Focal, and Groovy.
Ideally jtdiff should not care about the file name at all, either it can
open it or not. Still, as accepting *any* file is a significant behavior
change, I proposed that it accepts all files "ending" in summary.txt -
it is also a very minimal and easy change to do on the source code
(using String.endsWith instead of String.equals).
[Test Case]
1) Create a summary.txt file with the one-line content of:
api/java_applet/Applet/AccessibleApplet/index.html#AccessibleContext
Passed. test cases: 1; all passed
2) Copy that file to second-summary.txt
3) Try to use jtdiff to compare both files, see that it fails
$ jtdiff -format:text second-summary.txt summary.txt
Error: File not recognized: second-summary.txt
4) And the exit code is 2
$ echo $?
2
Expected:
jtdiff should accept any file name that ends with 'summary.txt'.
[Where problems could occur]
- On the Ubuntu archive it should not cause any problems, as only openjdk-8 and
openjdk-lts actually depend on it and I only use it against existing and valid
summary.txt files.
- For users, it can regress if the user was counting on jtdiff failing and
exiting with an error code 2 when given a file not named "summary.txt".
Automated scripts that do test result comparison come to mind. Still, this is a
highly irregular use, as it would be unexpected to have a script/user providing
'invalid' test summary files with the expectation for it it to fail.
[Other Info]
To reduce the risk of regressions, the proposed fix will change a
filename.equals("summary.txt") into filename.endsWith("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 => Wishlist
** Changed in: jtreg (Ubuntu)
Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx)
** Changed in: jtreg (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/1904070
Title:
jdiff should be less strict about the summary.txt filename
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jtreg/+bug/1904070/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902712] Re: tomcat app LDAP authentification fails after JAVA-Update
Thank you for taking the time to report this bug and helping to make Ubuntu better. This has been reported [1] and is being discussed upstream for inclusion in 8u275 [2]. We are waiting for the release of 8u275 that will fix another regression and we will include this fix even if upstream does not. [1] https://bugs.openjdk.java.net/browse/JDK-8214440#comment-14377867 [2] https://mail.openjdk.java.net/pipermail/jdk8u-dev/2020-November/012950.html ** Tags added: bionic focal groovy hirsute regression-update xenial ** Changed in: openjdk-8 (Ubuntu) Importance: Undecided => Critical ** Changed in: openjdk-8 (Ubuntu) Status: New => Confirmed ** Changed in: openjdk-8 (Ubuntu) Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902712 Title: tomcat app LDAP authentification fails after JAVA-Update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1902712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853366] Re: mediathekview 13.0.6-1 does not support openjfx 11
I verified mediathekview for bionic and it now works and starts fine. $ apt policy mediathekview mediathekview: Installed: 13.0.6-3~18.04 Candidate: 13.0.6-3~18.04 Version table: *** 13.0.6-3~18.04 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 13.0.6-1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ** 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/1853366 Title: mediathekview 13.0.6-1 does not support openjfx 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediathekview/+bug/1853366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902708] Re: icedtea-8-plugin is missing IcedTeaPlugin.so
Thank you for taking the time to report this bug and helping to make Ubuntu better. According to https://launchpad.net/ubuntu/+source/icedtea-web/+changelog #detail_icedtea-web_1.8-0ubuntu8~18.04 the plugin was removed due to the lack of support for NPAPI from all major browsers, as follows: Provide empty icedtea-netx-common, icedtea-plugin and icedtea-8-plugin packages to match the binary packages found in 18.04 LTS. The plugin packages are non-functional, because the NPAPI support in browsers was already removed. Do you have a use case where that library is actually required? Could you please describe the steps to reproduce it? Note: Setting it as incomplete until more information becomes available. ** Changed in: icedtea-web (Ubuntu) Status: New => Incomplete ** Tags removed: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902708 Title: icedtea-8-plugin is missing IcedTeaPlugin.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/1902708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902708] Re: icedtea-8-plugin is missing IcedTeaPlugin.so
** Tags added: bionic regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902708 Title: icedtea-8-plugin is missing IcedTeaPlugin.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/1902708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877000] Re: openjfx is missing native libraries for webkit and media
Saikrishna Arcot (saiarcot895), while doing a verification on this bug I saw your patch, I apologize for not noticing it while I was fixing this, so I could use it and acknowledge your work - and save me the trouble of figuring it out myself. I verified that openjfx 11.0.7+0-2ubuntu2 in focal-proposed fixes the issue. The previously missing media libs are now in place: $ comm -3 <(dpkg-deb -c libopenjfx-jni_11.0.7+0-2ubuntu1_amd64.deb | cut -c49- | sort) <(dpkg-deb -c libopenjfx-jni_11.0.7+0-2ubuntu2_amd64.deb | cut -c49- | sort) ./usr/lib/x86_64-linux-gnu/jni/libavplugin.so ./usr/lib/x86_64-linux-gnu/jni/libfxplugins.so ./usr/lib/x86_64-linux-gnu/jni/libgstreamer-lite.so ./usr/lib/x86_64-linux-gnu/jni/libjfxmedia.so ./usr/lib/x86_64-linux-gnu/jni/libjfxwebkit.so and installing the libopenjfx-java/-jni binaries fixes PDFSam: it no longer gives a warning about missing jfxmedia in the library path and a sound does play after completing an action. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877000 Title: openjfx is missing native libraries for webkit and media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1877000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts
** No longer affects: openjdk-7 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts
** No longer affects: openjdk-7 (Ubuntu Xenial) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875918] Re: openjdk crash: jdk11+eclipse+jformdesigner
>Changelog of JFormDesigner 7.0.2 now states the following: >Eclipse plug-in on Ubuntu Linux: Disallow using Ubuntu Java to avoid Eclipse >crashes. AdoptOpenJDK 11 or later is recommended to run Eclipse on Ubuntu. Yes, I noticed that when I was trying to reproduce the issue, as reported in #3. They disabled it on their own and since we never heard a word I can't tell if they have any interest in getting it working with our OpenJDK. Reports about 7.0.2 not running with our OpenJDK should be reported directly to them, preferably referencing this bug as well. At the time I did send an email to the company behind the plugin to let them know we tried to take a look and to ask for some debugging data, but never got a reply. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875918 Title: openjdk crash: jdk11+eclipse+jformdesigner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1875918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877000] Re: openjfx is missing native libraries for webkit and media
The fix is waiting for review [1]. Now that Groovy is out someone should be looking at it soon. [1] https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=openjfx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877000 Title: openjfx is missing native libraries for webkit and media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1877000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821412] Re: "System program problem" report button does nothing
** Tags added: focal groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821412 Title: "System program problem" report button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1821412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894419] Re: Missing TextPane.background property in GTKLookAndFeel causes white background on dark theme
Thanks for the reproducer. JTextPane by itself does work correctly and has the right background and text colors from the theme, but when getting the TextPane.background color property the theme color is not being respect. I haven't found any open issues in OpenJDK upstream about this problem and so far it seems to affect all codebases I have looked at (OpenJDK 8-16). To address that I have send a message to the swing mailing about this. I will add more comments when I get a reply. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894419 Title: Missing TextPane.background property in GTKLookAndFeel causes white background on dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1894419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894419] Re: Missing TextPane.background property in GTKLookAndFeel causes white background on dark theme
** Summary changed: - Wrong TextPane.background color with GTKLookAndFeel on dark theme + Missing TextPane.background property in GTKLookAndFeel causes white background on dark theme ** Description changed: OpenJDK provide GTKLookAndFeel for Ubuntu and other Linux desktop when using Gnome and GTK based environment. When setting dark theme (such as adwaita-dark) from operating system preference, GTK LAF changes its colors (great!). - Unfortunately "TextPane.background" become always 'white' so edit pane - become a "white-out", that means both background and font are white. + Unfortunately when getting "TextPane.background" it returns always + 'white' so edit pane become a "white-out", that means both background + and font are white. It is because GTK LaF inherit from Synth Laf, which is extend BasicLookAndFeel, and TextPane.background is defined in BasicLookAndFeel as follows: ``` - "TextPane.background", white, + "TextPane.background", white, ``` Since GTK LaF respect desktop theme such as dark, so it should be also change based on the desktop configuration. I've attached a patch to solve it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894419 Title: Missing TextPane.background property in GTKLookAndFeel causes white background on dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1894419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887142] Re: pdfsam won't run, has missing and conflicting dependencies
Verified pdfsam 4.0.4-1ubuntu2~20.04 and libsejda-java 3.2.84-2~20.04 from focal-proposed. I confirm that PDFSam now works for splitting and merging PDF files. pdfsam: Installed: 4.0.4-1ubuntu2~20.04 Candidate: 4.0.4-1ubuntu2~20.04 Version table: *** 4.0.4-1ubuntu2~20.04 400 400 http://localhost:/ubuntu focal-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 4.0.4-1 500 500 http://localhost:/ubuntu focal/universe amd64 Packages libsejda-java: Installed: 3.2.84-2~20.04 Candidate: 3.2.84-2~20.04 Version table: *** 3.2.84-2~20.04 400 400 http://localhost:/ubuntu focal-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 3.2.84-1 500 500 http://localhost:/ubuntu focal/universe amd64 Packages ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887142 Title: pdfsam won't run, has missing and conflicting dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhibernate-validator-java/+bug/1887142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878899] Re: Call trace from __video_do_ioctl
** Also affects: v4l2loopback (Ubuntu) Importance: Undecided Status: New ** Changed in: v4l2loopback (Ubuntu) Status: New => Confirmed ** No longer affects: linux (Ubuntu) ** Summary changed: - Call trace from __video_do_ioctl + Call trace from __video_do_ioctl on focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878899 Title: Call trace from __video_do_ioctl on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1878899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877000] Re: openjfx is missing native libraries for webkit and media
Robie, I updated my submission to strip all unrelated changes. Thanks for the heads up. ** Changed in: openjfx (Ubuntu Focal) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877000 Title: openjfx is missing native libraries for webkit and media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1877000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894419] Re: Wrong TextPane.background color with GTKLookAndFeel on dark theme
Forgot to add what happened in my case.
- background was dark
- text was white
I modified the code a bit to simplify it:
import java.awt.BorderLayout;
import java.awt.Dimension;
import javax.swing.JFrame;
import javax.swing.JTextPane;
public class Example {
public Example() {
JFrame frame = new JFrame();
JTextPane pane = new JTextPane();;
frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
pane.setPreferredSize(new Dimension(200, 200));
frame.getContentPane().add(pane, BorderLayout.CENTER);
frame.pack();
frame.setVisible(true);
}
public static void main(String[] args) {
new Example();
}
}
** Changed in: openjdk-lts (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894419
Title:
Wrong TextPane.background color with GTKLookAndFeel on dark theme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1894419/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894419] Re: Wrong TextPane.background color with GTKLookAndFeel on dark theme
Thank you for taking the time to report this bug and helping to make Ubuntu better. I tried the code in https://stackoverflow.com/a/31928409 with Ayu- Mirage-Dark and I couldn't reproduce the issue. Please provide the following items: - a reproducer with actual code - the exact OpenJDK version - which Ubuntu release was this tested on I'm setting it as incomplete for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894419 Title: Wrong TextPane.background color with GTKLookAndFeel on dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1894419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762999] Re: Unable to start Scilab 6.0.1 on bionic because of missed Java
That was a regression introduced by OpenJDK 11.0.6, it is being tracked in bug 1870813. ** No longer affects: openjdk-8 (Ubuntu) ** No longer affects: openjdk-9 (Ubuntu) ** No longer affects: openjdk-lts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762999 Title: Unable to start Scilab 6.0.1 on bionic because of missed Java To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1762999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870813] Re: Scilab does not start on bionic and focal
** Description changed: [Impact] Scilab does not start. This is a regression from an OpenJDK 11 update. SRU TEAM: please note that scilab runs OpenJDK 8 and since Bionic we have been forcing it to use OpenJDK 11 (see bug 1814133). Since the last Bionic and Focal update there have been fixes from both upstream and Debian to improve compatibility. Apart from those fixes I would like to bring additional fixes to our LTS releases and align them better with the one on Groovy (which works fine): * improved dependencies * appdata/desktop fixes to improve user experience * update from 6.0.1 to 6.0.2 in Bionic [Test Case] On Bionic or Focal: Steps to reproduce: 1. Install Scilab with `sudo apt-get install scilab` 2. Try to launch Scilab from terminal by using command `scilab` Expected results: * Scilab started normally Actual results: * Scilab does not start, shows the following output in the terminal: $ scilab Picked up _JAVA_OPTIONS: -Djava.class.path=/usr/share/java/flexdock.jar:/usr/share/java/skinlf.jar:/usr/share/java/looks.jar:/usr/share/java/commons-logging.jar:/usr/share/java/jhall.jar:/usr/share/java/lucene-core-4.10.4.jar:/usr/share/java/lucene-analyzers-common-4.10.4.jar:/usr/share/java/lucene-queryparser-4.10.4.jar:/usr/share/maven-repo/org/freehep/freehep-util/debian/freehep-util-debian.jar:/usr/share/maven-repo/org/freehep/freehep-io/debian/freehep-io-debian.jar:/usr/share/maven-repo/org/freehep/freehep-graphicsio/debian/freehep-graphicsio-debian.jar:/usr/share/java/freehep-graphicsio-emf-2.1.jar:/usr/share/java/freehep-graphics2d-2.1.1.jar:/usr/share/java/jrosetta-API.jar:/usr/share/java/jrosetta-engine-1.0.4.jar:/usr/share/java/jgraphx.jar:/usr/share/java/jogl2.jar:/usr/share/java/gluegen2-rt.jar:/usr/share/java/jeuclid-core.jar:/usr/share/java/jlatexmath-fop-1.0.7.jar:/usr/share/java/fop.jar:/usr/share/java/saxon.jar:/usr/share/java/batik.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/jlatexmath-1.0.7.jar:/usr/share/java/ecj.jar:/usr/share/java/javax.activation.jar:/usr/share/java/jaxb-runtime.jar:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar:/usr/share/scilab/modules/completion/jar/org.scilab.modules.completion.jar:/usr/share/scilab/modules/graphic_export/jar/org.scilab.modules.graphic_export.jar:/usr/share/scilab/modules/external_objects_java/tests/libintl.jar:/usr/share/scilab/modules/external_objects_java/jar/org.scilab.modules.external_objects_java.jar:/usr/share/scilab/modules/scirenderer/jar/scirenderer.jar:/usr/share/scilab/modules/action_binding/jar/org.scilab.modules.action_binding.jar:/usr/share/scilab/modules/history_manager/jar/org.scilab.modules.history_manager.jar:/usr/share/scilab/modules/console/jar/org.scilab.modules.console.jar:/usr/share/scilab/modules/graphic_objects/jar/org.scilab.modules.graphic_objects.jar:/usr/share/scilab/modules/xcos/jar/org.scilab.modules.xcos.jar:/usr/share/scilab/modules/commons/jar/org.scilab.modules.commons.jar:/usr/share/scilab/modules/graph/jar/org.scilab.modules.graph.jar:/usr/share/scilab/modules/gui/jar/org.scilab.modules.gui.jar:/usr/share/scilab/modules/renderer/jar/org.scilab.modules.renderer.jar:/usr/share/scilab/modules/helptools/jar/scilab_ja_JP_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_fr_FR_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_pt_BR_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_ru_RU_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_en_US_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_images.jar:/usr/share/scilab/modules/helptools/jar/org.scilab.modules.helptools.jar:/usr/share/scilab/modules/types/jar/org.scilab.modules.types.jar:/usr/share/scilab/modules/localization/jar/org.scilab.modules.localization.jar:/usr/share/scilab/modules/javasci/jar/org.scilab.modules.javasci.jar:/usr/share/scilab/modules/preferences/jar/org.scilab.modules.preferences.jar:/usr/share/scilab/modules/core/jar/org.scilab.modules.core.jar:/usr/share/scilab/modules/history_browser/jar/org.scilab.modules.history_browser.jar:/usr/share/scilab/modules/ui_data/jar/org.scilab.modules.ui_data.jar:/usr/share/scilab/modules/scinotes/jar/org.scilab.modules.scinotes.jar: WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.scilab.modules.jvm.LibraryPath (file:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar) to field java.lang.ClassLoader.sys_paths WARNING: Please consider reporting this to the maintainers of org.scilab.modules.jvm.LibraryPath WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Could not access to the Main Scilab Class: Exception in thread "main" java.lang.ExceptionInInitializerError at
[Bug 1870813] Re: Scilab does not start on bionic and focal
** Description changed: [Impact] Scilab does not start. This is a regression from an OpenJDK 11 update. SRU TEAM: please note that scilab runs OpenJDK 8 and since Bionic we have been forcing it to use OpenJDK 11 (see bug 1814133). Since the last Bionic and Focal update there have been fixes from both upstream and Debian to improve compatibility. Apart from those fixes I would like to bring additional fixes to our LTS releases and align them better with the one on Groovy (which works fine): * improved dependencies * appdata/desktop fixes to improve user experience * update from 6.0.1 to 6.0.2 in Bionic [Test Case] On Bionic or Focal: Steps to reproduce: 1. Install Scilab with `sudo apt-get install scilab` 2. Try to launch Scilab from terminal by using command `scilab` Expected results: * Scilab started normally Actual results: * Scilab does not start, shows the following output in the terminal: $ scilab Picked up _JAVA_OPTIONS: -Djava.class.path=/usr/share/java/flexdock.jar:/usr/share/java/skinlf.jar:/usr/share/java/looks.jar:/usr/share/java/commons-logging.jar:/usr/share/java/jhall.jar:/usr/share/java/lucene-core-4.10.4.jar:/usr/share/java/lucene-analyzers-common-4.10.4.jar:/usr/share/java/lucene-queryparser-4.10.4.jar:/usr/share/maven-repo/org/freehep/freehep-util/debian/freehep-util-debian.jar:/usr/share/maven-repo/org/freehep/freehep-io/debian/freehep-io-debian.jar:/usr/share/maven-repo/org/freehep/freehep-graphicsio/debian/freehep-graphicsio-debian.jar:/usr/share/java/freehep-graphicsio-emf-2.1.jar:/usr/share/java/freehep-graphics2d-2.1.1.jar:/usr/share/java/jrosetta-API.jar:/usr/share/java/jrosetta-engine-1.0.4.jar:/usr/share/java/jgraphx.jar:/usr/share/java/jogl2.jar:/usr/share/java/gluegen2-rt.jar:/usr/share/java/jeuclid-core.jar:/usr/share/java/jlatexmath-fop-1.0.7.jar:/usr/share/java/fop.jar:/usr/share/java/saxon.jar:/usr/share/java/batik.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/jlatexmath-1.0.7.jar:/usr/share/java/ecj.jar:/usr/share/java/javax.activation.jar:/usr/share/java/jaxb-runtime.jar:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar:/usr/share/scilab/modules/completion/jar/org.scilab.modules.completion.jar:/usr/share/scilab/modules/graphic_export/jar/org.scilab.modules.graphic_export.jar:/usr/share/scilab/modules/external_objects_java/tests/libintl.jar:/usr/share/scilab/modules/external_objects_java/jar/org.scilab.modules.external_objects_java.jar:/usr/share/scilab/modules/scirenderer/jar/scirenderer.jar:/usr/share/scilab/modules/action_binding/jar/org.scilab.modules.action_binding.jar:/usr/share/scilab/modules/history_manager/jar/org.scilab.modules.history_manager.jar:/usr/share/scilab/modules/console/jar/org.scilab.modules.console.jar:/usr/share/scilab/modules/graphic_objects/jar/org.scilab.modules.graphic_objects.jar:/usr/share/scilab/modules/xcos/jar/org.scilab.modules.xcos.jar:/usr/share/scilab/modules/commons/jar/org.scilab.modules.commons.jar:/usr/share/scilab/modules/graph/jar/org.scilab.modules.graph.jar:/usr/share/scilab/modules/gui/jar/org.scilab.modules.gui.jar:/usr/share/scilab/modules/renderer/jar/org.scilab.modules.renderer.jar:/usr/share/scilab/modules/helptools/jar/scilab_ja_JP_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_fr_FR_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_pt_BR_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_ru_RU_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_en_US_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_images.jar:/usr/share/scilab/modules/helptools/jar/org.scilab.modules.helptools.jar:/usr/share/scilab/modules/types/jar/org.scilab.modules.types.jar:/usr/share/scilab/modules/localization/jar/org.scilab.modules.localization.jar:/usr/share/scilab/modules/javasci/jar/org.scilab.modules.javasci.jar:/usr/share/scilab/modules/preferences/jar/org.scilab.modules.preferences.jar:/usr/share/scilab/modules/core/jar/org.scilab.modules.core.jar:/usr/share/scilab/modules/history_browser/jar/org.scilab.modules.history_browser.jar:/usr/share/scilab/modules/ui_data/jar/org.scilab.modules.ui_data.jar:/usr/share/scilab/modules/scinotes/jar/org.scilab.modules.scinotes.jar: WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.scilab.modules.jvm.LibraryPath (file:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar) to field java.lang.ClassLoader.sys_paths WARNING: Please consider reporting this to the maintainers of org.scilab.modules.jvm.LibraryPath WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Could not access to the Main Scilab Class: Exception in thread "main" java.lang.ExceptionInInitializerError at
[Bug 1887142] Re: pdfsam won't run, has missing and conflicting dependencies
> Is it possible that any Ubuntu users consume libsejda-java directly, and thus would be regressed by bumping it to to the 1.1 spec? Thanks for catching this. I updated the regression to include: Ubuntu users consuming libsejda-java directly can regress if something else in their dependency chain currently relies on spec 1.0 - they would need to update these dependencies to also use spec 1.1. I don't know how I could/should evaluate how bad this is compared to having a non-working package such as pdfsam, so I would appreciate any feedback related to the SRU process on such decisions (maybe just having the regressions described is good enough?). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887142 Title: pdfsam won't run, has missing and conflicting dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhibernate-validator-java/+bug/1887142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887142] Re: pdfsam won't run, has missing and conflicting dependencies
** Description changed: [Impact] pdfsam fails to work due missing and conflicting dependencies. On Focal and Groovy libhibernate-validator-java has a runtime dependency on libel-api-java and an implementation of el-api. Both are usually provided when running under Java EE. On Java SE the application must take care of providing them - and pdfsam is missing these dependencies. The usual implementation of el-api on Maven projects is from Glassfish, but that has not yet been packaged. libtomcat9-embed-java also provides one such implementation in tomcat9-embed-el.jar which can be used instead. Also during build time pdfsam must create links of the jar files it needs for runtime: tomcat9-embed-el.jar and classmate.jar (a new dependency from libhibernate-validator-java) are missing from this list. Only on Focal: * libsejda-java 3.2.84-1 depends on libgeronimo-validation-1.0-spec-java * libhibernate-validator-java depends on libgeronimo-validation-1.1-spec-java A Java application must has either 1.0 or 1.1 spec on its classpath, never both as they are incompatible. To fix this libsejda-java in Focal should be updated to 3.2.84-2 so everything depends on the 1.1 spec (ie. libgeronimo-validation-1.1-spec-java). [Test Case] 1) On Focal and Groovy, install pdfsam and run it $ sudo apt get install -y pdfsam $ pdfsam 2) Split a PDF Expected result: For the action to execute correctly. Actual result: The console shows a java stacktrace such as ERROR 15:56:04.873 org.pdfsam.UncaughtExceptionLogger[JavaFX Application Thread] Unexpected error org.sejda.eventstudio.exception.EventStudioException: Reflective method invocation exception ... [Regression Potential] * libseja-java backport: Moving from 1.0 to 1.1 spec might cause regressions on packages that depend on libsejda-java as now el-api (and its implementation) must be available on the classpath (default on Java EE). At this time the only package that depends on libsejda-java is pdfsam. + Ubuntu users consuming libsejda-java directly can regress if something else in their dependency chain currently relies on spec 1.0 - they would need to update these dependencies to also use spec 1.1. * New dependency on libtomcat9-embed-java (as an el-api provider): The most common implementation of el-api is from Glassfish, so using tomcat9 to provide this might introduce problems if it deviates from the spec (unlikely, as tomcat is also a Java EE provider). [Other Info] [Original Report] pdfsam does not produce an output file because of various java-exceptions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pdfsam 4.0.4-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 10 11:46:14 2020 InstallationDate: Installed on 2019-09-09 (304 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pdfsam UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887142 Title: pdfsam won't run, has missing and conflicting dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhibernate-validator-java/+bug/1887142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853366] Re: mediathekview 13.0.6-1 does not support openjfx 11
** Description changed: - [Impact] + [Impact] The update of openjfx and openjdk from 8 to 11 in Bionic caused a regression on mediathekview and it no longer starts. mediathekview 13.0.6-1/bionic only works with openjfx 8, to properly support openjfx/openjdk 11 a backport of mediathekview 13.0.6-3/disco is needed. - [Test Case] Install mediathekview and run it: $ sudo apt install mediathekview $ mediathekview Expected result: App should open and run. Current result: - App complain that it needs OpenJDK 8 to run. + mediathekview spits a message to stdout saying it requires OpenJDK 8 to run and then exits, no GUI is shown. - - [Regression Potential] + [Regression Potential] mediathekview 13.0 was designed to run with openjdk/openjfx 8, so forcing the compatibility with 11 might introduce regressions, these will have to be tracked down as new bug reports come in. - [Other Info] mediathekview 13.2 (in Focal and Groovy) has upstream support for openjdk/openjfx 11, but the minor version update also brings a lot of other changes and new dependencies that could introduce further regressions. Such update will only be tried if cherry-picking further fixes for 13.0.6-3 is too deemed to much work. - [Original Report] mediathekview no longer starts with the latest libopenjfx-java 11.0.2+1-1~18.04.2. It runs fine when downgrading to 8u161-b12-1ubuntu2. $ mediathekview === JavaFX wurde nicht im klassenpfad gefunden. Stellen Sie sicher, dass Sie ein Java JRE ab Version 8 benutzen. Falls Sie Linux nutzen, installieren Sie das openjfx-Paket ihres Package-Managers, oder nutzen Sie eine eigene JRE-Installation. === -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853366 Title: mediathekview 13.0.6-1 does not support openjfx 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediathekview/+bug/1853366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853366] Re: mediathekview 13.0.6-1 does not support openjfx 11
** Description changed: - mediathekview no longer starts with the latest libopenjfx-java - 11.0.2+1-1~18.04.2. It runs fine when downgrading to - 8u161-b12-1ubuntu2. + [Impact] + The update of openjfx and openjdk from 8 to 11 in Bionic caused a regression on mediathekview and it no longer starts. + + mediathekview 13.0.6-1/bionic only works with openjfx 8, to properly + support openjfx/openjdk 11 a backport of mediathekview 13.0.6-3/disco is + needed. + + + [Test Case] + Install mediathekview and run it: + $ sudo apt install mediathekview + $ mediathekview + + Expected result: + App should open and run. + + Current result: + App complain that it needs OpenJDK 8 to run. + + + [Regression Potential] + mediathekview 13.0 was designed to run with openjdk/openjfx 8, so forcing the compatibility with 11 might introduce regressions, these will have to be tracked down as new bug reports come in. + + + [Other Info] + mediathekview 13.2 (in Focal and Groovy) has upstream support for openjdk/openjfx 11, but the minor version update also brings a lot of other changes and new dependencies that could introduce further regressions. Such update will only be tried if cherry-picking further fixes for 13.0.6-3 is too deemed to much work. + + + [Original Report] + mediathekview no longer starts with the latest libopenjfx-java 11.0.2+1-1~18.04.2. It runs fine when downgrading to 8u161-b12-1ubuntu2. $ mediathekview === JavaFX wurde nicht im klassenpfad gefunden. Stellen Sie sicher, dass Sie ein Java JRE ab Version 8 benutzen. Falls Sie Linux nutzen, installieren Sie das openjfx-Paket ihres Package-Managers, oder nutzen Sie eine eigene JRE-Installation. === -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853366 Title: mediathekview 13.0.6-1 does not support openjfx 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediathekview/+bug/1853366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853366] Re: mediathekview 13.0.6-1 does not support openjfx 11
** Summary changed: - latest libopenjxf-java incompatible with bionic mediathekview + mediathekview 13.0.6-1 does not support openjfx 11 ** Changed in: openjfx (Ubuntu) Status: Confirmed => Invalid ** Changed in: openjfx (Ubuntu Bionic) Status: Confirmed => Invalid ** Changed in: mediathekview (Ubuntu) Importance: Undecided => High ** Changed in: mediathekview (Ubuntu Bionic) Importance: Undecided => High ** Changed in: mediathekview (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/1853366 Title: mediathekview 13.0.6-1 does not support openjfx 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediathekview/+bug/1853366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721852] Re: JavaFX support is in Oracle JDK 9 but missing in Ubuntu OpenJDK 9
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 1721852 and any other logs that are relevant for this particular issue. ** Changed in: openjdk-9 (Ubuntu) Status: Confirmed => Invalid ** Changed in: openjfx (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721852 Title: JavaFX support is in Oracle JDK 9 but missing in Ubuntu OpenJDK 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-9/+bug/1721852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682449] Re: Trying to open JavaFX browser with jbrowserdriver crashes JVM
Thank you for reporting this bug to Ubuntu. Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: openjfx (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682449 Title: Trying to open JavaFX browser with jbrowserdriver crashes JVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1682449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799946] Re: OpenJFX-11 does not work with OpenJDK-8
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. Oracle has dropped the leadership of the OpenJFX 8 project [1] and nobody else took it over, so it is pretty much dead. According to the official OpenJFX website [2] it is being developed at https://github.com/openjdk/jfx and as of now the download page indicates that the only supported versions are 11 (LTS version), 15, and 16 [3]. That said, there is one repository still backporting some fixes to OpenJFX 8u [4] which, should anyone volunteer, could be used to create a new openjfx-8 package. [1] https://mail.openjdk.java.net/pipermail/openjfx-dev/2019-January/023039.html [2] https://wiki.openjdk.java.net/display/OpenJFX [3] https://gluonhq.com/products/javafx/ [4] https://github.com/ojdkbuild/upstream_openjfx-8u ** Changed in: openjfx (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799946 Title: OpenJFX-11 does not work with OpenJDK-8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1799946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836437] Re: Native libraries not locatable, resulting application launch failure
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 1836437 and any other logs that are relevant for this particular issue. Please be aware that 2 missing libraries are being fixed in bug 1877000. ** Changed in: openjfx (Ubuntu) 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/1836437 Title: Native libraries not locatable, resulting application launch failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1836437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879480] Re: Missing files in .deb package
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. That said, the openjfx files are split among 3 packages: openjfx, libopenjfx-jni, and libopenjfx-java. For lib files in Bionic, take a look at https://packages.ubuntu.com/bionic/amd64/libopenjfx-jni/filelist https://packages.ubuntu.com/bionic/amd64/libopenjfx-java/filelist The javapackager from openjfx has been removed upstream and replaced by jpackager in OpenJDK. Removal of openjfx's javapackager: https://bugs.openjdk.java.net/browse/JDK-8203379 JEP-343 for jpackager: https://bugs.openjdk.java.net/browse/JDK-8200758 Due to that openjdk no longer has any files under /usr/bin ** Changed in: openjfx (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879480 Title: Missing files in .deb package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1879480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877000] Re: openjfx is missing native libraries for webkit and media
** Description changed: - [Impact] + [Impact] OpenJFX's media and webkit native libraries are missing from amd64 builds in Focal and Groovy. This is a regression from Bionic. This prevents applications that depend on these libraries from working correctly. [Test Case] The libjfxmedia.so and libjfxwebkit.so should be present in the libopenjfx-jni binary for all archs. One can see in the amd64 package listing for Focal [1,2] and Groovy [3,4] that libjfxmedia.so and libjfxwebkit.so are only available on arm64, armhf, ppc64el, and s390x. [1] https://packages.ubuntu.com/search?searchon=contents=libjfxmedia.so=exactfilename=focal=any [2] https://packages.ubuntu.com/search?searchon=contents=libjfxwebkit.so=exactfilename=focal=any [3] https://packages.ubuntu.com/search?searchon=contents=libjfxmedia.so=exactfilename=groovy=any [4] https://packages.ubuntu.com/search?searchon=contents=libjfxwebkit.so=exactfilename=groovy=any - Another possible test case is running pdfsam in the console to split a PDF file (after pdfsam bug 1887142 is fixed) and look if errors as: Caused by: java.lang.UnsatisfiedLinkError: no jfxmedia in java.library.path: [/usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib] show up in the stdout. A sound should be played if everything works. - - [Regression Potential] + [Regression Potential] Enabling the native libraries will allow applications to use them again. - * This can trigger errors in applications that were not detected while the libraries were missing. + * This can trigger errors in applications that hidden by the fact that there were no native libraries to use. * This can cause applications that use OpenJFX to fail to run or crash during runtime. - It is unlikely that autopkgtest will detect such errors given that OpenJFX _did_ migrate when the native libraries were missing (and should have caused errors). + It is unlikely that autopkgtest will detect such errors given that OpenJFX _did_ migrate when the native libraries were missing (and that should have caused errors). [Other Info] - [Original Report] I'm trying to run BlueJ on Ubuntu 20.04 (fresh install), while the main app runs the editor refuses to start, looking at its logs apparently it can't find jfxwebkit. So I tried to search for it, and apparently it is present in the other architectures for Focal as well as all architectures in Eoan, Bionic and Xenial in the libopenjfx-jni package, but not for Focal amd64. The version of openjfx I have is 11.0.7+0-2ubuntu1. I have also attached BlueJ's log for reference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877000 Title: openjfx is missing native libraries for webkit and media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1877000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870813] Re: Scilab does not start on bionic and focal
** Description changed: [Impact] Scilab does not start. This is a regression from an OpenJDK 11 update. SRU TEAM: please note that scilab runs OpenJDK 8 and since Bionic we have been forcing it to use OpenJDK 11 (see bug 1814133). Since the last Bionic and Focal update there have been fixes from both upstream and Debian to improve compatibility. Apart from those fixes I would like to bring additional fixes to our LTS releases and align them better with the one on Groovy (which works fine): * improved dependencies * appdata/desktop fixes to improve user experience * update from 6.0.1 to 6.0.2 in Bionic - [Test Case] On Bionic or Focal: Steps to reproduce: 1. Install Scilab with `sudo apt-get install scilab` 2. Try to launch Scilab from terminal by using command `scilab` Expected results: * Scilab started normally Actual results: * Scilab does not start, shows the following output in the terminal: $ scilab Picked up _JAVA_OPTIONS: -Djava.class.path=/usr/share/java/flexdock.jar:/usr/share/java/skinlf.jar:/usr/share/java/looks.jar:/usr/share/java/commons-logging.jar:/usr/share/java/jhall.jar:/usr/share/java/lucene-core-4.10.4.jar:/usr/share/java/lucene-analyzers-common-4.10.4.jar:/usr/share/java/lucene-queryparser-4.10.4.jar:/usr/share/maven-repo/org/freehep/freehep-util/debian/freehep-util-debian.jar:/usr/share/maven-repo/org/freehep/freehep-io/debian/freehep-io-debian.jar:/usr/share/maven-repo/org/freehep/freehep-graphicsio/debian/freehep-graphicsio-debian.jar:/usr/share/java/freehep-graphicsio-emf-2.1.jar:/usr/share/java/freehep-graphics2d-2.1.1.jar:/usr/share/java/jrosetta-API.jar:/usr/share/java/jrosetta-engine-1.0.4.jar:/usr/share/java/jgraphx.jar:/usr/share/java/jogl2.jar:/usr/share/java/gluegen2-rt.jar:/usr/share/java/jeuclid-core.jar:/usr/share/java/jlatexmath-fop-1.0.7.jar:/usr/share/java/fop.jar:/usr/share/java/saxon.jar:/usr/share/java/batik.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/jlatexmath-1.0.7.jar:/usr/share/java/ecj.jar:/usr/share/java/javax.activation.jar:/usr/share/java/jaxb-runtime.jar:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar:/usr/share/scilab/modules/completion/jar/org.scilab.modules.completion.jar:/usr/share/scilab/modules/graphic_export/jar/org.scilab.modules.graphic_export.jar:/usr/share/scilab/modules/external_objects_java/tests/libintl.jar:/usr/share/scilab/modules/external_objects_java/jar/org.scilab.modules.external_objects_java.jar:/usr/share/scilab/modules/scirenderer/jar/scirenderer.jar:/usr/share/scilab/modules/action_binding/jar/org.scilab.modules.action_binding.jar:/usr/share/scilab/modules/history_manager/jar/org.scilab.modules.history_manager.jar:/usr/share/scilab/modules/console/jar/org.scilab.modules.console.jar:/usr/share/scilab/modules/graphic_objects/jar/org.scilab.modules.graphic_objects.jar:/usr/share/scilab/modules/xcos/jar/org.scilab.modules.xcos.jar:/usr/share/scilab/modules/commons/jar/org.scilab.modules.commons.jar:/usr/share/scilab/modules/graph/jar/org.scilab.modules.graph.jar:/usr/share/scilab/modules/gui/jar/org.scilab.modules.gui.jar:/usr/share/scilab/modules/renderer/jar/org.scilab.modules.renderer.jar:/usr/share/scilab/modules/helptools/jar/scilab_ja_JP_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_fr_FR_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_pt_BR_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_ru_RU_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_en_US_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_images.jar:/usr/share/scilab/modules/helptools/jar/org.scilab.modules.helptools.jar:/usr/share/scilab/modules/types/jar/org.scilab.modules.types.jar:/usr/share/scilab/modules/localization/jar/org.scilab.modules.localization.jar:/usr/share/scilab/modules/javasci/jar/org.scilab.modules.javasci.jar:/usr/share/scilab/modules/preferences/jar/org.scilab.modules.preferences.jar:/usr/share/scilab/modules/core/jar/org.scilab.modules.core.jar:/usr/share/scilab/modules/history_browser/jar/org.scilab.modules.history_browser.jar:/usr/share/scilab/modules/ui_data/jar/org.scilab.modules.ui_data.jar:/usr/share/scilab/modules/scinotes/jar/org.scilab.modules.scinotes.jar: WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.scilab.modules.jvm.LibraryPath (file:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar) to field java.lang.ClassLoader.sys_paths WARNING: Please consider reporting this to the maintainers of org.scilab.modules.jvm.LibraryPath WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Could not access to the Main Scilab Class: Exception in thread "main" java.lang.ExceptionInInitializerError at
[Bug 1877000] Re: openjfx is missing native libraries for webkit and media
** Also affects: openjfx (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: openjfx (Ubuntu Focal) Status: New => Confirmed ** Changed in: openjfx (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877000 Title: openjfx is missing native libraries for webkit and media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1877000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887142] Re: pdfsam won't run, has missing and conflicting dependencies
** Description changed: [Impact] pdfsam fails to work due missing and conflicting dependencies. On Focal and Groovy libhibernate-validator-java has a runtime dependency on libel-api-java and an implementation of el-api. Both are usually provided when running under Java EE. On Java SE the application must take care of providing them - and pdfsam is missing these dependencies. The usual implementation of el-api on Maven projects is from Glassfish, - but that has not yet been packaged. libtomcat9-java also provides one - such implementation in tomcat9-jasper-el.jar which can be used instead. + but that has not yet been packaged. libtomcat9-embed-java also provides + one such implementation in tomcat9-embed-el.jar which can be used + instead. Also during build time pdfsam must create links of the jar files it - needs for runtime: libel-api-java, libtomcat9-java, and classmate (new + needs for runtime: tomcat9-embed-el.jar and classmate.jar (a new dependency from libhibernate-validator-java). Only on Focal: * libsejda-java 3.2.84-1 depends on libgeronimo-validation-1.0-spec-java * libhibernate-validator-java depends on libgeronimo-validation-1.1-spec-java A Java application must has either 1.0 or 1.1 spec on its classpath, never both as they are incompatible. To fix this libsejda-java in Focal should be updated to 3.2.84-2 so everything depends on the 1.1 spec (ie. libgeronimo-validation-1.1-spec-java). [Test Case] 1) On Focal and Groovy, install pdfsam and run it $ sudo apt get install -y pdfsam $ pdfsam 2) Split a PDF Expected result: For the action to execute correctly. Actual result: The console shows a java stacktrace such as ERROR 15:56:04.873 org.pdfsam.UncaughtExceptionLogger[JavaFX Application Thread] Unexpected error org.sejda.eventstudio.exception.EventStudioException: Reflective method invocation exception ... [Regression Potential] - * libseja-java: + * libseja-java backport: Moving from 1.0 to 1.1 spec might cause regressions on packages that depend on libsejda-java as now el-api (and its implementation) must be available on the classpath (default on Java EE). At this time the only package that depends on libsejda-java is pdfsam. - * New dependency on libtomcat9-java (as an el-api provider): - The usual implementation of el-api is from Glassfish, so using tomcat9 to provide this might introduce problems if it deviates from the spec (unlikely, as tomcat is also a Java EE provider). - + * New dependency on libtomcat9-embed-java (as an el-api provider): + The most common implementation of el-api is from Glassfish, so using tomcat9 to provide this might introduce problems if it deviates from the spec (unlikely, as tomcat is also a Java EE provider). [Other Info] + [Original Report] pdfsam does not produce an output file because of various java-exceptions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pdfsam 4.0.4-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 10 11:46:14 2020 InstallationDate: Installed on 2019-09-09 (304 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pdfsam UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: [Impact] pdfsam fails to work due missing and conflicting dependencies. On Focal and Groovy libhibernate-validator-java has a runtime dependency on libel-api-java and an implementation of el-api. Both are usually provided when running under Java EE. On Java SE the application must take care of providing them - and pdfsam is missing these dependencies. The usual implementation of el-api on Maven projects is from Glassfish, but that has not yet been packaged. libtomcat9-embed-java also provides one such implementation in tomcat9-embed-el.jar which can be used instead. Also during build time pdfsam must create links of the jar files it needs for runtime: tomcat9-embed-el.jar and classmate.jar (a new - dependency from libhibernate-validator-java). + dependency from libhibernate-validator-java) are missing from this list. Only on Focal: * libsejda-java 3.2.84-1 depends on libgeronimo-validation-1.0-spec-java * libhibernate-validator-java depends on libgeronimo-validation-1.1-spec-java A Java application must has either 1.0 or 1.1 spec on its classpath, never both as they are incompatible. To fix this libsejda-java in Focal should be updated to 3.2.84-2 so everything depends on the 1.1 spec (ie. libgeronimo-validation-1.1-spec-java). [Test Case] 1) On Focal and Groovy, install pdfsam and run it $ sudo apt get install -y pdfsam $ pdfsam 2) Split a PDF Expected result: For the action to
[Bug 1887142] Re: libhibernate-validator-java should be backported to 4.3.4-1~18.04.1
** Description changed: [Impact] - Debian started migrating from libgeronimo-validation-1.0-spec-java to libgeronimo-validation-1.1-spec-java quite a while ago. Unfortunately both packages implement different Bean Validation Specs and are not compatible, thus all reverse (build-)dependencies and reverse (build-)dependencies of these spec packages must rely solely on the 1.0 or 1.1 version to avoid FTBFS or runtime issues. This transition has not yet been completed on Debian and both Focal and Groovy ended up with mixed dependencies. + pdfsam fails to work due missing and conflicting dependencies. - So far 2 packages seem to be affected by this and have regressed since Focal: - 1) pdfsam will start but can't split/merge/etc pdfs - 2) libspring-java FTBFS + On Focal and Groovy libhibernate-validator-java has a runtime dependency + on libel-api-java and an implementation of el-api. Both are usually + provided when running under Java EE. On Java SE the application must + take care of providing them - and pdfsam is missing these dependencies. - Both depend indirectly on libgeronimo-validation-1.1-spec-java through - libhibernate-validator-java. + The usual implementation of el-api on Maven projects is from Glassfish, + but that has not yet been packaged. libtomcat9-java also provides one + such implementation in tomcat9-jasper-el.jar which can be used instead. - pdfsam depends on libgeronimo-validation-1.0-spec-java through libsejda- - java, while libspring-java depends on 1.0 through through libspring- - java. + Also during build time pdfsam must create links of the jar files it + needs for runtime: libel-api-java, libtomcat9-java, and classmate (new + dependency from libhibernate-validator-java). - The easiest fix is to downgrade libhibernate-validator-java from 5.3.6-1 - to 4.3.4-1~18.04.1. Trying to update all dependencies to use - libgeronimo-validation-1.1-spec-java is problematic, requires new - packages, and even some dependencies that have not yet been packaged or - tested well. + Only on Focal: + * libsejda-java 3.2.84-1 depends on libgeronimo-validation-1.0-spec-java + * libhibernate-validator-java depends on libgeronimo-validation-1.1-spec-java + + A Java application must has either 1.0 or 1.1 spec on its classpath, + never both as they are incompatible. To fix this libsejda-java in Focal + should be updated to 3.2.84-2 so everything depends on the 1.1 spec (ie. + libgeronimo-validation-1.1-spec-java). [Test Case] 1) On Focal and Groovy, install pdfsam and run it $ sudo apt get install -y pdfsam $ pdfsam 2) Split a PDF Expected result: For the action to execute correctly. Actual result: The console shows a java stacktrace such as ERROR 15:56:04.873 org.pdfsam.UncaughtExceptionLogger[JavaFX Application Thread] Unexpected error org.sejda.eventstudio.exception.EventStudioException: Reflective method invocation exception ... [Regression Potential] - I haven't found packages that depend on libhibernate-validator-java and on validation-1.1-spec-java directly or indirectly, but I haven't looked at a depth bigger than 3. If there are packages with (indirect) dependencies on both libhibernate-validator-java and libgeronimo-validation-1.1-spec-java they will regress after this change. + * libseja-java: + Moving from 1.0 to 1.1 spec might cause regressions on packages that depend on libsejda-java as now el-api (and its implementation) must be available on the classpath (default on Java EE). At this time the only package that depends on libsejda-java is pdfsam. + + * New dependency on libtomcat9-java (as an el-api provider): + The usual implementation of el-api is from Glassfish, so using tomcat9 to provide this might introduce problems if it deviates from the spec (unlikely, as tomcat is also a Java EE provider). + [Other Info] - * On Debian unstable a new package called libhibernate-validator4-java has been created to deal with this problem, but it is not enough and it is even blocking from moving to testing. - * For pdfsam I tried to move libsejda-java to 1.1 spec, but as described in debian bug 942507 comment 10 it introduces new dependencies and one dependency on el-impl that is not packaged yet. [Original Report] pdfsam does not produce an output file because of various java-exceptions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pdfsam 4.0.4-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 10 11:46:14 2020 InstallationDate: Installed on 2019-09-09 (304 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pdfsam UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - libhibernate-validator-java should be
[Bug 1887142] Re: libhibernate-validator-java should be backported to 4.3.4-1~18.04.1
Backporting libhibernate-validator-java didn't work as expected. While the 4.3.4-1 deb binary from Focal (when it was still devel) works fine, it no longer builds as it depended on jboss-logging 3.3. The newer jboss-logging 3.4 does not provide the same classes and it has too many reverse (build) dependencies to be feasible to downgrade. Going the other way and updating libsejda-java to rely on libgeronimo-validation-1.1-spec-java requires some new dependencies (see debian bug 942507): * libel-api-java * an el-api implementation, usually Glassfish, but it is not yet packaged, thus tomcat9-jasper-el.jar can be used * libhibernate-validator-java >= 5.3.6-2 (as 5.3.6-1 is missing some runtime dependencies) The first 2 dependencies come from libhibernate-validator-java 5.3.6, but they are expected to be automatically provided by the Java EE environment and don't show up as actual dependencies. Since pdfsam run Java SE it must provide them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887142 Title: libhibernate-validator-java should be backported to 4.3.4-1~18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhibernate-validator-java/+bug/1887142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877000] Re: openjdk is missing native libraries for webkit and media
** Description changed: - I'm trying to run BlueJ on Ubuntu 20.04 (fresh install), while the main - app runs the editor refuses to start, looking at its logs apparently it - can't find jfxwebkit. So I tried to search for it, and apparently it is - present in the other architectures for Focal as well as all - architectures in Eoan, Bionic and Xenial in the libopenjfx-jni package, - but not for Focal amd64. The version of openjfx I have is - 11.0.7+0-2ubuntu1. I have also attached BlueJ's log for reference. + [Impact] + OpenJFX's media and webkit native libraries are missing from amd64 builds in Focal and Groovy. This is a regression from Bionic. + + This prevents applications that depend on these libraries from working + correctly. + + [Test Case] + The libjfxmedia.so and libjfxwebkit.so should be present in the libopenjfx-jni binary for all archs. + + One can see in the amd64 package listing for Focal [1,2] and Groovy + [3,4] that libjfxmedia.so and libjfxwebkit.so are only available on + arm64, armhf, ppc64el, and s390x. + + [1] https://packages.ubuntu.com/search?searchon=contents=libjfxmedia.so=exactfilename=focal=any + [2] https://packages.ubuntu.com/search?searchon=contents=libjfxwebkit.so=exactfilename=focal=any + [3] https://packages.ubuntu.com/search?searchon=contents=libjfxmedia.so=exactfilename=groovy=any + [4] https://packages.ubuntu.com/search?searchon=contents=libjfxwebkit.so=exactfilename=groovy=any + + + Another possible test case is running pdfsam in the console to split a PDF file (after pdfsam bug 1887142 is fixed) and look if errors as: + Caused by: java.lang.UnsatisfiedLinkError: no jfxmedia in java.library.path: [/usr/java/packages/lib, /usr/lib/x86_64-linux-gnu/jni, /lib/x86_64-linux-gnu, /usr/lib/x86_64-linux-gnu, /usr/lib/jni, /lib, /usr/lib] + show up in the stdout. A sound should be played if everything works. + + + [Regression Potential] + Enabling the native libraries will allow applications to use them again. + * This can trigger errors in applications that were not detected while the libraries were missing. + * This can cause applications that use OpenJFX to fail to run or crash during runtime. + It is unlikely that autopkgtest will detect such errors given that OpenJFX _did_ migrate when the native libraries were missing (and should have caused errors). + + [Other Info] + + + [Original Report] + I'm trying to run BlueJ on Ubuntu 20.04 (fresh install), while the main app runs the editor refuses to start, looking at its logs apparently it can't find jfxwebkit. So I tried to search for it, and apparently it is present in the other architectures for Focal as well as all architectures in Eoan, Bionic and Xenial in the libopenjfx-jni package, but not for Focal amd64. The version of openjfx I have is 11.0.7+0-2ubuntu1. I have also attached BlueJ's log for reference. ** Tags added: groovy ** Summary changed: - openjdk is missing native libraries for webkit and media + openjfx is missing native libraries for webkit and media -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877000 Title: openjfx is missing native libraries for webkit and media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1877000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877000] Re: openjdk is missing native libraries for webkit and media
** Summary changed: - libjfxwebkit not present in the package for Focal amd64 + openjdk is missing native libraries for webkit and media -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877000 Title: openjdk is missing native libraries for webkit and media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1877000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887142] Re: libhibernate-validator-java should be kept at 4.3.4-1
** Description changed: - pdfsam does not produce an output file because of various java- - exceptions. + [Impact] + Debian started migrating from libgeronimo-validation-1.0-spec-java to libgeronimo-validation-1.1-spec-java quite a while ago. Unfortunately both packages implement different Bean Validation Specs and are not compatible, thus all (build-)dependencies and reverse (build-)dependencies must use the same package to avoid FTBFS or runtime issues. This transition has not yet been completed and both Focal and Groovy ended up with mixed dependencies. + + So far 2 packages seem to be affected by this: + 1) pdfsam will start but can act (split/merge/etc) on any pdf + 2) libspring-java FTBFS + + Both depend indirectly on libgeronimo-validation-1.1-spec-java through + libhibernate-validator-java. + + pdfsam depends on libgeronimo-validation-1.0-spec-java through libsejda- + java, while libspring-java depends on 1.0 through through libspring- + java. + + The easiest fix is to downgrade libhibernate-validator-java from 5.3.6-1 + to 4.3.4-1. Trying to update all dependencies to use libgeronimo- + validation-1.1-spec-java is problematic, requires new packages, and even + some dependencies that have not yet been packaged or tested well. + + + [Test Case] + 1) On Focal and Groovy, install pdfsam and run it + $ sudo apt get install -y pdfsam + $ pdfsam + 2) Split a PDF + + Expected result: + For the action to execute correctly. + + Actual result: + The console shows a java stacktrace such as + ERROR 15:56:04.873 org.pdfsam.UncaughtExceptionLogger[JavaFX Application Thread] Unexpected error + org.sejda.eventstudio.exception.EventStudioException: Reflective method invocation exception + ... + + + [Regression Potential] + I haven't found packages that depend on libhibernate-validator-java and on validation-1.1-spec-java directly or indirectly, but I haven't looked at a depth bigger than 3. If there are packages with (indirect) dependencies on both libhibernate-validator-java and libgeronimo-validation-1.1-spec-java they will regress after this change. + + + [Other Info] + * On Debian unstable a new package called libhibernate-validator4-java has been created to deal with this problem, but it is not enough and it is even blocking from moving to testing. + * For pdfsam I tried to move libsejda-java to 1.1 spec, but as described in debian bug 942507 comment 10 it introduces new dependencies and one dependency on el-impl that is not packaged yet. + + + [Original Report] + pdfsam does not produce an output file because of various java-exceptions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pdfsam 4.0.4-1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 10 11:46:14 2020 InstallationDate: Installed on 2019-09-09 (304 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pdfsam UpgradeStatus: No upgrade log present (probably fresh install) ** Tags added: groovy ** Description changed: - [Impact] - Debian started migrating from libgeronimo-validation-1.0-spec-java to libgeronimo-validation-1.1-spec-java quite a while ago. Unfortunately both packages implement different Bean Validation Specs and are not compatible, thus all (build-)dependencies and reverse (build-)dependencies must use the same package to avoid FTBFS or runtime issues. This transition has not yet been completed and both Focal and Groovy ended up with mixed dependencies. + [Impact] + Debian started migrating from libgeronimo-validation-1.0-spec-java to libgeronimo-validation-1.1-spec-java quite a while ago. Unfortunately both packages implement different Bean Validation Specs and are not compatible, thus all reverse (build-)dependencies and reverse (build-)dependencies of these spec packages must rely solely on the 1.0 or 1.1 version to avoid FTBFS or runtime issues. This transition has not yet been completed on Debian and both Focal and Groovy ended up with mixed dependencies. - So far 2 packages seem to be affected by this: - 1) pdfsam will start but can act (split/merge/etc) on any pdf - 2) libspring-java FTBFS + So far 2 packages seem to be affected by this and have regressed since Focal: + 1) pdfsam will start but can't split/merge/etc pdfs + 2) libspring-java FTBFS Both depend indirectly on libgeronimo-validation-1.1-spec-java through libhibernate-validator-java. pdfsam depends on libgeronimo-validation-1.0-spec-java through libsejda- java, while libspring-java depends on 1.0 through through libspring- java. The easiest fix is to downgrade libhibernate-validator-java from 5.3.6-1 to 4.3.4-1. Trying to update all dependencies to use libgeronimo- validation-1.1-spec-java is problematic, requires new
[Bug 1887142] Re: libhibernate-validator-java should be kept at 4.3.4-1
** Also affects: libspring-java (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942814 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887142 Title: libhibernate-validator-java should be kept at 4.3.4-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhibernate-validator-java/+bug/1887142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887142] Re: libhibernate-validator-java should be kept at 4.3.4-1
** Summary changed: - pdfsam does not produce output + libhibernate-validator-java should be kept at 4.3.4-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887142 Title: libhibernate-validator-java should be kept at 4.3.4-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhibernate-validator-java/+bug/1887142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880597] Re: Pdfsam fails splitting a 4 pages PDF
*** This bug is a duplicate of bug 1887142 *** https://bugs.launchpad.net/bugs/1887142 ** This bug has been marked a duplicate of bug 1887142 pdfsam does not produce output -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880597 Title: Pdfsam fails splitting a 4 pages PDF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1880597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882617] Re: OpenJDK 11 breaks when running on armhf
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 in advance. ** Changed in: openjdk-lts (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882617 Title: OpenJDK 11 breaks when running on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1882617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882208] Re: undefined symbol: JLI_StringDup
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 1882208 and any other logs that are relevant for this particular issue - specially hs_err_log files. ** Changed in: openjdk-lts (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882208 Title: undefined symbol: JLI_StringDup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1882208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561587] Re: java crashed with SIGSEGV in newEntry.isra.4()
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 1561587 and any other logs that are relevant for this particular issue. ** Changed in: openjdk-8 (Ubuntu) Status: New => Incomplete ** No longer affects: ubuntu ** Project changed: openjdk => openjdk-8-jre-dcevm (Ubuntu) ** No longer affects: openjdk-8-jre-dcevm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561587 Title: java crashed with SIGSEGV in newEntry.isra.4() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1561587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895596] Re: OpenJdk 11 headless crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please check if there are any .crash files in /var/crash that seem related to this and then upload them by running $ apport-bug /var/crash Please let us know when that is done. Thanks! ** Changed in: openjdk-lts (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895596 Title: OpenJdk 11 headless crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1895596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875918] Re: openjdk crash: jdk11+eclipse+jformdesigner
Running JFormDesigner 7.0.1 works fine under Ubuntu running OpenJDK 11.0.8 (11.0.8+10-0ubuntu1~20.04) - it shows a screen asking for registration. I don't have a license to go further than that. The original report does not clarify if this was the screen that crashed or if one needed a license so the file can be opened - if so, please provide a reproducer that don't require a license to be run. Unfortunately JFormDesigner's 7.0.2 update disabled running it under Ubuntu's OpenJDK. After creating a new JForm it shows a screen asking the user to download a JVM from AdoptOpenJDK. The company does not provide a bug tracker to follow up on this. Setting the bug as Incomplete for Focal since we need, at minimum, more detailed debug information to see where the crash is happening on Java and the native stack. A non-proprietary reproducer would be ideal. ** Changed in: openjdk-lts (Ubuntu Focal) Status: New => Incomplete ** Changed in: openjdk-lts (Ubuntu) Importance: High => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875918 Title: openjdk crash: jdk11+eclipse+jformdesigner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1875918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834265] Re: scilab fails to start missing java-8-oracle
** Changed in: scilab (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834265 Title: scilab fails to start missing java-8-oracle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1834265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870813] Re: Scilab does not start on bionic and focal
** Description changed: - [Impact] - Scilab does not start. This is a regression from an OpenJDK 11 updated. + [Impact] + Scilab does not start. This is a regression from an OpenJDK 11 update. + + SRU TEAM: please note that scilab runs OpenJDK 8 and since Bionic we have been forcing it to use OpenJDK 11 (see bug 1814133). Since the last Bionic and Focal update there have been fixes from both upstream and Debian to improve compatibility. Apart from those fixes I would like to bring additional fixes to our LTS releases and align them better with the one on Groovy (which works fine): + * improved dependencies + * appdata/desktop fixes to improve user experience + * update from 6.0.1 to 6.0.2 in Bionic + [Test Case] On Bionic or Focal: Steps to reproduce: 1. Install Scilab with `sudo apt-get install scilab` 2. Try to launch Scilab from terminal by using command `scilab` Expected results: * Scilab started normally Actual results: * Scilab does not start, shows the following output in the terminal: $ scilab Picked up _JAVA_OPTIONS: -Djava.class.path=/usr/share/java/flexdock.jar:/usr/share/java/skinlf.jar:/usr/share/java/looks.jar:/usr/share/java/commons-logging.jar:/usr/share/java/jhall.jar:/usr/share/java/lucene-core-4.10.4.jar:/usr/share/java/lucene-analyzers-common-4.10.4.jar:/usr/share/java/lucene-queryparser-4.10.4.jar:/usr/share/maven-repo/org/freehep/freehep-util/debian/freehep-util-debian.jar:/usr/share/maven-repo/org/freehep/freehep-io/debian/freehep-io-debian.jar:/usr/share/maven-repo/org/freehep/freehep-graphicsio/debian/freehep-graphicsio-debian.jar:/usr/share/java/freehep-graphicsio-emf-2.1.jar:/usr/share/java/freehep-graphics2d-2.1.1.jar:/usr/share/java/jrosetta-API.jar:/usr/share/java/jrosetta-engine-1.0.4.jar:/usr/share/java/jgraphx.jar:/usr/share/java/jogl2.jar:/usr/share/java/gluegen2-rt.jar:/usr/share/java/jeuclid-core.jar:/usr/share/java/jlatexmath-fop-1.0.7.jar:/usr/share/java/fop.jar:/usr/share/java/saxon.jar:/usr/share/java/batik.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/jlatexmath-1.0.7.jar:/usr/share/java/ecj.jar:/usr/share/java/javax.activation.jar:/usr/share/java/jaxb-runtime.jar:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar:/usr/share/scilab/modules/completion/jar/org.scilab.modules.completion.jar:/usr/share/scilab/modules/graphic_export/jar/org.scilab.modules.graphic_export.jar:/usr/share/scilab/modules/external_objects_java/tests/libintl.jar:/usr/share/scilab/modules/external_objects_java/jar/org.scilab.modules.external_objects_java.jar:/usr/share/scilab/modules/scirenderer/jar/scirenderer.jar:/usr/share/scilab/modules/action_binding/jar/org.scilab.modules.action_binding.jar:/usr/share/scilab/modules/history_manager/jar/org.scilab.modules.history_manager.jar:/usr/share/scilab/modules/console/jar/org.scilab.modules.console.jar:/usr/share/scilab/modules/graphic_objects/jar/org.scilab.modules.graphic_objects.jar:/usr/share/scilab/modules/xcos/jar/org.scilab.modules.xcos.jar:/usr/share/scilab/modules/commons/jar/org.scilab.modules.commons.jar:/usr/share/scilab/modules/graph/jar/org.scilab.modules.graph.jar:/usr/share/scilab/modules/gui/jar/org.scilab.modules.gui.jar:/usr/share/scilab/modules/renderer/jar/org.scilab.modules.renderer.jar:/usr/share/scilab/modules/helptools/jar/scilab_ja_JP_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_fr_FR_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_pt_BR_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_ru_RU_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_en_US_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_images.jar:/usr/share/scilab/modules/helptools/jar/org.scilab.modules.helptools.jar:/usr/share/scilab/modules/types/jar/org.scilab.modules.types.jar:/usr/share/scilab/modules/localization/jar/org.scilab.modules.localization.jar:/usr/share/scilab/modules/javasci/jar/org.scilab.modules.javasci.jar:/usr/share/scilab/modules/preferences/jar/org.scilab.modules.preferences.jar:/usr/share/scilab/modules/core/jar/org.scilab.modules.core.jar:/usr/share/scilab/modules/history_browser/jar/org.scilab.modules.history_browser.jar:/usr/share/scilab/modules/ui_data/jar/org.scilab.modules.ui_data.jar:/usr/share/scilab/modules/scinotes/jar/org.scilab.modules.scinotes.jar: WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.scilab.modules.jvm.LibraryPath (file:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar) to field java.lang.ClassLoader.sys_paths WARNING: Please consider reporting this to the maintainers of org.scilab.modules.jvm.LibraryPath WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Could not access to the Main Scilab Class:
[Bug 1767082] Re: Scilab 6.0.1 shows on start warning in terminal - /usr/share/java/jlatexmath-fop-1.0.6.jar, but there is /usr/share/java/jlatexmath-fop-1.0.7.jar in repository
This was fixed in scilab 6.0.1-7ubuntu1~18.04, so closing this bug. Please note that scilab still has problems starting due to LP:# 1870813. ** Changed in: scilab (Ubuntu) Status: Confirmed => Fix Released ** No longer affects: libjlatexmath-java (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767082 Title: Scilab 6.0.1 shows on start warning in terminal - /usr/share/java /jlatexmath-fop-1.0.6.jar, but there is /usr/share/java/jlatexmath- fop-1.0.7.jar in repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1767082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765503] Re: scilab: hdf5 is broken in Scilab 6.0 on bionic
** Description changed:
+ [Impact]
+ Scilab 6.0 requires hdf5 1.8 to work, but since Bionic we are shipping HDF5
1.10. This makes hdf5 unusable with Scilab 6.0. Scilab needs to be patched to
work with hdf5 1.10 or updated from 6.0 to 6.1.
+
+ [Test Case]
+ = Expected result =
+
+ $ scilab-cli
+ --> test_run('hdf5')
+TMPDIR = /tmp/SCI_TMP_10959_EouWeO
+
+ Module 001/001 - [hdf5] :
+
+001/052 - [hdf5] binary_bit-for-bit..passed
+002/052 - [hdf5] h5attr..passed
+003/052 - [hdf5] h5close.passed
+004/052 - [hdf5] h5cppassed
+005/052 - [hdf5] h5dataset...passed
+006/052 - [hdf5] h5existspassed
+007/052 - [hdf5] h5flush.passed
+008/052 - [hdf5] h5group.passed
+009/052 - [hdf5] h5isAttrpassed
+010/052 - [hdf5] h5isFilepassed
+011/052 - [hdf5] h5isGroup...passed
+012/052 - [hdf5] h5isRef.passed
+013/052 - [hdf5] h5isSet.passed
+014/052 - [hdf5] h5isSpace...passed
+015/052 - [hdf5] h5isTypepassed
+016/052 - [hdf5] h5label.passed
+017/052 - [hdf5] h5lnpassed
+018/052 - [hdf5] h5lspassed
+019/052 - [hdf5] h5mount.passed
+020/052 - [hdf5] h5mvpassed
+021/052 - [hdf5] h5open..passed
+022/052 - [hdf5] h5read..passed
+023/052 - [hdf5] h5readattr..passed
+024/052 - [hdf5] h5rmpassed
+025/052 - [hdf5] h5umountpassed
+026/052 - [hdf5] h5write.passed
+027/052 - [hdf5] loadhdf5datapassed
+028/052 - [hdf5] loadhdf5data_v1.passed
+029/052 - [hdf5] saveloadHdf5passed
+030/052 - [hdf5] bug_11954...passed
+031/052 - [hdf5] bug_12285...passed
+032/052 - [hdf5] bug_13689...passed
+033/052 - [hdf5] bug_13941...passed
+034/052 - [hdf5] bug_14149...passed
+035/052 - [hdf5] bug_14446...passed
+036/052 - [hdf5] bug_14775...passed
+037/052 - [hdf5] bug_14886...failed:
error_output not empty
+ Use
'no_check_error_output' option to disable this check.
+038/052 - [hdf5] bug_15188...failed:
error_output not empty
+ Use
'no_check_error_output' option to disable this check.
+039/052 - [hdf5] bug_15302...failed:
error_output not empty
+ Use
'no_check_error_output' option to disable this check.
+040/052 - [hdf5] bug_15501...passed
+041/052 - [hdf5] bug_15502...passed
+042/052 - [hdf5] bug_15692...passed
+043/052 - [hdf5] bug_15693...passed
+044/052 - [hdf5] bug_15721...passed
+045/052 - [hdf5] bug_15809...passed
+046/052 - [hdf5] bug_5629passed
+047/052 - [hdf5] bug_6440passed
+048/052 - [hdf5] bug_7224failed:
error_output not empty
+ Use
'no_check_error_output' option to disable this check.
+049/052 - [hdf5] bug_8170failed:
error_output not empty
+ Use
'no_check_error_output' option to disable this check.
+050/052 - [hdf5] bug_8383passed
+051/052 - [hdf5] bug_9510passed
+052/052 - [hdf5] matrix_as_input.passed
+
+
[Bug 1765503] Re: scilab: hdf5 is broken in Scilab 6.0 on bionic
** Summary changed: - scilab: save, open and ATOMS system is broken in Scilab 6 on bionic, cosmic, disco and eoan + scilab: hdf5 is broken in Scilab 6.0 on bionic ** No longer affects: scilab (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765503 Title: scilab: hdf5 is broken in Scilab 6.0 on bionic To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1765503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765503] Re: scilab: save, open and ATOMS system is broken in Scilab 6 on bionic, cosmic, disco and eoan
** Also affects: hdf5 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: scilab (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: hdf5 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: scilab (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: hdf5 (Ubuntu) ** No longer affects: hdf5 (Ubuntu Bionic) ** No longer affects: hdf5 (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765503 Title: scilab: save, open and ATOMS system is broken in Scilab 6 on bionic, cosmic, disco and eoan To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1765503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870813] Re: Scilab does not start on bionic and focal
** Also affects: scilab (Ubuntu Groovy) Importance: Undecided Status: Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870813 Title: Scilab does not start on bionic and focal To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1870813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775219] Re: incorrectly reports package as unsupported if apt cache is empty
** Branch linked: lp:~tdaitx/ubuntu/groovy/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775219 Title: incorrectly reports package as unsupported if apt cache is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1775219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870813] Re: Scilab does not start on bionic and focal
** Changed in: scilab (Ubuntu Bionic) Importance: Undecided => High ** Changed in: scilab (Ubuntu Focal) Importance: Undecided => High ** Changed in: scilab (Ubuntu Bionic) 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/1870813 Title: Scilab does not start on bionic and focal To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1870813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870813] Re: Scilab does not start on bionic and focal
Norbert, thanks for the updates. The package has been uploaded to Focal and is waiting approval. As for Bionic, I will cherry pick some patches. Scilab 6.1 introduced the fileio module which depends on std::filesystem::weakly_canonical that is only available on libstdc++-8. Bionic uses gcc/g++ 7 by default, so we are not recompiling scilab with gcc/g++ 8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870813 Title: Scilab does not start on bionic and focal To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1870813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870813] Re: Scilab does not start on bionic and focal
** Summary changed: - Scilab does not start on focal + Scilab does not start on bionic and focal ** Tags added: bionic rls-bb-incoming rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870813 Title: Scilab does not start on bionic and focal To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1870813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826455] Re: update to openjdk 11.0.3 in 18.04 LTS
** Changed in: openjdk-lts (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.net/bugs/1826455 Title: update to openjdk 11.0.3 in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1826455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870813] Re: Scilab does not start on focal
Added bionic task. Removed java-common and openjdk-lts as being affected. ** Description changed: + [Impact] + Scilab does not start. This is a regression from an OpenJDK 11 updated. + + [Test Case] + On Bionic or Focal: + Steps to reproduce: - 1. Have Ubuntu 20.04 LTS beta installed - 2. Install Scilab with `sudo apt-get install scilab` - 3. Try to launch Scilab from terminal by using command `scilab` + 1. Install Scilab with `sudo apt-get install scilab` + 2. Try to launch Scilab from terminal by using command `scilab` Expected results: * Scilab started normally Actual results: * Scilab does not start, shows the following output in the terminal: $ scilab Picked up _JAVA_OPTIONS: -Djava.class.path=/usr/share/java/flexdock.jar:/usr/share/java/skinlf.jar:/usr/share/java/looks.jar:/usr/share/java/commons-logging.jar:/usr/share/java/jhall.jar:/usr/share/java/lucene-core-4.10.4.jar:/usr/share/java/lucene-analyzers-common-4.10.4.jar:/usr/share/java/lucene-queryparser-4.10.4.jar:/usr/share/maven-repo/org/freehep/freehep-util/debian/freehep-util-debian.jar:/usr/share/maven-repo/org/freehep/freehep-io/debian/freehep-io-debian.jar:/usr/share/maven-repo/org/freehep/freehep-graphicsio/debian/freehep-graphicsio-debian.jar:/usr/share/java/freehep-graphicsio-emf-2.1.jar:/usr/share/java/freehep-graphics2d-2.1.1.jar:/usr/share/java/jrosetta-API.jar:/usr/share/java/jrosetta-engine-1.0.4.jar:/usr/share/java/jgraphx.jar:/usr/share/java/jogl2.jar:/usr/share/java/gluegen2-rt.jar:/usr/share/java/jeuclid-core.jar:/usr/share/java/jlatexmath-fop-1.0.7.jar:/usr/share/java/fop.jar:/usr/share/java/saxon.jar:/usr/share/java/batik.jar:/usr/share/java/xml-apis-ext.jar:/usr/share/java/commons-io.jar:/usr/share/java/xmlgraphics-commons.jar:/usr/share/java/avalon-framework.jar:/usr/share/java/jlatexmath-1.0.7.jar:/usr/share/java/ecj.jar:/usr/share/java/javax.activation.jar:/usr/share/java/jaxb-runtime.jar:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar:/usr/share/scilab/modules/completion/jar/org.scilab.modules.completion.jar:/usr/share/scilab/modules/graphic_export/jar/org.scilab.modules.graphic_export.jar:/usr/share/scilab/modules/external_objects_java/tests/libintl.jar:/usr/share/scilab/modules/external_objects_java/jar/org.scilab.modules.external_objects_java.jar:/usr/share/scilab/modules/scirenderer/jar/scirenderer.jar:/usr/share/scilab/modules/action_binding/jar/org.scilab.modules.action_binding.jar:/usr/share/scilab/modules/history_manager/jar/org.scilab.modules.history_manager.jar:/usr/share/scilab/modules/console/jar/org.scilab.modules.console.jar:/usr/share/scilab/modules/graphic_objects/jar/org.scilab.modules.graphic_objects.jar:/usr/share/scilab/modules/xcos/jar/org.scilab.modules.xcos.jar:/usr/share/scilab/modules/commons/jar/org.scilab.modules.commons.jar:/usr/share/scilab/modules/graph/jar/org.scilab.modules.graph.jar:/usr/share/scilab/modules/gui/jar/org.scilab.modules.gui.jar:/usr/share/scilab/modules/renderer/jar/org.scilab.modules.renderer.jar:/usr/share/scilab/modules/helptools/jar/scilab_ja_JP_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_fr_FR_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_pt_BR_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_ru_RU_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_en_US_help.jar:/usr/share/scilab/modules/helptools/jar/scilab_images.jar:/usr/share/scilab/modules/helptools/jar/org.scilab.modules.helptools.jar:/usr/share/scilab/modules/types/jar/org.scilab.modules.types.jar:/usr/share/scilab/modules/localization/jar/org.scilab.modules.localization.jar:/usr/share/scilab/modules/javasci/jar/org.scilab.modules.javasci.jar:/usr/share/scilab/modules/preferences/jar/org.scilab.modules.preferences.jar:/usr/share/scilab/modules/core/jar/org.scilab.modules.core.jar:/usr/share/scilab/modules/history_browser/jar/org.scilab.modules.history_browser.jar:/usr/share/scilab/modules/ui_data/jar/org.scilab.modules.ui_data.jar:/usr/share/scilab/modules/scinotes/jar/org.scilab.modules.scinotes.jar: WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.scilab.modules.jvm.LibraryPath (file:/usr/share/scilab/modules/jvm/jar/org.scilab.modules.jvm.jar) to field java.lang.ClassLoader.sys_paths WARNING: Please consider reporting this to the maintainers of org.scilab.modules.jvm.LibraryPath WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Could not access to the Main Scilab Class: Exception in thread "main" java.lang.ExceptionInInitializerError - at org.scilab.modules.localization.Messages.gettext(Unknown Source) - at org.scilab.modules.commons.xml.XConfiguration.(Unknown Source) - at org.scilab.modules.core.Scilab.(Unknown Source) + at org.scilab.modules.localization.Messages.gettext(Unknown Source) + at
[Bug 1870813] Re: Scilab does not start on focal
Backporting some selected fixes from Groovy works ok on Focal. Norbert, assuming scilab 6.1 works on Bionic, do you see or know any limitations/problems of upgrading Bionic's scilab from 6.0 to 6.1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870813 Title: Scilab does not start on focal To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1870813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884277] Re: Scilab does not start on Ubuntu 18.04 LTS bionic beaver
*** This bug is a duplicate of bug 1870813 *** https://bugs.launchpad.net/bugs/1870813 ** This bug has been marked a duplicate of bug 1870813 Scilab does not start on focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884277 Title: Scilab does not start on Ubuntu 18.04 LTS bionic beaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1884277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877234] Re: Scilab 6.0.2 crashes on startup
*** This bug is a duplicate of bug 1870813 *** https://bugs.launchpad.net/bugs/1870813 ** This bug has been marked a duplicate of bug 1870813 Scilab does not start on focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877234 Title: Scilab 6.0.2 crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1877234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887664] Re: python_dateutil get_zonefile_instance functionality is broken without upstream tarball
Thank you for taking the time to report this bug and helping to make Ubuntu better. Is there any reason why 'dateutil.tz' can't be used instead of dateutil.zoneinfo? The original bug report was made against python- sqlalchemy-utils, which seems to indicate that some functionatility of it might be making use of dateutil.zoneinfo instead of dateutil.tz. Some context: python-dateutil’s zoneinfo tarball is not included in the binary package since 1.4.1-1ubuntu2 (from 28 Sep 2008) [1]. The dateutil.zoneinfo is expected to use the shipped tarball instead of the system’s tzdata. Unfortunately shipping copies zoneinfo data goes against Debian and Ubuntu policies - specially for outdated copies. See the original bug report for that in Debian [2]. The usual way to access timezone data is by relying on dateutil.tz: it is designed to use the system's zoneinfo first, with dateutil.zoneinfo as a fallback. Debian and Ubuntu ship tzdata with current zoneinfo, thus the dateutil.zoneinfo code is never used - it seems it is there basically for Windows, since Windows provides no API for timezone data. On a side note: PEP 615 [3] has been approved for Python 3.9 and so python-dateutil will no longer be required in the future - there’s also some plans to include it as a backport for 3.6+. Bug will be marked as incomplete while we wait for more information. Feel free to reply back and change its status after updating the report. Thanks! References: [1] https://launchpad.net/ubuntu/+source/python-dateutil/1.4-1ubuntu2 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416204 [3] https://www.python.org/dev/peps/pep-0615/ ** Bug watch added: Debian Bug tracker #416204 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416204 ** Changed in: python-dateutil (Ubuntu Groovy) Status: Triaged => Incomplete ** Changed in: python-sqlalchemy-utils (Ubuntu Groovy) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887664 Title: python_dateutil get_zonefile_instance functionality is broken without upstream tarball To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-dateutil/+bug/1887664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870088] Re: xz-utils ftbfs in focal
** Tags removed: block-proposed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870088] Re: xz-utils ftbfs in focal
** Changed in: xz-utils (Ubuntu Focal) Status: Confirmed => 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/1870088 Title: xz-utils ftbfs in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870088] Re: xz-utils ftbfs in focal
Installed xz-utils 5.2.4-1ubuntu1 on Focal from focal-proposed, works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870088] Re: xz-utils ftbfs in focal
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887587] Re: jtreg fails to locate its own lib directory
** Bug watch added: Debian Bug tracker #965047 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965047 ** Also affects: jtreg (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965047 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887587 Title: jtreg fails to locate its own lib directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jtreg/+bug/1887587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887587] [NEW] jtreg fails to locate its own lib directory
Public bug reported:
Since jtreg 5.1-b01-1 it will no longer run without having JTREG_HOME
(or JT_HOME) explicitly set on the environment, previous versions worked
ok.
It will exit 1 when trying to run it:
$ jtreg
Cannot determine JTREG_HOME; please set it explicitly
The reason is a change in debian/patches/launcher.patch that adds the check
if [ -z "${JTREG_HOME}" ]; then
JTREG_HOME="/usr/share/jtreg"
fi
too further down compared to the previous jtreg version. This causes the
code to search for lib/jtreg.jar in the script's path (/usr/bin) first,
which does not work and then calls exit 1.
That check is added exclusively for Debian/Ubuntu by d/p/launcher.patch
and should come before jtreg will try to look for lib/jtreg.jar by
itself.
** Affects: jtreg (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/1887587
Title:
jtreg fails to locate its own lib directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jtreg/+bug/1887587/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870085] Re: xfsdump ftbfs in focal (all archs)
Version 3.1.9 builds fine on Groovy. ** Changed in: xfsdump (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870085 Title: xfsdump ftbfs in focal (all archs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsdump/+bug/1870085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870215] Re: autopkgtest fails due to tests/test_gil.py::TestGIL::test_rectbivariatespline being killed by oom killer
Attaching debdiff in case scipy's autopkgtest must be run in a low ram scenario. ** Patch added: "scipy_1.3.3-3build1__1.3.3-3ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/scipy/+bug/1870215/+attachment/5344438/+files/scipy_1.3.3-3build1__1.3.3-3ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870215 Title: autopkgtest fails due to tests/test_gil.py::TestGIL::test_rectbivariatespline being killed by oom killer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scipy/+bug/1870215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870215] Re: autopkgtest fails due to tests/test_gil.py::TestGIL::test_rectbivariatespline being killed by oom killer
Due to the package name change (python-scipy to scipy) it was no longer being run in autopkgtest's big_instance, thus the failure. So as an alternative to low ram systems the proposed merge does workaround the issue and no debdiff is required. ** Description changed: Recent autopkgtest runs of scipy have been failing due to tests/test_gil.py::TestGIL::test_rectbivariatespline causing the python interpreter to be killed by OOM killer as the autopkgtest instance usually does not have enough RAM to run it. An example of a run failure can be seen at [1]. - Local tests indicate that TestGIL::test_rectbivariatespline requires at - least 2.5 GiB of available RAM to pass. + Local tests indicate that TestGIL::test_rectbivariatespline requires + about 1.5 GiB of available RAM to pass. The test needs to be skipped for the autopkgtest to pass. It can be done by: 1. Adding a @pytest.mark.skipif decorator to it to check for ram availability 2. Adding a @pytest.mark.skip to it to always skip, even when the instance could run it 3. Skipping it in scipy/conftest.py by adding a clause to check for the item.nodeid in the pytest_runtest_setup(item) function. All options require a patch in debian/patches. The code under debian/tests/python3 only set tests as "skipped" *after* they have been run, directly over the results in junit.xml after all tests are run - so it is not an option since the python instance is killed while tests are being run. - References: [1] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/scipy/20200327_041737_f50f1@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870215 Title: autopkgtest fails due to tests/test_gil.py::TestGIL::test_rectbivariatespline being killed by oom killer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scipy/+bug/1870215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870215] [NEW] autopkgtest fails due to tests/test_gil.py::TestGIL::test_rectbivariatespline being killed by oom killer
Public bug reported: Recent autopkgtest runs of scipy have been failing due to tests/test_gil.py::TestGIL::test_rectbivariatespline causing the python interpreter to be killed by OOM killer as the autopkgtest instance usually does not have enough RAM to run it. An example of a run failure can be seen at [1]. Local tests indicate that TestGIL::test_rectbivariatespline requires at least 2.5 GiB of available RAM to pass. The test needs to be skipped for the autopkgtest to pass. It can be done by: 1. Adding a @pytest.mark.skipif decorator to it to check for ram availability 2. Adding a @pytest.mark.skip to it to always skip, even when the instance could run it 3. Skipping it in scipy/conftest.py by adding a clause to check for the item.nodeid in the pytest_runtest_setup(item) function. All options require a patch in debian/patches. The code under debian/tests/python3 only set tests as "skipped" *after* they have been run, directly over the results in junit.xml after all tests are run - so it is not an option since the python instance is killed while tests are being run. References: [1] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/scipy/20200327_041737_f50f1@/log.gz ** Affects: scipy (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/1870215 Title: autopkgtest fails due to tests/test_gil.py::TestGIL::test_rectbivariatespline being killed by oom killer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scipy/+bug/1870215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859217] Re: openjdk8 update 8u232-b09-0ubuntu1~18.04.1 breaks Timestamp values for timezones that change DST observance
Thank you for taking the time to report this bug and helping to make Ubuntu better. The changes come from the update to tzdata2019c [1] which was done at a later time in OpenJDK 11 - in fact the newer OpenJDK 11.0.6 reports the same results as OpenJDK 8u232. OpenJDK 11.0.6 is available in focal- proposed as of now and will available in supported Ubuntu releases soon. The announcement for tzdata2019c [2] does state that past timestamps for Turkey changed and the OpenJDK commit [1] has the references to the changes. To check if OpenJDK itself was somehow incorrectly interpreting the data I also run the following using 'date' which uses the system's timezone data (also sourced from tzdata2019c). Results matches the OpenJDK output: $ date --date='TZ="Europe/Istanbul" 1943-01-01 12:01:01' '+%s' -852044339 Please note that date is limited to 'seconds' precision for the epoch. If that is somehow wrong, it should be brought to the attention of the maintainers of tzdata through the t...@iana.org mailing list as stated in [3]. I'm closing this bug now. References: [1] https://hg.openjdk.java.net/jdk8u/jdk8u-dev/jdk/rev/8560bc534080#l4.130 [2] https://mm.icann.org/pipermail/tz-announce/2019-September/57.html [3] https://www.iana.org/time-zones ** Changed in: openjdk-8 (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/1859217 Title: openjdk8 update 8u232-b09-0ubuntu1~18.04.1 breaks Timestamp values for timezones that change DST observance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1859217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855484] Re: OpenJDK 8u232 not available for Bionic
Thank you for taking the time to report this bug and helping to make Ubuntu better. OpenJDK 8u232 was updated a month ago and we are now working on 8u242. ** Changed in: openjdk-8 (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.net/bugs/1855484 Title: OpenJDK 8u232 not available for Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1855484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845359] Re: Do not migrate openjdk-8 release candidate
** Changed in: openjdk-8 (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/1845359 Title: Do not migrate openjdk-8 release candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1845359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842046] Re: eclipse installer from eclipse-2019-06 seg-faults on Ubuntu/Bionic-current
Marking as invalid since we can't reproduce it. ** Changed in: openjdk-lts (Ubuntu) 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/1842046 Title: eclipse installer from eclipse-2019-06 seg-faults on Ubuntu/Bionic- current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1842046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850608] Re: Segfaults trying to send crash report
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850608 Title: Segfaults trying to send crash report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1850608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838740] Re: libjawt.so inconsistency lets JVM crash
Also reproducible with OpenJDK 11.0.5+10-2ubuntu1 in Focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838740 Title: libjawt.so inconsistency lets JVM crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1838740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour
I tested the initramfs-tools in xenial-proposed, bionic-proposed, and disco-proposed with all 3 testcases (panic=-1, panic=10, and no panic), everything worked as expected: - panic=-1 rebooted instantly after the root partition is not found - panic=10 rebooted after 10 seconds - no "panic" entry caused to drop into a basic shell ii initramfs-tools 0.122ubuntu8.16 all generic modular initramfs generator (automation) ii initramfs-tools 0.130ubuntu3.9 all generic modular initramfs generator (automation) ii initramfs-tools 0.131ubuntu19.2 all generic modular initramfs generator (automation) multipass@xenial:~$ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.122ubuntu8.16 Candidate: 0.122ubuntu8.16 Version table: *** 0.122ubuntu8.16 400 400 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.122ubuntu8.15 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 0.122ubuntu8.14 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 0.122ubuntu8 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages multipass@bionic:~$ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.130ubuntu3.9 Candidate: 0.130ubuntu3.9 Version table: *** 0.130ubuntu3.9 400 400 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.130ubuntu3.8 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 0.130ubuntu3.6 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 0.130ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages multipass@disco:~$ apt-cache policy initramfs-tools initramfs-tools: Installed: 0.131ubuntu19.2 Candidate: 0.131ubuntu19.2 Version table: *** 0.131ubuntu19.2 400 400 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.131ubuntu19.1 500 500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 0.131ubuntu19 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco verification-needed-xenial ** Tags added: verification-done-bionic verification-done-disco 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/1831252 Title: panic=-1 is completely ignored by the initrd causing unexpected behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845359] Re: Do not migrate openjdk-8 release candidate
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845359 Title: Do not migrate openjdk-8 release candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1845359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845359] [NEW] Do not migrate openjdk-8 release candidate
Public bug reported: openjdk-8 version 8u222-b10-1ubuntu3 is the latest security update while 8u232-* is a release candidate build which should not migrate to the release pocket. ** Affects: openjdk-8 (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845359 Title: Do not migrate openjdk-8 release candidate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1845359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
