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
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
```
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
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
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-*
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
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
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:
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.
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
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
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
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
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
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
#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:
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:
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,
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.
@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:
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
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
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.
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:
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
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:
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:
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".
@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).
@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.
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
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
** 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
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
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
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
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
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.
**
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
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
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
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
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
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
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.
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
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.
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)
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
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
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.
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
** 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
*** 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
** 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,
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
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:
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
@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
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
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
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
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
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
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:
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
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
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
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
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
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
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
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.
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.
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
*** 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.
** 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:
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:
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
** 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
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.
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:
*** 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
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.
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)
Here is the upstream bug: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=817038
** Bug watch added: Debian Bug tracker #817038
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817038
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Trying to upgrade from 15.10 (x86 64bit) and I've got the issue too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570947
Title:
Trusty to Xenial upgrade KeyError: 'SUDO_UID'
To manage
Thanks for the confirmation! Is there a process to fix this in Ubuntu
too? It is appropriate to set this issue to "confirmed" status?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511945
Title:
** Changed in: meld (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511945
Title:
Failed "Merge All", TypeError: merge_all_non_conflicting_changes()
takes
Public bug reported:
Since updating to Ubuntu Wily when resolving a git merge conflict with
meld I get this message in the console when using "Merge All" from the
menu.
TypeError: merge_all_non_conflicting_changes() takes exactly 1 argument
(2 given)
The "Merge All" doesn't do anything. I'd
Public bug reported:
Currently the Gradle package depends on default-jre-headless (openjdk-7
-jre-headless) but I think it would also run on openjdk-8-jre-headless.
Could you allow this as an alternative?
** Affects: gradle (Ubuntu)
Importance: Undecided
Status: New
** Description
If you look at the Scala package I think the dependency could be done
like that: http://packages.ubuntu.com/wily/scala
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511931
Title:
OpenJDK 8 support
Gradle 2.5 is now in Ubuntu Wily so I think this wishlist item can be
closed. Thanks to the people who made this possible!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009508
Title:
Upgrade to
Public bug reported:
Currently the Groovy package depends on default-jre-headless (openjdk-7
-jre-headless) but I think it would also run on openjdk-8-jre-headless
or (even better) on the generic java7-runtime-headless (which allows
future Java 7 compatible runtimes) . Could you allow this as an
Public bug reported:
Currently the Groovy package depends on default-jre-headless (openjdk-7
-jre-headless) but I think it would also run on openjdk-8-jre-headless
or (even better) on the generic java7-runtime-headless (which allows
future Java 7 compatible runtimes) . Could you allow this as an
Does anyone have instructions for how to configure this by hand on a
desktop Ubuntu vivid or wily installation?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/995332
Title:
Please
Does anyone have instructions for how to configure this by hand on a
desktop Ubuntu vivid or wily installation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995332
Title:
Please enhance
I am and was using all kinds of versions of keytool. I never had any
problem.
I'd say as long as the reason for the lock-to-java8 is unknown, remove
it. It's causing a headache with my setup.
If in future we find out about an issue with keytool, the right was to
deal with that is backporting the
Thanks, I now posted to the right mailing list:
http://lists.freedesktop.org/archives/intel-gfx/2015-October/077193.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296224
Title:
Horrible noise
Sorry, too many instructions and too many dead ends in those. I just
appended the info that I missed out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296224
Title:
Horrible noise via DisplayPort
1 - 100 of 982 matches
Mail list logo
