This bug was fixed in the package update-manager - 1:20.04.6
---
update-manager (1:20.04.6) focal; urgency=medium
* deb2snap: Don't replace debs that were manually installed via
another package (LP: #1872958).
-- Marcus Tomlinson Wed, 15 Apr 2020
11:34:33 +0100
** Changed i
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package resource-agents - 1:4.5.0-2ubuntu2
---
resource-agents (1:4.5.0-2ubuntu2) focal; urgency=medium
* Remove bind9 autopkgtest not compatible with ubuntu (LP: #1872877)
-- Rafael David Tinoco Wed, 15 Apr 2020
03:32:33 +
** Changed in: resource-
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
This bug was fixed in the package linux - 5.4.0-24.28
---
linux (5.4.0-24.28) focal; urgency=medium
* focal/linux: 5.4.0-24.28 -proposed tracker (LP: #1871939)
* getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
Public bug reported:
Ubuntu 20.04, ubuntu session with wayland. After about one hour usage,
while firefox has been launched gnome-shell(?) crashed and falled back
to gdm login screen. This has happened several times.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+ On platforms with VMD support, block devices won't be scanned if VMD
+ controller is not previously probed.
+
+ [Fix]
+ Two commits from v5.5-rc1 to be backported.
+
+ [Test Case]
+ On platforms with VMD support, boot with prebuilt ke
nafallo@wendigo:~$ snap refresh
signal-desktop 1.33.1 from Snapcrafters refreshed
nafallo@wendigo:~$ fscrypt --version
fscrypt version v0.2.7
nafallo@wendigo:~$ fscrypt status .|grep policy
Options: padding:32 contents:AES_256_XTS filenames:AES_256_CTS policy_version:2
Confirmed working with ne
** Description changed:
+ [Impact]
- for SRU template:
- QEMU_MODULE_DIR="/tmp/" qemu-system-x86_64 -cdrom localhost::/foo
+ * An infrequent but annoying issue is qemus problem to not be able to
+hot-add capabilities IF since starting the instance qemu has been
+upgraded. This is due
Public bug reported:
bug was caught automatically. no further info can be provided.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-efi-amd64-signed 1.139+2.04-1ubuntu24
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.2
** Changed in: glib2.0 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872153
Title:
SIGSEGV in g_source_set_ready_time()
To manage notifications
The new glib has been uploaded to focal-proposed now which includes the
other fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869881
Title:
html file detected as unknown application/octet-stream
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867613
Title:
Ubuntu dock does not allow drag and
This is all green and aging for 15 days, I think it could be released or
am I missing something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868012
Title:
MRE for open-vm-tools to version 11.0.5
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868529
Title:
Stretched image previews on desktop
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873031
Title:
245.4-2ubuntu1 has broken dhcp based NTP updates
*** This bug is a duplicate of bug 1846785 ***
https://bugs.launchpad.net/bugs/1846785
Thanks, that's the same issue than bug #1846785, we should probably SRU
that fix to bionic
** Information type changed from Private to Public
** This bug has been marked a duplicate of bug 1846785
Crash
Closing because INVALID: fixed in Inkscape 1.0rc1.
Tested on Inkscape 1.0rc1 (09960d6, 2020-04-09), macOS 10.13.6
(17G12034).
Original report: cannot corroborate as I do not have the Adobe fonts
listed. Tested with other typeface families with more than four faces
(e.g, Archivo, Chivo, etc.), all
** Changed in: ubuntu-power-systems
Status: Fix Committed => 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/1855668
Title:
lockdown on power
To manage notifications about this bu
Hello Mark, or anyone else affected,
Accepted chrony into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/chrony/3.2-4ubuntu4.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
** Changed in: ubuntu-power-systems
Status: Fix Committed => 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/1866909
Title:
Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted
Public bug reported:
Currently , libva fails to load the 2.1.0 driver on Comet Lake graphics
on 18.04.
If we want to support this newer hardware , we need to backport version
2.3.0 of the driver.
See thread here https://discourse.ubuntu.com/t/18-04-intel-va-api-
support-for-intel-comet-lake/1513
@Daniel, not sure as this has been addressed yet, but I deleted
.cache/pulse and rebooted. The issue is still the same.
My setup is listed in bug 1873005 in case anybody's interested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Sorry, I've since reinstalled the server. The same pool is there, and
it's still focal, but the OS disk was reinstalled. I used it to test the
subiquity server installer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
There is no more zsys integration for this part of the stack.
Fix regression from disco due to useradd merge with debian.
** Affects: zsys (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs
btw, this bug should be fixed with the nouveau river in 5.7 (and
backports should follow soon for 5.4, 5.5 and 5.6)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803179
Title:
System does not relia
** Changed in: kunpeng920/upstream-kernel
Milestone: None => linux-v5.7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864950
Title:
[roce-0227]sync mainline kernel 5.6rc3 roce patchset into ub
Hi Bryce,
After long testing I have no problems with any key shortcuts (Ctrl+d and
Ctrl+z for example), I only see this issue when using Clipboard.
I tested:
Kubuntu host with Console (Qt terminal) and Ubuntu guest with GNOME terminal
(GTK) - problem
Kubuntu host with Console (Qt terminal) and K
** Changed in: kunpeng920/upstream-kernel
Milestone: None => linux-v5.7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867586
Title:
[hns3-0316]sync mainline kernel 5.6rc4 hns3 patchset into ub
As of today, after the update of linux kernel to 5.4.0-24.28, the list
of missing firmwares gets shorter.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-24-generic
W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module
amdgpu
W: Po
** Also affects: shadow (Ubuntu)
Importance: Undecided
Status: New
** Also affects: adduser (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
The system key is only rewritten if this is required. Normally it is not
modified.
The question now is: what has changed that made the system key differ?
One thing we did observe was /snap/core/$current changing without a
complete snapd re-start. Perhaps something was pinging snapd over the
API a
This bug was fixed in the package grub2 - 2.04-1ubuntu26
---
grub2 (2.04-1ubuntu26) focal; urgency=medium
[ Julian Andres Klode ]
* Move /boot/efi -> debconf migration into wrapper, so it runs everywhere
(LP: #1872077)
* Display disk name and size in the ESP selection dialog
This bug was fixed in the package apache2 - 2.4.41-4ubuntu3
---
apache2 (2.4.41-4ubuntu3) focal; urgency=medium
[ Timo Aaltonen ]
* d/p/buffer-http-request-bodies-for-tlsv13.diff, d/p/tlsv13-add-logno.diff:
mod_ssl: Add patches to fix TLS 1.3 client cert authentication for POS
This bug was fixed in the package fonts-noto-color-emoji - 0~20200408-1
---
fonts-noto-color-emoji (0~20200408-1) unstable; urgency=medium
* New upstream release (LP: #1871791)
- This update introduces support for Unicode 12.1 with new
gender and hand-holding options for m
Urm, it's going to be tricky to debug this as I can't figure out why
abd_verify is being shown but the object code isn't able to find this
symbol when I dig into it. Any idea if zfs-dkms was being used?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Bug is tracked here: https://bugs.openjdk.java.net/browse/JDK-8239385
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861883
Title:
JAAS Krb5LoginModule authenticates wrong principal
To manage notif
** Tags added: ubuntu-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815684
Title:
[SRU] Please accept zeroc-ice to supported releases
To manage notifications about this bug go to:
For some reason I unable to rebuild snapd following #29 instruction. All
goes fine, but in the end xdg-open wont work. I've checked
/var/log/syslog and it full of:
chromium_chromium.desktop[1674]: user-open error: Supplied URL scheme
"magnet" is not allowed
What is interesting, when I'm changing
Ack, good point thanks - I updated the patch to:
@@ -87,7 +87,9 @@
fi
# base-passwd defines gid 46 as group plugdev
if [ "$method" != efi ]; then
- options="$option
Fixed in 5.8+dfsg-1 which we merged (we are at 5.8+dfsg-2ubuntu2)
So at lest Focal should be fixed by now.
** Changed in: net-snmp (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: net-snmp (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: net-snmp (Ubun
Given how low prio/heat this issue had I'm gonna mark the SRU tasks won't fix.
Triaged+Low severity would be correct as well, but that would trigger wrong
expectations as I just see no one get to it.
That way it is clear and if this really is more painful/severe than I
thought people can speak up
Public bug reported:
After booting with nvidia drivers, if I change which monitor is the main
one first, then change the scaling from 100% to 200%, it works. But
doing this in the inverse direction, by first setting the scaling and
then changing the main monitor, it fails and the screens go black.
eoan-proposed verified using [Test Case] with output:
root@juju-773c15-lp1863014-eoan-10:/home/ubuntu# apt-cache policy vaultlocker
vaultlocker:
Installed: 1.0.6-0ubuntu0.19.10.1
Candidate: 1.0.6-0ubuntu0.19.10.1
Version table:
*** 1.0.6-0ubuntu0.19.10.1 500
500 http://archive.ubunt
This bug was fixed in the package ceilometer - 1:13.1.0-0ubuntu1~cloud0
---
ceilometer (1:13.1.0-0ubuntu1~cloud0) bionic-train; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
ceilometer (1:13.1.0-0ubuntu1) eoan; urgency=medium
.
* d/watch: Update tar
Okay, I had verified this from the day in it landed in -proposed. It is
working as expected (https://discourse.ubuntu.com/t/ubuntu-high-
availability-corosync-pacemaker-shared-disk-environments/). I'm marking
this as verification-done as it has stayed in -proposed for sometime now
and no bad feedba
This bug was fixed in the package horizon - 3:16.1.0-0ubuntu1~cloud0
---
horizon (3:16.1.0-0ubuntu1~cloud0) bionic-train; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
horizon (3:16.1.0-0ubuntu1) eoan; urgency=medium
.
* d/watch: Update tarball URL
This bug was fixed in the package neutron - 2:15.0.2-0ubuntu1~cloud0
---
neutron (2:15.0.2-0ubuntu1~cloud0) bionic-train; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
neutron (2:15.0.2-0ubuntu1) eoan; urgency=medium
.
* d/watch: Update tarball URL
The verification of the Stable Release Update for cinder has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
This bug was fixed in the package neutron-fwaas - 1:15.0.1-0ubuntu1~cloud0
---
neutron-fwaas (1:15.0.1-0ubuntu1~cloud0) bionic-train; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
neutron-fwaas (1:15.0.1-0ubuntu1) eoan; urgency=medium
.
* d/gbp.conf
Thanks a lot Uwe (for the report) and Scott (for pointing to the Debian
change already in git).
** Changed in: postfix (Ubuntu)
Status: New => Triaged
** Changed in: postfix (Ubuntu)
Importance: Undecided => Critical
** Tags added: server-next
** Tags added: rls-ff-incoming
--
You r
The verification of the Stable Release Update for ceilometer has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update s
The verification of the Stable Release Update for neutron-fwaas has
completed successfully and the package has now been released to
-updates. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-updat
eoan-proposed verified using [Test Case] with output:
root@juju-773c15-lp1863014-eoan-10:/home/ubuntu# apt-cache policy vaultlocker
vaultlocker:
Installed: 1.0.6-0ubuntu0.19.10.1
Candidate: 1.0.6-0ubuntu0.19.10.1
Version table:
*** 1.0.6-0ubuntu0.19.10.1 500
500 http://archive.ubunt
This bug was fixed in the package cinder - 2:15.1.0-0ubuntu1~cloud0
---
cinder (2:15.1.0-0ubuntu1~cloud0) bionic-train; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
cinder (2:15.1.0-0ubuntu1) eoan; urgency=medium
.
* New stable point release for Op
This bug was fixed in the package nova - 2:20.1.1-0ubuntu1~cloud0
---
nova (2:20.1.1-0ubuntu1~cloud0) bionic-train; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
nova (2:20.1.1-0ubuntu1) eoan; urgency=medium
.
* New stable point release for OpenStac
The verification of the Stable Release Update for neutron has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so w
The verification of the Stable Release Update for glance has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
Daniel, I filed that issue as
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873266
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869042
Title:
[nvidia] all monitor scaling fails due to ove
The verification of the Stable Release Update for nova has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we c
This bug was fixed in the package glance - 2:19.0.2-0ubuntu1~cloud0
---
glance (2:19.0.2-0ubuntu1~cloud0) bionic-train; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
glance (2:19.0.2-0ubuntu1) eoan; urgency=medium
.
* d/gbp.conf: Create stable/train
Okay, I had verified this from the day in it landed in -proposed. It is
working as expected (https://discourse.ubuntu.com/t/ubuntu-high-
availability-corosync-pacemaker-shared-disk-environments/). I'm marking
this as verification-done as it has stayed in -proposed for sometime now
and no bad feedba
The verification of the Stable Release Update for horizon has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so w
zfs-dkms was not being used, I had no need for it on this machine. I
only have zfs-dkms in my pi4, since the ubuntu kernel there doesn't
include the zfs module.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
The file you are missing belongs to postfix:
$ dpkg -S /usr/share/postfix/postinst.functions
postfix: /usr/share/postfix/postinst.functions
and postfix-ldap correctly depends on that:
Depends: libc6 (>= 2.11), libldap-2.4-2 (>= 2.4.7), postfix (= 3.4.5-1ubuntu1)
So something must have messed wit
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
This entry:
* swap storms kills interactive use (LP: #1861359)
- SAUCE: mm/page_alloc.c: disable memory reclaim watermark boosting by
default
closed this bug, but per latest comments, that isn't sufficient to
address the issue. Putting back to Confirmed.
** Changed in: linux (Ubuntu Focal
*** This bug is a duplicate of bug 1872077 ***
https://bugs.launchpad.net/bugs/1872077
Just for prosperity, the fix in bug 1872077 has fixed this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
I have 2 indicators running: insync and indicator-cpufreq.
I disabled the indicator extension and it still not completely smooth,
there are definitely dropped frames. It _may_ be a little better thou,
it is difficult to say (is there a way to profile the framerate of the
animation?).
--
You rece
Public bug reported:
Xfce 4.14 has the ability to do folder thumbnails and this should be enabled by
default in Xubuntu.
https://docs.xfce.org/xfce/thunar/tumbler#customized_thumbnailer_for_folders
** Affects: thunar (Ubuntu)
Importance: Undecided
Status: New
--
You received this
I see this behavior as well, but I am on Manjaro Gnome, not Ubuntu. So
is this a `gnome-calendar`-specific bug rather than one related to the
OS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872805
I agree and thanks for the suggestion.
I'll take a look at this for 20.10 and work with Bernd on this as usual.
Unless he beats me to it, since we are mostly busy finalizing 20.04 atm :-)
** Changed in: gpsd (Ubuntu)
Status: New => Triaged
** Changed in: gpsd (Ubuntu)
Importance: Unde
upload sponsored.
** Changed in: fonts-monoid (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871140
Title:
py3 fix needed
To manage notificatio
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (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/1852813
Title:
I can confirm the fix. Re-installed OS via same build iso, selected
proposed, and no warnings or unexpected windows popped up. Thanks for
all the hard work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872145
Title:
explicit key offered after all agent keys, auth can fail before
explicit key used
To manage notifications a
201 - 300 of 769 matches
Mail list logo
