"An upgrade is not possible at this time
Due to a bug in shim, LP: #1928434, upgrades are not currently safe for
your hardware.
Once that bug has been resolved you will be able to upgrade to the next
release of Ubuntu."
ubuntu 20:10, 07.06.2021, macbook air 6,2 middle 2013
--
You received
@Brian, thanks! Both tests pass now. Can you move livecd-rootfs for
bionic from proposed to updates please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915571
Title:
Cannot start bash session
Please disregard my last comment (#5). The problem I had was not this
one but related to using other connector agents in addition to
NetworkManager, in my case the openvpn3 command line.
(Automatic connection to the VPN is not there, but that is probably
safest.)
--
You received this bug
All autopkgtests for the newly accepted linux-meta-raspi2 (4.15.0.1087.84) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
langford/unknown (arm64)
r8168/8.045.08-2ubuntu1 (armhf)
snapd/unknown (arm64)
systemd/unknown (arm64)
*** This bug is a duplicate of bug 1869750 ***
https://bugs.launchpad.net/bugs/1869750
I am using Ubuntu 18.04.1 LTS.
It was working fine then PC feeling a little slow so I tried to restart the PC.
When it did not respond I forced power off but pressing the power button.
When I restarted the
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839912
On Mon, Jun 07, 2021 at 05:14:50AM -, Andrea Righi wrote:
> Public bug reported:
>
> The lxc autotest is failing with the following error(s) on the latest
> kernel linux-unstable 5.13:
>
> FAIL: lxc-tests: lxc-test-apparmor (1s)
> ---
> failed - opened /sys/kernel/uevent_helper
> ---
> PASS:
** Changed in: linux-oem-5.10 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930556
Title:
Focal update: v5.10.36 upstream stable release
To manage
** Changed in: linux-oem-5.10 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verified linux-oem-5.13 version 5.13.0-1003.3 from focal-proposed on
Intel ADL-S SDP.
** Also affects: linux-oem-5.13 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.13 (Ubuntu)
** Changed in: linux-oem-5.10 (Ubuntu Impish)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928750
Title:
Support mic-mute on Dell's platform
To manage notifications
** Changed in: linux-oem-5.10 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924207
Title:
[SRU][F:OEM-5.10/G/H] add realtek 8852 bluetooth support
To manage
** Changed in: linux-oem-5.13 (Ubuntu Focal)
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/1929027
Title:
drm/i915: Drop force_probe requirement for
** Changed in: linux-oem-5.10 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923571
Title:
Focal update: v5.10.28 upstream stable release
To manage
Just booted with "intel_idle.max_cstate=1" added to the kernel cmdline.
This seems to have fixed the problem. Network speeds are as expected,
ethtool shows no errors after some big network transfers. Tested the
kernel from #59 and the default 5.8.0-55-generic, both work when
Enable -proposed pocket and update. The "Rear Microphone - Built-in
Audio" is not present anymore.
The jack detection still works correctly for all 4 audio ports.
** Tags removed: verification-needed-focal verification-needed-hirsute
** Tags added: verification-done-focal
** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: nvidia-graphics-drivers-465 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
Importance: Undecided => High
** Changed in:
For hirsute, it is not really possible to test the packages as the only
available image for this HW os for focal. So, changing verification-
needed-hirsute to verification-done-hirsute.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-focal verification-done-hirsute
** No longer affects: focal (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926030
Title:
IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
To manage notifications about this
wow it's running like a fridge! cheers.
On 07/06/2021 03:23, Srinivas Pandruvada wrote:
> Please try this version
> https://github.com/intel/thermal_daemon/tree/ubuntu-bug-1930422
>
> checkout branch ubuntu-bug-1930422.
> Then repeat comments at #11
>
** Attachment added: "branch-output.txt"
I can confirm that the xenial, bionic, focal and hirsute packages are
working as expected.
To perform the verification I have used the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-dev
function generate_motd_message() {
message=$1
** Changed in: libayatana-appindicator (Ubuntu)
Status: New => Fix Committed
** Changed in: libayatana-appindicator (Ubuntu)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package isc-dhcp - 4.4.1-2.2ubuntu6.2
---
isc-dhcp (4.4.1-2.2ubuntu6.2) hirsute-security; urgency=medium
* Fix regression caused by rebuild with newer toolchain (LP: #1930917)
- debian/rules: build with -fno-strict-aliasing.
-- Marc Deslauriers
** Description changed:
[Impact]
Here's what has been brought to my attention by a UA customer:
* Release:
Xenial/16.04LTS
* Openssh version:
7.2p2-4ubuntu2.10
* Fuzzer tool used:
https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html
Hey Lucas! What package versions did you use? Were those from the ubuntu
archives? Since I see the instructions still mention using the PPA while
for testing we need to use the archive packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hey Lucas! What package versions did you use? Were those from the ubuntu
archives? Since I see the instructions still mention using the PPA while
for testing we need to use the archive packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hey Lucas! What package versions did you use? Were those from the ubuntu
archives? Since I see the instructions still mention using the PPA while
for testing we need to use the archive packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1
---
linux (5.11.0-18.19+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1
---
linux (5.11.0-18.19+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1
---
linux (5.11.0-18.19+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms
Public bug reported:
[Impact]
This is a regression in shim 15.4 that causes a crash in shim when chainbooting.
Also, the machine resets when you exit grub, rather than going back to
the EFI shell when launched from it.
[Test plan]
TODO for the chainboot, something similar to
The verification of the Stable Release Update for libreoffice has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1
---
linux (5.11.0-18.19+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1
---
linux (5.11.0-18.19+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.80-0ubuntu3
---
nvidia-graphics-drivers-460 (460.80-0ubuntu3) impish; urgency=medium
* debian/dkms_nvidia/patches/buildfix_kernel_5.13.patch,
debian/templates/dkms_nvidia.conf.in:
- Add support for Linux
The verification of the Stable Release Update for neutron has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package linux-gcp - 5.11.0-1008.8+21.10.1
---
linux-gcp (5.11.0-1008.8+21.10.1) impish; urgency=medium
* impish/linux-gcp: 5.11.0-1008.8+21.10.1 -proposed tracker (LP:
#1927565)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
Hello Corey, or anyone else affected,
Accepted neutron into victoria-proposed. The package will build now and
be available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Public bug reported:
On a clean install of Ubuntu 21.04:
Setting up bookworm (1.1.2+git20200823-1) ...
File
"/usr/share/com.github.babluboy.bookworm/scripts/mobi_lib/mobiml2xhtml.py",
line 249
print " - fixed by injecting empty start tag ", tname
^
SyntaxError: Missing
for reference - ceph-mgr uses cherrypy3 which is what pulls this into
main.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930111
Title:
[MIR] new dependencies of cherrypy3: jaraco.collections,
I could try to test the suggested change...
I understand that I would need to
- generate a key pair
- roll the public key into bios
- build the shim
- sign the shim with the private key
- set a boot entry with the new shim and updater as its parameter
- try to boot via this new boot entry
Is
I have now verified the packages on focal, and things work as expected:
ubuntu@zynqmp$ apt policy bootgen-xlnx
bootgen-xlnx:
Installed: 2020.2-0ubuntu4~20.04.1
Candidate: 2020.2-0ubuntu4~20.04.1
Version table:
*** 2020.2-0ubuntu4~20.04.1 500
500 http://ports.ubuntu.com/ubuntu-ports
** Description changed:
+ [Impact]
+ test_maps bpf selftests is failing on bionic.
That's because _test_and_fail_on_apple in DistUpgradeQuirks.py (see line
377) in the upgrader itself, is set to fail if vendor.startswith('Apple
Inc.') OR if vendor is unknown i.e. /sys/class/dmi/id/sys_vendor is null
(for example as it will be in WSL or just about any other system where
DMI isn't
I have the exact same issue after upgrading from xenial to bionic. I
have a script that does this:
mail --attach "$log_file" --subject "$subject" "$recipient" <
"$body_file"
It was working on xenial. After upgrading to bionic, I get a mail with
the attached file and an empty body.
--
You
** Attachment added: "apport.linux-image-5.8.0-55-generic.cime34c6.apport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931106/+attachment/5502930/+files/apport.linux-image-5.8.0-55-generic.cime34c6.apport
--
You received this bug notification because you are a member of Ubuntu
Hi, vcarceler.
Can you give complete dmesg from when this happens?
Thanks for you report.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931001
Title:
kernel: watchdog: BUG: soft lockup
** Tags added: hirsute
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931105
Title:
Sleep issue on ubuntu 21.04, CPU AMD 5700u
To manage notifications
--- Comment From tuli...@br.ibm.com 2021-06-07 10:25 EDT---
> I think this affects pmdk (rather the Linux kernel).
Correct.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931063
Title:
Hello Oleg, or anyone else affected,
Accepted python-oslo.messaging into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/python-oslo.messaging/5.35.0-0ubuntu4 in a few hours, and then in the
-proposed repository.
Please help us by testing
** Patch added:
"0001-selftests-bpf-add-ifdefs-in-tests-for-required-Clang.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931129/+attachment/5502940/+files/0001-selftests-bpf-add-ifdefs-in-tests-for-required-Clang.patch
--
You received this bug notification because you are a
This bug was fixed in the package xilinx-vcu-ctrl -
2020.2-0ubuntu4~20.04.1
---
xilinx-vcu-ctrl (2020.2-0ubuntu4~20.04.1) focal; urgency=medium
* SRU to focal (LP: #1929834)
-- Alfonso Sanchez-Beato (email Canonical) Fri, 28 May 2021 10:32:47 +0200
** Changed in:
This bug was fixed in the package linux-aws - 5.11.0-1008.8+21.10.1
---
linux-aws (5.11.0-1008.8+21.10.1) impish; urgency=medium
* impish/linux-aws: 5.11.0-1008.8+21.10.1 -proposed tracker (LP:
#1927561)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
--
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1
---
linux (5.11.0-18.19+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms
This bug was fixed in the package linux-gcp - 5.11.0-1008.8+21.10.1
---
linux-gcp (5.11.0-1008.8+21.10.1) impish; urgency=medium
* impish/linux-gcp: 5.11.0-1008.8+21.10.1 -proposed tracker (LP:
#1927565)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1
---
linux (5.11.0-18.19+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms
This bug was fixed in the package vitis-ai - 1.3.2-0ubuntu5~20.04.1
---
vitis-ai (1.3.2-0ubuntu5~20.04.1) focal; urgency=medium
* SRU to focal (LP: #1929834)
- Remove the unneeded patch for working-around duplicate definition of
SSDOutputInfo
vitis-ai
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1
---
linux (5.11.0-18.19+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.80-0ubuntu3
---
nvidia-graphics-drivers-460 (460.80-0ubuntu3) impish; urgency=medium
* debian/dkms_nvidia/patches/buildfix_kernel_5.13.patch,
debian/templates/dkms_nvidia.conf.in:
- Add support for Linux
Note: the issue can be solved with the fix above or with downgrading
ffmpeg; this could be indicated in the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931022
Title:
[SOLVED] Kino
Public bug reported:
I installed Kino 1.3.4 on Ubuntu 18.04 and 20.04. It runs, import, etc.
all normally. However, when a transition is created, the preview is
perfect but its stored version (the temporary .dv file) is a still video
of a single frame. The same worked on previous versions of
** Changed in: debian
Status: Unknown => 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/484039
Title:
[needs-packaging] frogr
To manage notifications about this bug go to:
Public bug reported:
Hi! I have problem with slow keyboard layout switching between Russian
and English layouts. In ubuntu 16.04-20.04 :)
gsettings get org.gnome.desktop.wm.keybindings switch-input-source
['XF86Keyboard']
But in gnome-tweak-tool I set as key for layout switching caps-lock. It is
This test F-hwe-5.8 / G-5.8 kernel fixes the issue:
https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/
The latest automatically updated kernel (5.8.0-55-generic) does not fix
the issue.
** Also affects: focal (Ubuntu)
Importance: Undecided
Status: New
** No longer
Please don't blame Python. This is by design, we should not upgrade
Apple systems just because their dmi is broken.
Seems we forgot to check that we are booting on UEFI in the first place,
though, but oh well, still a step up from nobody upgrading to most x86
'PC's upgrading.
--
You received
longer run. thanks for your help. without people like you we'd all be
using Windows!
On 07/06/2021 03:23, Srinivas Pandruvada wrote:
> Please try this version
> https://github.com/intel/thermal_daemon/tree/ubuntu-bug-1930422
>
> checkout branch ubuntu-bug-1930422.
> Then repeat comments at #11
>
I can confirm the update introduced a regression on Hirsute (and Impish
I presume). Focal and Groovy work properly. Unfortunately, it's not
related to the security patch, but it stems from the package being
rebuilt with the newer toolchain in Hirsute, so removing the patch won't
fix the issue.
I
** Attachment added: "apport.linux-image-5.10.0-1029-oem.d72pbt2u.apport"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1930754/+attachment/5502931/+files/apport.linux-image-5.10.0-1029-oem.d72pbt2u.apport
--
You received this bug notification because you are a member of
** Changed in: nova/rocky
Status: In Progress => Fix Committed
** Changed in: nova/queens
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/1892361
upload to bionic unapproved queue on 11th May -
https://launchpadlibrarian.net/538166201/ceph_12.2.13-0ubuntu0.18.04.8_source.changes
and still awaiting sru team approval.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For what it's worth, I commented out the `mystatedir statedir ifindex
interface` line, and changed the three `return` lines to be `exit 0` and
now I no longer get the angry red FAILED line during boot, `systemctl
status networking.service` looks okay, and my internet continues to
function just
** Changed in: openssh (Ubuntu Xenial)
Status: New => In Progress
** Description changed:
+ [Impact]
Here's what has been brought to my attention by a UA customer:
* Release:
Xenial/16.04LTS
* Openssh version:
7.2p2-4ubuntu2.10
* Fuzzer tool used:
** Also affects: glibc (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/1910312
Title:
semctl09 from ubuntu_ltp_syscalls failed on X / F-oem-5.6 /
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The behaviour you describe is by design. The mechanism provided by
systemd for a local administrator to override a systemd service is to
use /etc/systemd/system/ and/or /etc/systemd/system/*.service.d/. In
A little more information, after some investigation.
The issue affects xdm logins at the console, as well as remote ssh
logins. This also means that audio at the console fails to work, as ACLs
for the console's user are not added to the audio devices.
It seem that it can be solved by putting in
I'm currently treating this as an upstream kernel regression reported
here
https://lore.kernel.org/regressions/20210607142245.eikvyeacqwwu6dn3@wittgenstein
We should wait whether a simple revert will be acceptable or whether
anything else is needed from LXC specifically.
--
You received this
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc5/amd64/
Headers are not needed.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package fpga-manager-xlnx -
2020.2ubuntu2~20.04
---
fpga-manager-xlnx (2020.2ubuntu2~20.04) focal; urgency=medium
* SRU to focal (LP: #1929834)
-- Alfonso Sanchez-Beato (email Canonical) Fri, 28 May 2021 10:18:09 +0200
** Changed in: libegl-mali-xlnx
This bug was fixed in the package bootgen-xlnx - 2020.2-0ubuntu4~20.04.1
---
bootgen-xlnx (2020.2-0ubuntu4~20.04.1) focal; urgency=medium
* SRU to focal (LP: #1929834)
-- Alfonso Sanchez-Beato (email Canonical) Thu, 27 May 2021 16:58:44 +0200
** Changed in: bootgen-xlnx
This bug was fixed in the package libegl-mali-xlnx -
9p0.01rel0-0ubuntu5~20.04.1
---
libegl-mali-xlnx (9p0.01rel0-0ubuntu5~20.04.1) focal; urgency=medium
* SRU to focal (LP: #1929834)
-- Alfonso Sanchez-Beato (email Canonical) Fri, 28 May 2021 10:27:02 +0200
** Changed in:
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1
---
linux (5.11.0-18.19+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1
---
linux (5.11.0-18.19+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms
This bug was fixed in the package linux - 5.11.0-18.19+21.10.1
---
linux (5.11.0-18.19+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-18.19+21.10.1 -proposed tracker (LP: #1927560)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
- update dkms
This bug was fixed in the package xrt - 202020.2.8.726-0ubuntu7~20.04
---
xrt (202020.2.8.726-0ubuntu7~20.04) focal; urgency=medium
* SRU to focal (LP: #1929834)
- Fix patches description
xrt (202020.2.8.726-0ubuntu6~20.04) focal; urgency=medium
* Backport impish/hirsute
This bug was fixed in the package neutron - 2:16.3.2-0ubuntu2
---
neutron (2:16.3.2-0ubuntu2) focal; urgency=medium
* d/p/updates-for-python3.8.patch: Cherry-picked from
https://review.opendev.org/c/openstack/neutron/+/793417
to ensure py38 keepalived-state-change cleanup
The verification of the Stable Release Update for neutron has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This seems like it's caused by the removal of pidgin-libnotify from the
20.04 repository. Was this done by mistake? The pidgin package
recommends pidgin-libnotify in both 18.04 and 20.04, but for some reason
pidgin-libnotify doesn't exist in the 20.04 repository. I don't see any
explanation for
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (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/1902572
Title:
Again I don't see any throttling.
With the version from
https://github.com/intel/thermal_daemon
Can you do
#systemctl disable thermald
reboot
from a command line
#thermald --no-daemon --loglevel=debug --adaptive
Attach the output
Alternatively you can just add --loglevel=debug instead of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (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/1931024
Public bug reported:
yes
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.25-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
AptOrdering:
teams:amd64: Install
Public bug reported:
After update to firefox 89.0+build2-0ubuntu0.18.04.2, firefox appeared
completely broken. Restored history showed a bunch of blank or messed up
windows (NOT pages). My system is dual monitor with one monitor in
portrait mode.
As part of chasing a fix in a clean profile, got
[Expired for freeipmi (Ubuntu) because there has been no activity for 60
days.]
** Changed in: freeipmi (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931062
Title:
package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to
install/upgrade: installed
Public bug reported:
package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to
install/upgrade: installed mysql-server-8.0 package post-installation
script subprocess returned error exit status 1
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.25-0ubuntu0.20.04.1
Verified linux-oem-5.10 version 5.10.0-1030.31 from focal-proposed.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All autopkgtests for the newly accepted linux-base (4.5ubuntu1.6) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-oem-osp1/5.0.0-1071.77 (amd64)
Please visit the excuses page listed below and investigate the failures,
Hi Ted,
You will need to enable -proposed to get this kernel, as described in
https://wiki.ubuntu.com/Testing/EnableProposed from comment #27
You can turn this option off after the test.
It should be 5.8.0-56.63 from proposed on Groovy. (The 5.8 proposed kernel is
not ready for Focal yet, so
Public bug reported:
My ubuntu info:
Version: Ubuntu 21.04
Os type: 64-bit
GNOME version: 3.38.5
Windowing system: WayLand
i tried to update it Via terminal but i get this:
oneko is already the newest version (1.2.sakura.6-15).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
and
Thanks. The author is trying to send PATCH upstream and waiting for
approval. Will keep u updated if there's a new version of Hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929444
Title:
1 - 100 of 555 matches
Mail list logo