[Bug 2063464] Re: systemd-resolved wasn't installed on upgrade from Jammy to Noble
It's not clear to me how to test this package in the context of a `do- release-upgrade`. I tried both `-d` and `-p` to another minimal Jammy server install, but it both denied an upgrade with this message: ``` $ sudo do-release-upgrade -d Checking for a new Ubuntu release There is no development version of an LTS available. To upgrade to the latest non-LTS development release set Prompt=normal in /etc/update-manager/release-upgrades. ``` The upgrade that caused this bug report (see "original report") was done using `-d` – this doesn't work any more at the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: systemd-resolved wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] VarLogDistupgradeApttermlog.txt
apport information ** Attachment added: "VarLogDistupgradeApttermlog.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770666/+files/VarLogDistupgradeApttermlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] VarLogDistupgradeMainlog.txt
apport information ** Attachment added: "VarLogDistupgradeMainlog.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770667/+files/VarLogDistupgradeMainlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] VarLogDistupgradeAptHistorylog.txt
apport information ** Attachment added: "VarLogDistupgradeAptHistorylog.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770663/+files/VarLogDistupgradeAptHistorylog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] VarLogDistupgradeAptlog.txt
apport information ** Attachment added: "VarLogDistupgradeAptlog.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770665/+files/VarLogDistupgradeAptlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] VarLogDistupgradeAptclonesystemstate.tar.gz
apport information ** Attachment added: "VarLogDistupgradeAptclonesystemstate.tar.gz" https://bugs.launchpad.net/bugs/2063464/+attachment/5770664/+files/VarLogDistupgradeAptclonesystemstate.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770662/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770661/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770660/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] Re: Package wasn't installed on upgrade from Jammy to Noble
apport information ** Tags added: apport-collected dist-upgrade ** Description changed: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) + --- + ProblemType: Bug + ApportVersion: 2.28.1-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: unknown + CrashDB: ubuntu + CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash + DistroRelease: Ubuntu 24.04 + Package: ubuntu-release-upgrader (not installed) + ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 + Tags: noble dist-upgrade + Uname: Linux 6.8.0-31-generic x86_64 + UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) + UserGroups: N/A + VarLogDistupgradeXorgFixuplog: + INFO:root:/usr/bin/do-release-upgrade running + INFO:root:No xorg.conf, exiting + _MarkForUpload: True ** Attachment added: "CurrentDmesg.txt.txt" https://bugs.launchpad.net/bugs/2063464/+attachment/5770659/+files/CurrentDmesg.txt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063465] Re: Noble: ModuleNotFoundError: No module named 'distutils'
Indeed, the Jammy package depended on `python3-distutils` but the Noble package does not. I believe this is a packaging bug. https://packages.ubuntu.com/jammy/docker-compose https://packages.ubuntu.com/noble/docker-compose https://packages.ubuntu.com/noble/python3-compose -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063465 Title: Noble: ModuleNotFoundError: No module named 'distutils' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/2063465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063465] Re: Noble: ModuleNotFoundError: No module named 'distutils'
Not sure if this is the right package, but installing `python3-distutils-extra` seems to fix the issue, but now I'm running into a different problem so I'm not absolutely sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063465 Title: Noble: ModuleNotFoundError: No module named 'distutils' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/2063465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063465] [NEW] Noble: ModuleNotFoundError: No module named 'distutils'
Public bug reported:
After an upgrade of my server from Jammy to Noble, I get
```
Traceback (most recent call last):
File "/usr/bin/docker-compose", line 33, in
sys.exit(load_entry_point('docker-compose==1.29.2', 'console_scripts',
'docker-compose')())
^^^
File "/usr/bin/docker-compose", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.12/importlib/metadata/__init__.py", line 205, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1387, in _gcd_import
File "", line 1360, in _find_and_load
File "", line 1331, in _find_and_load_unlocked
File "", line 935, in _load_unlocked
File "", line 995, in exec_module
File "", line 488, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 9, in
from distutils.spawn import find_executable
ModuleNotFoundError: No module named 'distutils'
```
I suspect this is missing a dependency declaration?
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: docker-compose 1.29.2-6ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Apr 25 15:32:27 2024
PackageArchitecture: all
SourcePackage: docker-compose
UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago)
** Affects: docker-compose (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063465
Title:
Noble: ModuleNotFoundError: No module named 'distutils'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker-compose/+bug/2063465/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] [NEW] Package wasn't installed on upgrade from Jammy to Noble
Public bug reported: I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677512] Re: Backporting garbage-collection functionality
I think this can be closed. All supported versions of Ubuntu have docker-registry 2.6 or later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677512 Title: Backporting garbage-collection functionality To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker-registry/+bug/1677512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
I've got this issue on ``` # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal # uname -a Linux ultima 5.4.0-80-generic #90-Ubuntu SMP Fri Jul 9 22:49:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ``` The message is ``` kernel:[864004.039343] unregister_netdevice: waiting for lo to become free. Usage count = 1 ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917509] Re: Call for testing: grub2 security updates
On a focal system all up-to-date, I installed these updates (and only these) from focal-proposed, and everything seems fine. System is booting as normal. grub-common/focal-proposed 2.04-1ubuntu26.11 amd64 [upgradable from: 2.04-1ubuntu26.9] grub-efi-amd64-bin/focal-proposed 2.04-1ubuntu42 amd64 [upgradable from: 2.04-1ubuntu26.9] grub-efi-amd64-signed/focal-proposed 1.164+2.04-1ubuntu42 amd64 [upgradable from: 1.142.11+2.04-1ubuntu26.9] grub-efi-amd64/focal-proposed 2.04-1ubuntu42 amd64 [upgradable from: 2.04-1ubuntu26.9] grub2-common/focal-proposed 2.04-1ubuntu26.11 amd64 [upgradable from: 2.04-1ubuntu26.9] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917509 Title: Call for testing: grub2 security updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1917509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902525] Re: btrfs subvolume list segmentation fault
I'm seeing this on fully-updated Ubuntu 20.04 LTS with stock kernel 5.4.0-52-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902525 Title: btrfs subvolume list segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-progs/+bug/1902525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818549] Re: Can't use the extensions provided by the webext-* packages
There is a separate package chromium-ublock-origin. Maybe try that one for Chromium? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818549 Title: Can't use the extensions provided by the webext-* packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/browserpass/+bug/1818549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
Is there any idea when this OpenJDK 11 transition will happen, and Gradle 4.4.1 be released from bionic-proposed to bionic-updates? No need for an exact date, but will it take more like days or weeks from now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823476] [NEW] Rebuild with OpenSSL 1.1.1
Public bug reported: Now that OpenSSL 1.1.1 is in bionic-proposed and will enter bionic- updates soon, please also rebuild nginx against OpenSSL 1.1.1 so we can make full use of TLSv1.3. Currently OpenSSL 1.1.0 seems to be statically linked. ** Affects: nginx (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/1823476 Title: Rebuild with OpenSSL 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1823476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821235] Re: java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of
Works on Cosmic, too. Thanks! ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821235 Title: java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-tools-apksig/+bug/1821235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821235] Re: java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of
Damn, the repository still had the old version. Now, with the new version, it works. Sorry for that. ** Tags removed: verification-failed-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/1821235 Title: java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-tools-apksig/+bug/1821235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821235] Re: java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of
On Bionic, nothing has changed. $ dpkg -l apksigner Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-=-== ii apksigner 0.8-2~18.04 all command line tool to sign and verify Android APKs $ which apksigner /usr/bin/apksigner $ /usr/bin/apksigner Error: A JNI error has occurred, please check your installation and try again Exception in thread "main" java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:468) at java.net.URLClassLoader.access$100(URLClassLoader.java:74) at java.net.URLClassLoader$1.run(URLClassLoader.java:369) at java.net.URLClassLoader$1.run(URLClassLoader.java:363) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:362) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:495) ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821235 Title: java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-tools-apksig/+bug/1821235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
I've got another regression, this time in ApkSigner: https://bugs.launchpad.net/ubuntu/+source/android-platform-tools- apksig/+bug/1821235 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821235] [NEW] java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version o
Public bug reported: Here is another regression from the new packages in Bionic proposed- updates: $ apksigner Error: A JNI error has occurred, please check your installation and try again Exception in thread "main" java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:468) at java.net.URLClassLoader.access$100(URLClassLoader.java:74) at java.net.URLClassLoader$1.run(URLClassLoader.java:369) at java.net.URLClassLoader$1.run(URLClassLoader.java:363) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:362) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:495) I'm using OpenJDK 8 here. This will be affecting the publishing of Android apps. ApkSigner is the tool you use for signing the Application Archives. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apksigner 0.8-2~18.04 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 21 20:00:32 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (1063 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: android-platform-tools-apksig UpgradeStatus: Upgraded to bionic on 2018-04-26 (328 days ago) ** Affects: android-platform-tools-apksig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821235 Title: java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-tools-apksig/+bug/1821235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797761] Re: Gradle 4.4.1 package missing alternative dep to Java8
Cool, thanks! Works well so far (both Bionic and Cosmic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797761 Title: Gradle 4.4.1 package missing alternative dep to Java8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1797761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820513] Re: android-* packages not working well with OpenJDK 11
Feedback on #2 is contained in https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1820389. As far as I can tell the blocker regressions are gone. However there is still the issue of the missing alternative dependency declaration: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1797761 I cannot tell much about #1, but if someone defines a test procedure I'm happy to help testing. I'd really like to use an Ubuntu/Debian toolchain in future. However I think the libgradle-android-plugin-java package (Android Gradle plugin) is very outdated. I've opened https://bugs.launchpad.net/ubuntu/+source/android-platform-tools- base/+bug/1821073 about this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820513 Title: android-* packages not working well with OpenJDK 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-tools-base/+bug/1820513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821073] [NEW] libgradle-android-plugin-java 2.2.2 is outdated
Public bug reported: Now that Gradle 4.4.1 is about to enter Bionic, and has been available in Cosmic and Dingo for some time, it is safe to say that version 2.2.2 of the Android Gradle plugin is a very outdated match. Looking at https://developer.android.com/studio/releases/gradle-plugin #updating-gradle, version 3.0.1 or 3.1.0 would be more appropriate. It's probably also more compatible to later OpenJDK releases. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgradle-android-plugin-java 2.2.2-3 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 19:42:28 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (1062 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: android-platform-tools-base UpgradeStatus: Upgraded to bionic on 2018-04-26 (327 days ago) ** Affects: android-platform-tools-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821073 Title: libgradle-android-plugin-java 2.2.2 is outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-tools-base/+bug/1821073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797761] Re: Gradle 4.4.1 package missing alternative dep to Java8
#1820389 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797761 Title: Gradle 4.4.1 package missing alternative dep to Java8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1797761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820389] Re: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn()
See https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1797761 for the remaining issue with the alternative dependency declaration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820389 Title: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1820389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797761] Re: Gradle 4.4.1 package missing alternative dep to Java8
I tested all my projects in the Gradle 4.4.1 / OpenJDK 8 combination and I can say it's compatible. So there is no reason to not allow an alternative dependency to OpenJDK 8. For more information see issue 1820389. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797761 Title: Gradle 4.4.1 package missing alternative dep to Java8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1797761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820389] Re: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn()
I rebooted my machine and now everything works. Not sure where the old code was hiding. ** Tags removed: verification-failed-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/1820389 Title: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1820389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820389] Re: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn()
@Tiago: I just tried and the smallest possible project is the empty directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820389 Title: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1820389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820389] Re: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn()
This is about Bionic again. Thanks for mentioning the daemon. I ran $ gradle --no-daemon --stacktrace clean The full exception is: java.lang.ExceptionInInitializerError at org.gradle.internal.classloader.FilteringClassLoader.(FilteringClassLoader.java:48) at org.gradle.initialization.DefaultClassLoaderRegistry.restrictTo(DefaultClassLoaderRegistry.java:40) at org.gradle.initialization.DefaultClassLoaderRegistry.restrictToGradleApi(DefaultClassLoaderRegistry.java:36) at org.gradle.initialization.DefaultClassLoaderRegistry.(DefaultClassLoaderRegistry.java:30) at org.gradle.internal.service.scopes.GlobalScopeServices.createClassLoaderRegistry(GlobalScopeServices.java:207) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73) at org.gradle.internal.service.ReflectionBasedServiceMethod.invoke(ReflectionBasedServiceMethod.java:35) at org.gradle.internal.service.DefaultServiceRegistry$FactoryMethodService.invokeMethod(DefaultServiceRegistry.java:795) at org.gradle.internal.service.DefaultServiceRegistry$FactoryService.create(DefaultServiceRegistry.java:748) at org.gradle.internal.service.DefaultServiceRegistry$ManagedObjectProvider.getInstance(DefaultServiceRegistry.java:574) at org.gradle.internal.service.DefaultServiceRegistry$SingletonService.get(DefaultServiceRegistry.java:623) at org.gradle.internal.service.DefaultServiceRegistry.applyConfigureMethod(DefaultServiceRegistry.java:199) at org.gradle.internal.service.DefaultServiceRegistry.findProviderMethods(DefaultServiceRegistry.java:180) at org.gradle.internal.service.DefaultServiceRegistry.addProvider(DefaultServiceRegistry.java:255) at org.gradle.internal.service.ServiceRegistryBuilder.build(ServiceRegistryBuilder.java:52) at org.gradle.launcher.cli.BuildActionsFactory.runBuildInProcess(BuildActionsFactory.java:129) at org.gradle.launcher.cli.BuildActionsFactory.createAction(BuildActionsFactory.java:90) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.createAction(CommandLineActionFactory.java:296) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:286) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:264) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:33) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:257) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:191) at org.gradle.launcher.Main.doAction(Main.java:33) at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60) at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37) at org.gradle.launcher.GradleMain.main(GradleMain.java:23) Caused by: java.lang.RuntimeException: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn(Ljava/lang/Class;Ljava/lang/invoke/MethodHandles$Lookup;)Ljava/lang/invoke/MethodHandles$Lookup; at org.gradle.internal.classloader.ClassLoaderUtils.(ClassLoaderUtils.java:46) ... 39 more Caused by: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn(Ljava/lang/Class;Ljava/lang/invoke/MethodHandles$Lookup;)Ljava/lang/invoke/MethodHandles$Lookup; at org.gradle.internal.classloader.ClassLoaderUtils.(ClassLoaderUtils.java:43) ... 39 more ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820389 Title: Gradle on OpenJDK 8:
[Bug 1820389] Re: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn()
On Ubuntu Cosmic, I installed gradle 4.4.1-5~18.10.1, also moved ~/.gradle out of the way and used update-java-alternatives to make OpenJDK 8 the default. I tested 3 Java and 2 Android projects and all build fine. There are some additional warnings about features that will be removed with Gradle 5 but that's fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820389 Title: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1820389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820389] Re: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn()
I just installed gradle 4.4.1-5~18.04 and moved ~/.gradle to ~/.gradle.bak (actually it's a dangerous suggestion to remove that directory, because it can contain user settings). Issue 1: The hard dependency to OpenJDK 11 is still there. I can't uninstall OpenJDK 11 without uninstalling gradle. So I switched to Java 8 by running sudo update-java-alternatives -s java-1.8.0-openjdk-amd64 Issue 2: Then I tried "gradle --stacktrace clean" on all of my projects. The exception is slightly different from before, but still kind of similar. The stacktrace doesn't seem complete, I'm not sure why this is the case. Please let me know how to acquire a full stacktrace if you need it. $ gradle --stacktrace clean Starting a Gradle Daemon (subsequent builds will be faster) FAILURE: Build failed with an exception. * What went wrong: Unable to start the daemon process. This problem might be caused by incorrect configuration of the daemon. For example, an unrecognized jvm option is used. Please refer to the user guide chapter on the daemon at https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html Please read the following process output to find out more: --- FAILURE: Build failed with an exception. * What went wrong: java.lang.ExceptionInInitializerError (no error message) * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org * Try: Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Exception is: org.gradle.api.GradleException: Unable to start the daemon process. This problem might be caused by incorrect configuration of the daemon. For example, an unrecognized jvm option is used. Please refer to the user guide chapter on the daemon at https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html Please read the following process output to find out more: --- FAILURE: Build failed with an exception. * What went wrong: java.lang.ExceptionInInitializerError (no error message) * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput(DaemonGreeter.java:34) at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(DefaultDaemonStarter.java:152) at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(DefaultDaemonStarter.java:135) at org.gradle.launcher.daemon.client.DefaultDaemonConnector.doStartDaemon(DefaultDaemonConnector.java:210) at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(DefaultDaemonConnector.java:204) at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:128) at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:138) at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:92) at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:51) at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:291) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:264) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:33) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:257) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:191) at org.gradle.launcher.Main.doAction(Main.java:33) at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60) at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37) at org.gradle.launcher.GradleMain.main(GradleMain.java:23) * Get more help at
[Bug 1820389] Re: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn()
Thanks a lot! I'm happy to test any new proposed packages and will report back the findings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820389 Title: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1820389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820513] Re: android-* packages not working well with OpenJDK 11
For completeness, I just tested the combination Gradle 3.4.1 and OpenJDK 11, all from current Bionic (updated): * I get the "WARNING: An illegal reflective access" spamming in the console. Reported separately: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1803855 * The build breaks with > Failed to notify project evaluation listener. > javax/xml/bind/annotation/XmlSchema The full exception is: org.gradle.api.ProjectConfigurationException: A problem occurred configuring project ':sample-integration-android'. at org.gradle.configuration.project.LifecycleProjectEvaluator.addConfigurationFailure(LifecycleProjectEvaluator.java:94) at org.gradle.configuration.project.LifecycleProjectEvaluator.notifyAfterEvaluate(LifecycleProjectEvaluator.java:89) at org.gradle.configuration.project.LifecycleProjectEvaluator.doConfigure(LifecycleProjectEvaluator.java:76) at org.gradle.configuration.project.LifecycleProjectEvaluator.access$000(LifecycleProjectEvaluator.java:33) at org.gradle.configuration.project.LifecycleProjectEvaluator$1.execute(LifecycleProjectEvaluator.java:53) at org.gradle.configuration.project.LifecycleProjectEvaluator$1.execute(LifecycleProjectEvaluator.java:50) at org.gradle.internal.Transformers$4.transform(Transformers.java:169) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:61) at org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:50) at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:599) at org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:125) at org.gradle.execution.TaskPathProjectEvaluator.configure(TaskPathProjectEvaluator.java:35) at org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:62) at org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:38) at org.gradle.initialization.DefaultGradleLauncher$ConfigureBuildAction.execute(DefaultGradleLauncher.java:233) at org.gradle.initialization.DefaultGradleLauncher$ConfigureBuildAction.execute(DefaultGradleLauncher.java:230) at org.gradle.internal.Transformers$4.transform(Transformers.java:169) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:106) at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:56) at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:160) at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:119) at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:102) at org.gradle.launcher.exec.GradleBuildController.run(GradleBuildController.java:71) at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28) at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35) at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:41) at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:26) at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:75) at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:49) at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:49) at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:31) at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:67) at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120) at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:47) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120) at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26) at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120) at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34) at
[Bug 1820513] Re: android-* packages not working well with OpenJDK 11
Does this answer your questions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820513 Title: android-* packages not working well with OpenJDK 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-tools-base/+bug/1820513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820513] Re: android-* packages not working well with OpenJDK 11
Actually I don't find an openjdk-10-jdk[-headless] package in Bionic, so I'm not sure if I ever tested OpenJDK 10. Probably not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820513 Title: android-* packages not working well with OpenJDK 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-tools-base/+bug/1820513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820513] Re: android-* packages not working well with OpenJDK 11
First, a clarification: I'm not yet using the android* packages for building my Android apps. I would very much like to, but they seemed incomplete and outdated whenever I checked. Rather, I'm using the Android SDK downloaded from Google and brought up to date by running "sdkmanager --update". But I do use the Ubuntu supplied Gradle 3.4.1, OpenJDK 8 packages as well as several standlone SDK tools like apksigner, apktool, adb and some more. I described everything in e.g. this README: https://github.com/bitcoin-wallet/bitcoin- wallet/blob/master/wallet/README.md#building-the-development-version So yes, the Android builds work with OpenJDK 8, Gradle 3.4.1 under Ubuntu 18.04 LTS. On OpenJDK 11, Gradle 4.4.1 under Ubuntu 18.04 LTS- proposed the described issues appear. All issues I reported are perfectly reproducable. I will test OpenJDK 10 in a moment, but from memory when I updated Bionic I had similar issues until I uninstalled OpenJDK 10 which fixed all problems I had. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820513 Title: android-* packages not working well with OpenJDK 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-tools-base/+bug/1820513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
@Matthias: The current Gradle 3.4.1 doesn't requre Java 10 or 11. It runs fine with Java 8, and the declared package dependencies also reflects that. For an LTS, I'm suggesting to keep the compatiblity to Java 8, especially since upstream Gradle works fine with Java 8 (even the current version). I did *not* suggest to revert the JDK default. Tiago has updated bug 1820389 with more insight about the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820389] Re: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn()
@Tiago But can this be fixed *before* Gradle 4.4.1 is released to bionic-updates? I expect this will break many setups, certainly not what you'd expect for a LTS release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820389 Title: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1820389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820389] Re: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn()
I just compared the Gradle 4.4.1 in bionic-proposed against a manually installed Gradle 4.4.1. The manual install doesn't have this bug! For reference: $ gradle --version Gradle 4.4.1 Build time: 2012-12-21 00:00:00 UTC Revision: none Groovy: 2.4.15 Ant: Apache Ant(TM) version 1.10.3 compiled on July 19 2018 JVM: 1.8.0_191 (Oracle Corporation 25.191-b12) OS: Linux 4.18.0-16-generic amd64 $ ~/dev/gradle-4.4.1/bin/gradle --version Gradle 4.4.1 Build time: 2017-12-20 15:45:23 UTC Revision: 10ed9dc355dc39f6307cc98fbd8cea314bdd381c Groovy: 2.4.12 Ant: Apache Ant(TM) version 1.9.9 compiled on February 2 2017 JVM: 1.8.0_191 (Oracle Corporation 25.191-b12) OS: Linux 4.18.0-16-generic amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820389 Title: Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1820389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820389] Re: java.lang.ExceptionInInitializerError (no error message)
The full exception is. java.lang.ExceptionInInitializerError at org.gradle.internal.classloader.FilteringClassLoader.(FilteringClassLoader.java:48) at org.gradle.initialization.DefaultClassLoaderRegistry.restrictTo(DefaultClassLoaderRegistry.java:40) at org.gradle.initialization.DefaultClassLoaderRegistry.restrictToGradleApi(DefaultClassLoaderRegistry.java:36) at org.gradle.initialization.DefaultClassLoaderRegistry.(DefaultClassLoaderRegistry.java:30) at org.gradle.internal.service.scopes.GlobalScopeServices.createClassLoaderRegistry(GlobalScopeServices.java:207) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73) at org.gradle.internal.service.ReflectionBasedServiceMethod.invoke(ReflectionBasedServiceMethod.java:35) at org.gradle.internal.service.DefaultServiceRegistry$FactoryMethodService.invokeMethod(DefaultServiceRegistry.java:795) at org.gradle.internal.service.DefaultServiceRegistry$FactoryService.create(DefaultServiceRegistry.java:748) at org.gradle.internal.service.DefaultServiceRegistry$ManagedObjectProvider.getInstance(DefaultServiceRegistry.java:574) at org.gradle.internal.service.DefaultServiceRegistry$SingletonService.get(DefaultServiceRegistry.java:623) at org.gradle.internal.service.DefaultServiceRegistry.applyConfigureMethod(DefaultServiceRegistry.java:199) at org.gradle.internal.service.DefaultServiceRegistry.findProviderMethods(DefaultServiceRegistry.java:180) at org.gradle.internal.service.DefaultServiceRegistry.addProvider(DefaultServiceRegistry.java:255) at org.gradle.internal.service.ServiceRegistryBuilder.build(ServiceRegistryBuilder.java:52) at org.gradle.launcher.cli.BuildActionsFactory.runBuildInProcess(BuildActionsFactory.java:129) at org.gradle.launcher.cli.BuildActionsFactory.createAction(BuildActionsFactory.java:90) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.createAction(CommandLineActionFactory.java:296) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:286) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:264) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:33) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:257) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:191) at org.gradle.launcher.Main.doAction(Main.java:33) at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60) at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37) at org.gradle.launcher.GradleMain.main(GradleMain.java:23) Caused by: java.lang.RuntimeException: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn(Ljava/lang/Class;Ljava/lang/invoke/MethodHandles$Lookup;)Ljava/lang/invoke/MethodHandles$Lookup; at org.gradle.internal.classloader.ClassLoaderUtils.(ClassLoaderUtils.java:46) ... 39 more Caused by: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn(Ljava/lang/Class;Ljava/lang/invoke/MethodHandles$Lookup;)Ljava/lang/invoke/MethodHandles$Lookup; at org.gradle.internal.classloader.ClassLoaderUtils.(ClassLoaderUtils.java:43) ... 39 more ** Summary changed: - java.lang.ExceptionInInitializerError (no error message) + Gradle on OpenJDK 8: java.lang.NoSuchMethodError: java.lang.invoke.MethodHandles.privateLookupIn() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820389 Title: Gradle on OpenJDK 8:
[Bug 1695919] Re: [SRU] Fix regression by updating to Gradle 3.5/4.0
** Changed in: gradle (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/1695919 Title: [SRU] Fix regression by updating to Gradle 3.5/4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1695919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803855] Re: Illegal reflective access operation
I investigated into upstream bugtrackers and apparently it's a Groovy issue: https://issues.apache.org/jira/browse/GROOVY-8339 I'm afraid I could not find out how to "starting java for gradle with --illegal-access=permit". Gradle itself doesn't take any jvm parameters. I think at the moment the easiest way to work around this error is allowing the Ubuntu version of Gradle to work with OpenJDK 8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803855 Title: Illegal reflective access operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1803855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
4) Android builds are entirely broken with OpenJDK 11. Apparently, you'd be forced to upgrade Android Gradle plugin to at least 3.1.0 to be compatible to OpenJDK 11. Ubuntu/Debian still has version 2.2.2 [1]! But even if you upgrade to 3.1.0 manually (bypassing apt), you'd break reproducable builds. Versions 3.1 to 3.4 are dependent on file system sort order. According to Google, that bug has recently been fixed in 3.5 [2] and will be backported to 3.4, but anyway these versions require newer Gradle versions that have yet to appear in Ubuntu/Debian. So we have a dependency deadlock that is currently unresolvable. [1] https://packages.ubuntu.com/search?keywords=libgradle-android-plugin-java=names [2] https://issuetracker.google.com/issues/110237303 ** Bug watch added: issuetracker.google.com/issues #110237303 https://issuetracker.google.com/issues/110237303 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695919] Re: [SRU] Fix regression by updating to Gradle 3.5/4.0
I think this bug can be closed now. See #6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695919 Title: [SRU] Fix regression by updating to Gradle 3.5/4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1695919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804848] [NEW] Constant subscription requests despite being denied
Public bug reported: I keep getting subscription requests by 2 unknown people, every couple of hours. I denied and banned these requests numerious times over the past months, but I keep getting them. Sometimes, there are 20 or more of these confirmation dialog windows open when I return to my computer. I'd argue the bad/deny buttons are not working. Also, the requests should not open on top of each other. If someone sends multiple requests without me reacting, only the last one is relevant to me. I'm using a Google Talk account which is registered to my own domain. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: telepathy-gabble 0.18.4-1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 23 15:40:21 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (945 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: telepathy-gabble UpgradeStatus: Upgraded to bionic on 2018-04-26 (210 days ago) ** Affects: telepathy-gabble (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: I keep getting subscription requests by 2 unknown people, every couple of hours. I denied and banned these requests numerious times over the past months, but I keep getting them. Sometimes, there are 20 or more of these confirmation dialog windows open when I return to my computer. I'd argue the bad/deny buttons are not working. Also, the requests should not open on top of each other. If someone sends multiple requests without me reacting, only the last one is relevant to me. + + I'm using a Google Talk account which is registered to my own domain. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: telepathy-gabble 0.18.4-1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 23 15:40:21 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (945 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: telepathy-gabble UpgradeStatus: Upgraded to bionic on 2018-04-26 (210 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804848 Title: Constant subscription requests despite being denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/1804848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797761] [NEW] Gradle 4.4.1 package missing alternative dep to Java8
Public bug reported: Please provide the (alternative) dependency to openjdk-8-jre-headless again like the Bionic package did. For a lot of developers Java8 still matters (Android developers for example), and forcing them to install the Java11 packages always leads to compatibility problems. ** Affects: gradle (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Gradle 4.4.1 package (missing) missing alternative dep to Java8 + Gradle 4.4.1 package missing alternative dep to Java8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797761 Title: Gradle 4.4.1 package missing alternative dep to Java8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1797761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786974] Re: Nginx is starting before IPv6 address is ready
By the way, I've got all IP addresses hardcoded in /etc/network/interfaces, so there should not be a delay between IPv4 and IPv6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786974 Title: Nginx is starting before IPv6 address is ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1786974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786974] Re: Nginx is starting before IPv6 address is ready
Yes, I'm binding to a specific IPv6 address. I tried your suggestion but it didn't help. # cat /etc/systemd/system/nginx.service.d/override.conf [Unit] After=network-online.target Wants=network-online.target After reboot, still: # service nginx status ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/nginx.service.d └─override.conf Active: failed (Result: exit-code) since Tue 2018-08-14 22:01:39 UTC; 7s ago Docs: man:nginx(8) Process: 638 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE) Aug 14 22:01:39 ultima systemd[1]: Starting A high performance web server and a reverse proxy server... Aug 14 22:01:39 ultima nginx[638]: nginx: [emerg] bind() to [xxx::3]:80 failed (99: Cannot assign requested address) Aug 14 22:01:39 ultima nginx[638]: nginx: configuration file /etc/nginx/nginx.conf test failed Aug 14 22:01:39 ultima systemd[1]: nginx.service: Control process exited, code=exited status=1 Aug 14 22:01:39 ultima systemd[1]: nginx.service: Failed with result 'exit-code'. Aug 14 22:01:39 ultima systemd[1]: Failed to start A high performance web server and a reverse proxy server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786974 Title: Nginx is starting before IPv6 address is ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1786974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786974] [NEW] Nginx is starting before IPv6 address is ready
Public bug reported: After upgrading from xenial to bionic, I have this regression with nginx. On autostart after bootup, it fails Aug 14 15:51:43 xxx nginx[590]: nginx: [emerg] bind() to [xxx]:80 failed (99: Cannot assign requested address) The address is an IPv6 address. I can then do 'service start nginx' manually and it succeeds. But suffice to say, I'd expect it to start up automatically e.g. after a server reboot. I'm not sure but I think nginx should be waiting until all IP addresses are available. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nginx (not installed) ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Aug 14 16:02:25 2018 SourcePackage: nginx UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago) ** Affects: nginx (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786974 Title: Nginx is starting before IPv6 address is ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1786974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786111] [NEW] fdroid signatures: 1 positional argument but 2 were given
Public bug reported: On 1.0.9 (bionic-proposed, possibly also cosmic), './fdroid signatures' or './fdroid signatures blabla.apk' yields: 'TypeError: extract() takes 1 positional argument but 2 were given.' This renders the command useless; it appears to be broken. This is/was the upstream issue: https://gitlab.com/fdroid/fdroidserver/issues/536 The issue is fixed via this commit: https://gitlab.com/fdroid/fdroidserver/commit/d76c5dc859e2bfd7de9cbecd81bb68738858ed42 ** Affects: fdroidserver (Ubuntu) Importance: Undecided Status: New ** Description changed: - On 1.0.9 (bionic-proposed, possibly also cosmic), ./fdroid signatures or ./fdroid signatures blabla.apk yields: - TypeError: extract() takes 1 positional argument but 2 were given. + On 1.0.9 (bionic-proposed, possibly also cosmic), './fdroid signatures' or './fdroid signatures blabla.apk' yields: + 'TypeError: extract() takes 1 positional argument but 2 were given.' This renders the command useless; it appears to be broken. This is/was the upstream issue: https://gitlab.com/fdroid/fdroidserver/issues/536 The issue is fixed via this commit: https://gitlab.com/fdroid/fdroidserver/commit/d76c5dc859e2bfd7de9cbecd81bb68738858ed42 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786111 Title: fdroid signatures: 1 positional argument but 2 were given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fdroidserver/+bug/1786111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762183] Re: ModuleNotFoundError: No module named 'distutils.util'
Thanks! Version 1.0.9-1~18.04.1 fixes this bug for me. However, there is another bug to "fdroid signatures" that needs fixing: https://gitlab.com/fdroid/fdroidserver/issues/536 (fixed upstream) ** Tags removed: 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/1762183 Title: ModuleNotFoundError: No module named 'distutils.util' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fdroidserver/+bug/1762183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763090] Re: Dependency alternative to openjdk-8-jdk missing
Thanks! Version 1.0.9-1~18.04.1 fixes this bug for me. However, there is another bug to "fdroid signatures" that needs fixing: https://gitlab.com/fdroid/fdroidserver/issues/536 ** Tags removed: 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/1763090 Title: Dependency alternative to openjdk-8-jdk missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fdroidserver/+bug/1763090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781238] Re: package virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
This is the make.log. ** Attachment added: "make.log" https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1781238/+attachment/5162831/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781238 Title: package virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1781238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781238] Re: package virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
It's the gcc that gets installed as a (transitive) dependency to virtualbox-dkms. Yes, I tried purging everything. Maybe secure boot is a problem? (But in this case I'd expect a meaningful error message.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781238 Title: package virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1781238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781238] Re: package virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
I tried that, as well as a "dpkg --configure -a". I even uninstalled and reinstalled all virtualbox and dkms related packages. It all led to the same hang. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781238 Title: package virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1781238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781238] [NEW] package virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
Public bug reported: System hangs when configuring virtualbox-dkms: Setting up virtualbox-dkms (5.2.10-dfsg-6ubuntu18.04.1) ... Removing old virtualbox-5.2.10 DKMS files... Uninstall Beginning Module: virtualbox Version: 5.2.10 Kernel: 4.15.0-24-generic (x86_64) - Status: This module version was INACTIVE for this kernel. depmod... DKMS: uninstall completed. -- Deleting module version: 5.2.10 completely from the DKMS tree. -- Done. Loading new virtualbox-5.2.10 DKMS files... Building for 4.15.0-24-generic Building initial module for 4.15.0-24-generic [at this point, it hangs forever] ProblemType: Package DistroRelease: Ubuntu 18.04 Package: virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 11 16:50:29 2018 ErrorMessage: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) InstallationDate: Installed on 2016-04-21 (810 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: virtualbox Title: package virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) UpgradeStatus: Upgraded to bionic on 2018-04-26 (75 days ago) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic ** Description changed: System hangs when configuring virtualbox-dkms: - Setting up virtualbox-dkms (5.2.10-dfsg-6ubuntu18.04.1) ... Removing old virtualbox-5.2.10 DKMS files... Uninstall Beginning Module: virtualbox Version: 5.2.10 Kernel: 4.15.0-24-generic (x86_64) - Status: This module version was INACTIVE for this kernel. depmod... DKMS: uninstall completed. -- Deleting module version: 5.2.10 completely from the DKMS tree. -- Done. Loading new virtualbox-5.2.10 DKMS files... Building for 4.15.0-24-generic Building initial module for 4.15.0-24-generic + [at this point, it hangs forever] + ProblemType: Package DistroRelease: Ubuntu 18.04 Package: virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 11 16:50:29 2018 ErrorMessage: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) InstallationDate: Installed on 2016-04-21 (810 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: - dpkg 1.19.0.5ubuntu2 - apt 1.6.2 + dpkg 1.19.0.5ubuntu2 + apt 1.6.2 SourcePackage: virtualbox Title: package virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) UpgradeStatus: Upgraded to bionic on 2018-04-26 (75 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781238 Title: package virtualbox-dkms 5.2.10-dfsg-6ubuntu18.04.1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1781238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762183] Re: ModuleNotFoundError: No module named 'distutils.util'
Just tested fdroidserver 1.0.8-3 from Cosmic on Bionic and it seems to work! No further dependency upgrades necessary as far as I can tell, all deps were satisfied by packages from Bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762183 Title: ModuleNotFoundError: No module named 'distutils.util' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fdroidserver/+bug/1762183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763090] Re: Dependency alternative to openjdk-8-jdk missing
Just tested fdroidserver 1.0.8-3 from Cosmic on Bionic and it seems to work! No further dependency upgrades necessary as far as I can tell, all deps were satisfied by packages from Bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763090 Title: Dependency alternative to openjdk-8-jdk missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fdroidserver/+bug/1763090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758196] Re: Sync fdroidserver 1.0.6-1 (universe) from Debian/testing (main)
What's the plan for Bionic? The currently packaged fdroidserver 1.0.2-1 appears to be broken (unusable). Will it simply be updated to 1.0.6-1? Or will the individual bugs be fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758196 Title: Sync fdroidserver 1.0.6-1 (universe) from Debian/testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fdroidserver/+bug/1758196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768610] Re: leftover conffile forces GNOME is software rendering
I'm trying the bionic version of the proposed nux-tools (4.0.8+18.04.20180613.5-0ubuntu1) and it works fine so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration
** Description changed: After upgrading from 16.04 to 18.04 on a very plain Intel Skylake graphics, hardware acceleration is gone. Glxinfo and System Information report 'llvmpipe' (software rasterizer) It is caused by the file /etc/X11/Xsession.d/50_check_unity_support which can be deleted and then this problem goes away. + + Apparently the problem is that nux-tools is not purged, leaving the + above file (also see #1768610). > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglvnd0 1.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:24:48 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (735 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libglvnd UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767468 Title: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768610] Re: leftover conffile forces GNOME is software rendering
*** This bug is a duplicate of bug 1767468 *** https://bugs.launchpad.net/bugs/1767468 I've set the duplicate the other way round because the original bug is already milestoned. ** This bug has been marked a duplicate of bug 1767468 Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration
** This bug is no longer a duplicate of bug 1768610 leftover conffile forces GNOME is software rendering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767468 Title: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773846] [NEW] Fullscreen title bars (!) waste so much space
Public bug reported: On Xenial, I had only one title bar containing the menu to the left and the systray to the right. On Bionic, I've got three title bars: 1. Stripped down menu to the left, systray to the right 2. Current path (redundant, since this is usually in the prompt) 3. Full menu I consider this a significant regression, as it now wastes precious screen space – about three lines of terminal text compared to the last LTS. Also, two menu bars for the same app, partially containing the same items appear to be useless to me. I hope the change can be undone in the current LTS cycle. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 28 21:29:14 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (766 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to bionic on 2018-04-26 (31 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773846 Title: Fullscreen title bars (!) waste so much space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1773846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration
I'm using Ubuntu, not Xubuntu. I never tried to manually execute the script. I simply removed the file and rebooted – problem gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767468 Title: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768620] Re: removal_blacklist.cfg updates
Note however, that *if* you uninstall Unity the system will disable hardware acceleration due to this bug: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468 Maybe the uninstallation of Unity should be delayed until the above bug is fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768620 Title: removal_blacklist.cfg updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1768620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767468] Re: Upgrade from 16.04 to 18.04 disables hardware acceleration on Intel Graphics
@Michele: Thanks, that's it. You're my personal hero of the week (-: ** Package changed: libglvnd (Ubuntu) => nux (Ubuntu) ** Summary changed: - Upgrade from 16.04 to 18.04 disables hardware acceleration on Intel Graphics + Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration ** Description changed: After upgrading from 16.04 to 18.04 on a very plain Intel Skylake graphics, hardware acceleration is gone. Glxinfo and System Information report 'llvmpipe' (software rasterizer) + + It is caused by the file + /etc/X11/Xsession.d/50_check_unity_support + which can be deleted and then this problem goes away. > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglvnd0 1.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:24:48 2018 Dependencies: - gcc-8-base 8-20180414-1ubuntu2 - libc6 2.27-3ubuntu1 - libgcc1 1:8-20180414-1ubuntu2 + gcc-8-base 8-20180414-1ubuntu2 + libc6 2.27-3ubuntu1 + libgcc1 1:8-20180414-1ubuntu2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (735 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libglvnd UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767468 Title: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767468] [NEW] Upgrade from 16.04 to 18.04 disables hardware acceleration on Intel Graphics
Public bug reported: After upgrading from 16.04 to 18.04 on a very plain Intel Skylake graphics, hardware acceleration is gone. Glxinfo and System Information report 'llvmpipe' (software rasterizer) > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglvnd0 1.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:24:48 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (735 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libglvnd UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767468 Title: Upgrade from 16.04 to 18.04 disables hardware acceleration on Intel Graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1767468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767415] [NEW] Emojis in email headers are shown MUCH too large
Public bug reported:
See attached picture.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:52.7.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: aschildbach 1621 F pulseaudio
BuildID: 20180416164209
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 27 17:32:00 2018
EcryptfsInUse: Yes
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Thunderbird (default) -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2016-04-21 (735 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
default via 192.168.1.1 dev wlp58s0 proto dhcp metric 600
169.254.0.0/16 dev wlp58s0 scope link metric 1000
192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.70 metric 600
MostRecentCrashID: bp-dcf7be60-3e00-439e-a39a-52f0d2160327
PrefSources:
prefs.js
/usr/share/xul-ext/enigmail/defaults/preferences/enigmail.js
/usr/share/xul-ext/enigmail/defaults/preferences/000system.js
Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
SubmittedCrashIDs:
bp-dcf7be60-3e00-439e-a39a-52f0d2160327
bp-47dc2ae5-396d-44a8-a7c0-ecb542160206
bp-c61df29c-72c2-4a55-ac73-a006c2150907
bp-a280a2f0-5957-4f04-b28d-0ebe92150820
UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)
dmi.bios.date: 01/16/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.name: 07TYC2
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.family: NULL
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
** Attachment added: ""is live now" message from YouTube, containing a
"recording" emoji in the subject"
https://bugs.launchpad.net/bugs/1767415/+attachment/5128591/+files/Screenshot%20from%202018-04-27%2017-35-35.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767415
Title:
Emojis in email headers are shown MUCH too large
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1767415/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763090] [NEW] Dependency alternative to openjdk-8-jdk missing
Public bug reported: The current dependency declarations force me to either install Java7 or Java9. Java8 (openjdk-8-jdk) is missing from the list of alternatives. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: fdroidserver (not installed) ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 18:47:57 2018 InstallationDate: Installed on 2013-01-11 (1916 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fdroidserver UpgradeStatus: Upgraded to bionic on 2018-03-07 (34 days ago) ** Affects: fdroidserver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763090 Title: Dependency alternative to openjdk-8-jdk missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fdroidserver/+bug/1763090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762183] [NEW] ModuleNotFoundError: No module named 'distutils.util'
Public bug reported: The package fdroidserver seems to be missing a dependency on Bionic: $ fdroid update Traceback (most recent call last): File "/usr/bin/fdroid", line 24, in import fdroidserver.common File "/usr/lib/python3/dist-packages/fdroidserver/common.py", line 52, in from distutils.util import strtobool ModuleNotFoundError: No module named 'distutils.util' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: fdroidserver 1.0.2-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 8 15:55:33 2018 InstallationDate: Installed on 2013-01-11 (1913 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fdroidserver UpgradeStatus: Upgraded to bionic on 2018-03-07 (31 days ago) ** Affects: fdroidserver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762183 Title: ModuleNotFoundError: No module named 'distutils.util' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fdroidserver/+bug/1762183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760359] Re: Regression: java.lang.NoSuchMethodError: java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer;
Thanks Steve for the clarification. I personally feel the (forced) move to Java9 comes too early, as I just have moved my Android projects to Java8 with quite some headache. But I guess I have to adapt. Here is the output of gradle under openjdk-9. The first 5 lines are always the same regardless of the parameters. $ gradle WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.gradle.internal.reflect.JavaMethod (file:/usr/share/gradle/lib/gradle-base-services-3.4.1.jar) to method java.lang.ClassLoader.getPackages() WARNING: Please consider reporting this to the maintainers of org.gradle.internal.reflect.JavaMethod 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 :help Welcome to Gradle 3.4.1. To run a build, run gradle ... To see a list of available tasks, run gradle tasks To see a list of command-line options, run gradle --help To see more detail about a task, run gradle help --task BUILD SUCCESSFUL Total time: 1.105 secs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760359 Title: Regression: java.lang.NoSuchMethodError: java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1760359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Gradle 3.4.1 broken on Java8!
The latest sync to the experimental Debian version 3.4.1 of Gradle is broken on Java8. See https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1760359 I'd rather return to 3.2.1 than living with a broken Gradle for another 2 years cycle (3.2.1 was broken on the last 3 releases too and just fixed recently so we have a working version in the LTS). Why was a broken version synched? Is software in Debian experimental even ready for sync? -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
[Bug 1760359] Re: Regression: java.lang.NoSuchMethodError: java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer;
I think the issue that Gradle has been updated to the Debian experimental version 3.4.1. Before, it was synched to "unstable" 3.2.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760359 Title: Regression: java.lang.NoSuchMethodError: java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1760359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760359] [NEW] Regression: java.lang.NoSuchMethodError: java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer;
Public bug reported: Since a couple of days, gradle doesn't work on Ubuntu 18.04 LTS any more on openjdk8. Installing openjdk9 kind of works around this problem, but it throws a couple of scary illegal access warnings instead. Just a days ago, everything worked fine so there must have been some bug introduced into a dependent package. $ gradle -S Starting a Gradle Daemon, 8 busy and 2 incompatible and 1 stopped Daemons could not be reused, use --status for details FAILURE: Build failed with an exception. * What went wrong: java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer; * Try: Run with --info or --debug option to get more log output. * Exception is: java.lang.NoSuchMethodError: java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer; at org.gradle.internal.remote.internal.inet.SocketConnection$SocketInputStream.(SocketConnection.java:154) at org.gradle.internal.remote.internal.inet.SocketConnection.(SocketConnection.java:59) at org.gradle.internal.remote.internal.inet.SocketConnectCompletion.create(SocketConnectCompletion.java:39) at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connectToDaemon(DefaultDaemonConnector.java:255) at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connectToDaemonWithId(DefaultDaemonConnector.java:241) at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(DefaultDaemonConnector.java:213) at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(DefaultDaemonConnector.java:130) at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:127) at org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:81) at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:51) at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:173) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:244) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:217) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:33) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:210) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:174) at org.gradle.launcher.Main.doAction(Main.java:33) at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60) at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37) at org.gradle.launcher.GradleMain.main(GradleMain.java:23) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gradle 3.4.1-4 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 00:04:40 2018 InstallationDate: Installed on 2013-01-11 (1905 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gradle UpgradeStatus: Upgraded to bionic on 2018-03-07 (24 days ago) ** Affects: gradle (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760359 Title: Regression: java.lang.NoSuchMethodError: java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1760359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755607] Re: java.lang.UnsupportedOperationException: Cannot nest operations in the same thread. Each nested operation must run in its own thread.
I worked around this problem by manually installing the junit package (3.8.2-9). Note that the gradle package transitively declares a dependency to junit4, but seems to strictly require JUnit 3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755607 Title: java.lang.UnsupportedOperationException: Cannot nest operations in the same thread. Each nested operation must run in its own thread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1755607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683761] Re: undefined symbol: tgetent
With todays update of libnative-platform-java/jni, this issue is fixed in 18.04. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683761 Title: undefined symbol: tgetent To manage notifications about this bug go to: https://bugs.launchpad.net/gradle/+bug/1683761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754896] Re: Sync libnative-platform-java 0.14-3 (universe) from Debian unstable (main)
I can confirm the fix arrived in 18.04 and works as intended. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754896 Title: Sync libnative-platform-java 0.14-3 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnative-platform-java/+bug/1754896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695919] Re: [SRU] Fix regression by updating to Gradle 3.5/4.0
With todays update of libnative-platform-java/jni, this issue is fixed in 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695919 Title: [SRU] Fix regression by updating to Gradle 3.5/4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1695919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755607] [NEW] java.lang.UnsupportedOperationException: Cannot nest operations in the same thread. Each nested operation must run in its own thread.
Public bug reported: In the test phase of several of my projects, I get an exception repeated many times (one for each test?). I tested manually installed gradles too and the issue is present on 3.2.1 too but seems fixed in 3.3. Cannot nest operations in the same thread. Each nested operation must run in its own thread. java.lang.UnsupportedOperationException: Cannot nest operations in the same thread. Each nested operation must run in its own thread. at org.gradle.internal.operations.DefaultBuildOperationWorkerRegistry.doStartOperation(DefaultBuildOperationWorkerRegistry.java:65) at org.gradle.internal.operations.DefaultBuildOperationWorkerRegistry.access$400(DefaultBuildOperationWorkerRegistry.java:30) at org.gradle.internal.operations.DefaultBuildOperationWorkerRegistry$DefaultOperation.operationStart(DefaultBuildOperationWorkerRegistry.java:163) at org.gradle.api.internal.tasks.testing.worker.ForkingTestClassProcessor.processTestClass(ForkingTestClassProcessor.java:68) at org.gradle.api.internal.tasks.testing.processors.RestartEveryNTestClassProcessor.processTestClass(RestartEveryNTestClassProcessor.java:47) at sun.reflect.GeneratedMethodAccessor160.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.dispatch.FailureHandlingDispatch.dispatch(FailureHandlingDispatch.java:29) at org.gradle.internal.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:132) at org.gradle.internal.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33) at org.gradle.internal.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:72) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54) at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gradle 3.2.1-5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 13 23:17:26 2018 InstallationDate: Installed on 2013-01-11 (1887 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gradle UpgradeStatus: Upgraded to bionic on 2018-03-07 (6 days ago) ** Affects: gradle (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755607 Title: java.lang.UnsupportedOperationException: Cannot nest operations in the same thread. Each nested operation must run in its own thread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1755607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683761] Re: undefined symbol: tgetent
FWIW, Debian import freeze for bionic was already on March 1. According to https://wiki.ubuntu.com/DebianImportFreeze "After this date, packages will only be imported from Debian in this way by explicit request from a developer." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683761 Title: undefined symbol: tgetent To manage notifications about this bug go to: https://bugs.launchpad.net/gradle/+bug/1683761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683761] Re: undefined symbol: tgetent
Laurent, thanks a lot for looking into this! Is there a particular action needed for starting the Debian sync? I'm asking because apparently there was no Debian sync for the last 1 year. At least that's the time the package has been broken in the various Ubuntu releases that happened since then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683761 Title: undefined symbol: tgetent To manage notifications about this bug go to: https://bugs.launchpad.net/gradle/+bug/1683761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683761] Re: undefined symbol: tgetent
Sadly, Gradle in the current beta of upcoming 18.04 LTS is broken in the same way, too. Packages: gradle 3.2.1-5 libnative-platform-jni 0.14-2 libnative-platform-java 0.14-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683761 Title: undefined symbol: tgetent To manage notifications about this bug go to: https://bugs.launchpad.net/gradle/+bug/1683761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695919] Re: [SRU] Fix regression by updating to Gradle 3.5/4.0
Sadly, Gradle in the current beta of upcoming 18.04 LTS is broken in the same way, too. Packages: gradle 3.2.1-5 libnative-platform-jni 0.14-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695919 Title: [SRU] Fix regression by updating to Gradle 3.5/4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1695919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721215] Re: Fails to start with Ubuntu 17.10: undefined symbol tgetent
*** This bug is a duplicate of bug 1683761 *** https://bugs.launchpad.net/bugs/1683761 ** This bug has been marked a duplicate of bug 1683761 undefined symbol: tgetent -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721215 Title: Fails to start with Ubuntu 17.10: undefined symbol tgetent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1721215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695919] Re: Fix regression by updating to Gradle 3.5/4.0
** Summary changed:
- Fix regression by updating to Gradle 3.5
+ Fix regression by updating to Gradle 3.5/4.0
** Description changed:
Gradle 3.2.1 on Ubuntu 17.04 is currently entirely broken ("java: symbol
lookup error: /usr/lib/jni/libnative-platform-curses.so: undefined
symbol: tgetent", see https://bugs.launchpad.net/bugs/1683761).
- One way to fix this would be to update Gradle to version 3.5, as it
- handles the issue too. See upstream:
+ One way to fix this would be to update Gradle to version 3.5 or 4.0, as
+ it handles the issue too. See upstream:
https://github.com/gradle/gradle/issues/1493
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695919
Title:
Fix regression by updating to Gradle 3.5/4.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1695919/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683761] Re: undefined symbol: tgetent
Thanks Mateusz, I added an "update request" issue to the Gradle package: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1695919 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683761 Title: undefined symbol: tgetent To manage notifications about this bug go to: https://bugs.launchpad.net/gradle/+bug/1683761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695919] [NEW] Fix regression by updating to Gradle 3.5
Public bug reported:
Gradle 3.2.1 on Ubuntu 17.04 is currently entirely broken ("java: symbol
lookup error: /usr/lib/jni/libnative-platform-curses.so: undefined
symbol: tgetent", see https://bugs.launchpad.net/bugs/1683761).
One way to fix this would be to update Gradle to version 3.5, as it
handles the issue too. See upstream:
https://github.com/gradle/gradle/issues/1493
** Affects: gradle (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/1695919
Title:
Fix regression by updating to Gradle 3.5
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1695919/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683761] Re: undefined symbol: tgetent
** Package changed: gradle (Ubuntu) => libnative-platform-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/1683761 Title: undefined symbol: tgetent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnative-platform-java/+bug/1683761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1238322] Re: gradle not working: symbol lookup error
I filed the regression in zesty as a new bug, since this one is old and was apparently fixed. See https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1683761 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1238322 Title: gradle not working: symbol lookup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1238322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683761] [NEW] undefined symbol: tgetent
Public bug reported: This is a regression in zesty: When starting gradle, I always get java: symbol lookup error: /usr/lib/jni/libnative-platform-curses.so: undefined symbol: tgetent Apparently, this is a recurring bug. It was also present in 13.10: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1238322 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gradle 3.2.1-1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Tue Apr 18 13:39:55 2017 InstallationDate: Installed on 2013-01-11 (1557 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all SourcePackage: gradle UpgradeStatus: Upgraded to zesty on 2017-04-08 (9 days ago) ** Affects: gradle (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683761 Title: undefined symbol: tgetent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1683761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649428] [NEW] Cannot open file from https location (URL)
*** This bug is a security vulnerability *** Public security bug reported: If I try, I get this GIMP message: Opening 'https://[...]' failed: Could not load 'https://[...]': Failed to open file 'https://[...]': open() failed: No such file or directory Most of the time, I can manually edit the URL to read http://[...] and I can open the document as expected. The bug is a security vulnerability because it forces users to use unsecure communication. $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt-cache policy gimp gimp: Installed: 2.8.16-1ubuntu1.1 Candidate: 2.8.16-1ubuntu1.1 Version table: *** 2.8.16-1ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 100 /var/lib/dpkg/status 2.8.16-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649428 Title: Cannot open file from https location (URL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1649428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557957] Re: Can't pull translations from Transifex
This bug has just been fixed in Debian: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=817038#26 Can someone sync the package to Xenial and Yakkety? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557957 Title: Can't pull translations from Transifex To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1557957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613894] [NEW] Update package to 0.12.2
Public bug reported: Source can be found on GitHub: https://github.com/transifex/transifex- client/releases/tag/0.12.2 The current version in the repos is not functional any more, see https://bugs.launchpad.net/ubuntu/+source/transifex-client/+bug/1557957 ** Affects: transifex-client (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/1613894 Title: Update package to 0.12.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transifex-client/+bug/1613894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
