@rhpot1991,
would you please try 5.10-oem-1025 to check if the issue is gone?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342
Title:
Thunderbolt Dock Loses Monitors
To manage notificat
Public bug reported:
I literally dont know
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.44
ProcVersionSignature: Ubuntu 4.15.0-143.147-generic 4.15.18
Uname: Linux 4.15.0-143-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB
> @paelzer I updated the 'All open unclaimed MIR bugs' link on the MIR
> wiki page to show both NEW and CONFIRMED bugs, and I think we should be
> sure to include 'CONFIRMED' state bugs in our weekly review, not just
> 'NEW' state bugs.
Yeah I've got a notification about it.
I agree and thank you
** Description changed:
+ [Impact]
+
This is a new bug as of yesterday or the day before. If I select an area
on the desktop on my rightmost monitor, the origin point of the
selection is placed correctly at the cursor position, but other point is
offset by the width of the leftmost monito
** Description changed:
+ [Impact]
+
When dragging the mouse while selected on the Desktop, the selection box
is misaligned with the mouse pointer. The issue only started happening
on 21.04 after upgrading from 20.04 to the dev version of the OS.
+
+ [Test Plan]
+
+ Drag the mouse on the
Currently we don't have 0x9a15 pci device to verify, so will not SRU
patches.
** Description changed:
[Impact]
There is a new USB DWC3 ID which is required by TGL-H platform.
[Fix]
Cherry pick below series of patches from v5.12-rc2
https://patchwork.kernel.org/project/linux-acpi/cov
** Package changed: grub2 (Ubuntu) => grub2-signed (Ubuntu)
** Changed in: grub2-signed (Ubuntu)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928040
Title:
** Also affects: intel-microcode (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: intel-microcode (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: intel-microcode (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects:
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute)
Status: Triaged => 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/1923347
Title:
Selecting an area on the des
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute)
Status: Triaged => 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/1925095
Title:
GNOME Desktop selection is m
php8.0 removed from the blacklist
** Changed in: php8.0 (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/1927288
Title:
Please enable php8.0 in Ubuntu 21.10
Another customer hit this bug - waiting for release on uca ussuri
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907686
Title:
ovn: instance unable to retrieve metadata
To manage notifications abou
@Henrik,
Thanks.
here's another test kernel that disable d3cold_allowed for nvme with hmb.
https://drive.google.com/drive/folders/1gK67OYm6-jeKLj7GIQNZLCaHuaOwVTr1?usp=sharing
Please check the status of d3cold_allowed(it must be 0) before
s2idle&resume.
sudo cat /sys/bus/pci/devices/\:58\:00.0
1. The disks are not SCSI (Model: ST16000NM001G, see
https://www.seagate.com/gb/en/enterprise-storage/exos-drives/exos-x-drives/exos-x16/),
but I suspect they are identified as such due to the HBA?
2. The bug watcher has wrongly identified that LXD has releases a fix. Please
remove that.
2. It s
** Description changed:
[Impact]
GCE cloud instances started with images released prior to 2020-11-11
will fail to reboot when the newest grub2 2.02~beta2-36ubuntu3.32
packages are installed from -updates.
Upon reboot, the instance drops down to a grub prompt, and ceases to
boot
On Tue, May 11, 2021 at 1:35 AM Francisco Menchaca
<1921...@bugs.launchpad.net> wrote:
>
> Hi Christian,
>
> Thanks for your response.
>
> Do you mean disabling and enabling autostart to the old guests?
>
> In our dev lab worked straight away after installing the first PPA you
> bundled together, I
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922353
Title:
Overview sometimes fails to appear or disappear in 21.04
To manage notifications about this bug go to:
ht
Sorry for the lag on this issue.
Timo, while the added hooks are useful, they don't for the time being
obviate the need for the larger hammer of the sysctl, so we'd still like
to keep the referred to patch available, until we are forced to make a
choice if and when upstream drops the sysctl entire
Hey, Touchpad is still not working on any kernels.
I did the fresh 20.04 install and seems be touchpad issue again.
Tried kernels:5.4,5.6,5.8.14,5.9,5.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Can you apply for cve for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926673
Title:
Null pointer of fig2dev of gensvg.c in function svg_arrows
To manage notifications about this bug go to:
ht
The dmesg log looks OK to me at least the snd_hda_codec_realtek has the
chance to configure. The weird part is why still dummy output. Can you
give me the output of the commands "pactl list sinks`, `pactl list
sources`, `aplay -l` and `arecord -l`?
Could you also try to boot the kernel with the p
Hi, this looks like a legit issue with the linux-oem-5.6 da903x-
regulator module, which appears to have been addressed in f16861b12fa0
("regulator: rename da903x to da903x-regulator") (v5.8-rc6), which
points out that kmod gets confused before that commit.
You can verify this with e.g.:
$ modi
Public bug reported:
[Impact]
GCE cloud instances started with images released prior to 2020-11-11
will fail to reboot when the newest grub2 2.02~beta2-36ubuntu3.32
packages are installed from -updates.
Upon reboot, the instance drops down to a grub prompt, and ceases to
boot any further.
The o
Public bug reported:
The machine says Could not calculate the upgrade and then says "An
unresolvable problem occurred while calculating the upgrade.
If none of this applies, then please report this bug using the
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If
you want to inves
** Changed in: livecd-rootfs (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: livecd-rootfs (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: livecd-rootfs (Ubuntu Groovy)
Status: In Progress => Fix Committed
** Changed in: livecd-rootfs (
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
[Expired for xen (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xen (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892475
Title
[Expired for casper (Ubuntu) because there has been no activity for 60
days.]
** Changed in: casper (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877618
[Expired for xen (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xen (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892205
Title
[Expired for webkit2gtk (Ubuntu) because there has been no activity for
60 days.]
** Changed in: webkit2gtk (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
[Expired for dbus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dbus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917298
Tit
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/191729
[Expired for dbus (Ubuntu Focal) because there has been no activity for
60 days.]
** Changed in: dbus (Ubuntu Focal)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
[Expired for systemd (Ubuntu Focal) because there has been no activity
for 60 days.]
** Changed in: systemd (Ubuntu Focal)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918
[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Description changed:
[Impact]
Currently the ubuntu-base livecd-rootfs project is used to build tarballs
that are the base for building docker/OCI images.
The tarballs produced with the ubuntu-base project are modified externally
(see https://github.com/tianon/docker-brew-ubuntu-core/
Public bug reported:
Multiple memory leaks have been identified in libgdiplus library when
the test code provided ibgdiplus/tests/testgdi.c is compiled with ASAN
enabled. Memory leaks have been found in multiple components of the
library as below :
0x7fce7e31a3d0 in GdipCreatePen1 /home/targets/l
This was very helpful. On ubuntuforums, it was suggested that I check
the "Optimus" setting under the "Video" menu in the BIOS. That solved
half the problem. Then following your suggestion and changing the
Multimedia engine in SMPlayer to /usr/bin/mpv solved the other half.
Nvidia currently works
I think the desktop should use HWE kernel (5.8) by now. Can you please
give it a try?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875459
Title:
System hangs when loading google maps on chrome wit
Public bug reported:
I "backported" s3ql (built .debs for python3-pyfuse3_3.2.0-2build1,
python3-trio_0.18.0-1, and s3ql_3.7.0+dfsg-2build1-local1 to use in
Ubuntu 20.04), and encountered a fairly quick crash (like under a
minute) when I started writing data to the s3ql filesystem. The log
ends w
** Tags added: 5.6 oem oem-5.6 sru-20210412
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879339
Title:
test_310_config_security_perf_events_restrict /
test_400_refcount_config in ubuntu_qrt_kern
** Tags added: 5.6 oem oem-5.6 sru-20210412
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879341
Title:
test_350_retpolined_modules from ubuntu_qrt_kernel_security failed on
F-OEM-5.6
To manage
** Tags added: oem-5.6 sru-20210412
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887487
Title:
range bound deduction test in test_verifier from ubuntu_bpf failed on
F-oem-5.6
To manage notifica
** Tags added: oem oem-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/1866323
Title:
btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
To manage notifications about this bug go t
** Tags added: oem-5.6 sru-20210412
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880631
Title:
l2tp.sh from net in ubuntu_kernel_selftests failed with test not
executable
To manage notification
** Tags added: oem-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/1880645
Title:
icmp_redirect.sh in net from ubuntu_kernel_selftests failed on
F-OEM-5.6 / G / H
To manage notifications about
** Tags added: oem oem-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/1892213
Title:
psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
focal/linux
To manage notifications about
** Tags added: oem oem-5.6 sru-20210412
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856010
Title:
xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in
ubuntu_kernel_selftests will fail if run
** Tags added: oem oem-5.6 sru-20210412
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879345
Title:
probe event parser error log check in ftrace from
ubuntu_kernel_selftests failed on F-OEM-5.6
Public bug reported:
The suspend fail, it wakes up after 4 or 5 seconds from suspending. This
issue is very similar to Elementary OS's problem which I discovered. The
only difference is that in Ubuntu, it can suspend for the first time
after the restart or turned on, after waking up, it wont be ab
This bug probably should not have been recycled for gnome-shell users.
This bug is from 2014 and relates to Compiz/Unity. If you are using
gnome-shell then please subscribe to bug 1927948 instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1419
https://gitlab.gnome.org/GNOME/mutter/-/issues/1419
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1419
Importance: Unknown
Status: Unknown
** Bug watch added: gitlab.gnome.org/GNOME/gnome
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
apport-cli YOURFILE.crash
Then tell
Thanks for that. Your system log shows it was Xorg crashing in the
radeon driver:
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: radeon: The kernel rejected
CS, see dmesg for more information (-16).
mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE)
mai 10 13:43:01 poe org.gnome.Shell.de
Thanks. I can see lots of crashes and errors from your gnome-shell
extensions. Please remove them by:
cd /home/grizzlysmit/.local/share/gnome-shell/
rm -rf extensions
then log out and in again. And if you experience any problems again
after that then just follow the instructions in comment #5
** No longer affects: sddm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915870
Title:
gnome-shell/gnome-session-check-accelerated-gl-helper crashed with
SIGSEGV in cso_destroy_context()
*** This bug is a duplicate of bug 1922353 ***
https://bugs.launchpad.net/bugs/1922353
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1922353, so it is being marked as such. Please look
Verified for hirsute.
** Description changed:
efi: Failed to lookup EFI memory descriptor
is an error message generated by the kernel.
Please pull in https://github.com/rhboot/shim/pull/361/files to fix it.
[Test case]
- Verify that 'sudo journalctl -b -1 | grep 'efi: Failed to l
Thanks for calling our attention to this. It affects both ubuntu-docs
and gnome-user-docs, so I submitted an upstream issue as well.
** Also affects: gnome-user-docs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-user-docs (Ubuntu)
Importance: Undecided => Medium
**
Fresh installed HH final ISO alongside Windows 10 secure boot enabled.
Proposed must be enabled in Hirsute (9 packages):
sudo apt install shim-signed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
shim-sig
** Description changed:
efi: Failed to lookup EFI memory descriptor
is an error message generated by the kernel.
Please pull in https://github.com/rhboot/shim/pull/361/files to fix it.
+
+ [Test case]
+ Verify that 'sudo journalctl -b -1 | grep 'efi: Failed to lookup' returns no
resu
On all target releases, I've reproduced the bug with the old logwatch
version, and verified the issue is resolved with the new logwatch
version.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy verification-needed-xenial
** Tags
Hi Christian,
Thanks for your response.
Do you mean disabling and enabling autostart to the old guests?
In our dev lab worked straight away after installing the first PPA you
bundled together, I didn't have to disable and enable autostart.
Kind Regards,
FRANCISCO MENCHACASALES ENGINEER | https
Public bug reported:
Example failure:
http://10.246.72.9/5.4.0-1045.49-oracle/focal-linux-oracle-oracle-
amd64-5.4.0-VM.Standard2.1-ubuntu_qrt_kernel_security/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security
.test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel-
secur
Dude... I wish you posted that before I started all of these on my side !!
See ?? We both posted nearly at the same time !
I tried to downgrade first but I don't know why it started to throw me
huge dependency problems (Qt5 and tons of unknown packages)... I gave
up...
Feeling as surprised as you
Thank you Po-Hsu. The 5.8.0-52.59 kernel appears to be working fine on
Focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926030
Title:
IR Remote Keys Repeat Many Times Starting with Kernel 5.8.
This will happen if you try it. Never add the ubuntustudio-* packages
directly. If you wish to use the Ubuntu Studio packages on a regular
Ubuntu install, install "ubuntustudio-installer" first as this is the
supported method. The method you tried is unsupported, so I'm closing
this bug.
** Change
I tested the pre-built binary of the latest version of runc (by just replacing
/usr/sbin/runc) and I was able to go to 400 pods on a single test node.
This new version was released today.
```
root@node0:~# runc -v
runc version 1.0.0-rc94
spec: 1.0.2-dev
go: go1.14.15
libseccomp: 2.5.1
```
https:/
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/402538
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try /grub/g
** Changed in: pi-bluetooth (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/1921915
Title:
Bluetooth controller not detected on CM4
To manag
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925971
Title:
SRU bluetooth f
** 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/1928019
Title:
package plymouth-theme-ubuntustudio 20.04.1 failed to install/upgrade:
installed plymouth-theme-u
Public bug reported:
Unfortunately, I made the mistake of trying to add ubuntustudio packages
to a base install of Ubuntu 20.04 and there has been a problem.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: plymouth-theme-ubuntustudio 20.04.1
ProcVersionSignature: Ubuntu 5.6.0-1055.59-oe
The verification passed for Groovy.
*** On Pi 400 **
ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
Installed: 0.1.15ubuntu1
Candidate: 0.1.15ubuntu1.1~20.10.1
Version table:
0.1.15ubuntu1.1~20.10.1 500
500 http://ports.ubuntu.com
The verification passed for Groovy.
*** On Pi 400 **
ubuntu@ubuntu:~$ apt-cache policy pi-bluetooth linux-firmware-raspi2
pi-bluetooth:
Installed: 0.1.15ubuntu1
Candidate: 0.1.15ubuntu1.1~20.10.1
Version table:
0.1.15ubuntu1.1~20.10.1 500
500 http://ports.ubuntu.com
So the initramfs-tools with the fix has migrated now, the next impish
daily should have it (serial 20210511 or later). Would you be able to
test to see if that helps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
I uploaded it to this Gist:
https://gist.githubusercontent.com/atrepca/dede1e2f4b894a444d6ac0f0abeaf5dd/raw/e5877b08940773e01e5ef93596f31ede49cb69e0
/ubuntu-advantage.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Trying again...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927029
Title:
ua attach command fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-a
I can't seem to be able to attach, ok to post the full log here? It's
1342 lines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927029
Title:
ua attach command fails
To manage notifications about
Remy (remyzerems) solution seems better if the PPA author can be trusted.
Part of the security in Linux, comes from not installing random stuff on the
Internet.
PPAs are individual repos that anyone can set up without Ubuntu responsability
or oversight.
I know nothing about the PPA author, may
All autopkgtests for the newly accepted python-apt (1.6.5ubuntu0.6) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
botch/unknown (arm64)
update-manager/unknown (arm64)
apt/1.6.13 (amd64)
ubiquity/unknown (arm64)
isenkram/unknown (
This is a false-positive for the SRU due to the binary copy of shim 1.47
from impish to hirsute-proposed. It has already been fixed in hirsute
release, there is no change here and no need for an SRU verification.
** Changed in: shim-signed (Ubuntu Hirsute)
Status: Fix Committed => Fix Rele
This was not necessary to include in the SRU of shim-signed to hirsute
(and in fact I specifically omitted the change from the upload I did to
hirsute-proposed, which got clobbered). But it also doesn't have any
impact for hirsute since -Zxz is already the default, so given that the
package has su
*within a release. I've also updated the information above. Let me
know what further info is needed.
** Changed in: grub2-signed (Ubuntu)
Status: Incomplete => New
** Changed in: update-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you
This is package upgrades with a release.
** Description changed:
- I think this might be an issue with softare-updater, honestly. But it won't
upgrade grub, giving this as an explanation:
+ EDIT:I'm using the software update tool to do a regular package upgrade
+ on Xubuntu 20.04.
+
+ I think
This issue was fixed in the openstack/neutron 16.3.2 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883089
Title:
[L3] floating IP failed to bind due to no agent gateway port(fip-ns)
To ma
Yes, when I just plug in my hub (also without any connections), my wifi
connection get lost.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925768
Title:
Losing Wifi connection when USB-C Hub was pl
> Isn't 2.04 > than 2.02?
Yes, it is:
$ dpkg --compare-versions 2.04-1ubuntu26.11 gt 2.02~beta2-36ubuntu3.31; echo $?
0
$
So I don't see what the problem here is based on the information
available.
Did this error happen as part of a release upgrade between two releases,
or package upgrades with
Public bug reported:
https://help.ubuntu.com/stable/ubuntu-help/video-dvd-restricted.html
https://help.ubuntu.com/stable/ubuntu-help/video-dvd.html.en
These two help articles both recommend the Fluendo DVD Player for
legally playing DVDs. However, Fluendo announced that they would be
discontinuin
This issue was fixed in the openstack/neutron 17.1.2 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884723
Title:
[OVS] multicast between VM instances on different compute nodes is
broken
** Description changed:
[IMPACT]
There is a known issue in pam_tally2 which may cause an account to be lock
down even with correct password, in a busy node environment where simultaneous
logins takes place (https://github.com/linux-pam/linux-pam/issues/71).
- There are already two custome
Thanks for the heads up. I upgraded Chromium to
90.0.4430.72-0ubuntu0.16.04.1 and it's working fine here as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863608
Title:
version 80 does not sta
The verification passed for focal.
* On Pi 400 **
ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2
bluez:
Installed: 5.53-0ubuntu3
Candidate: 5.53-0ubuntu3.1
Version table:
5.53-0ubuntu3.1 500
500 http://ports.ubuntu.com/ubuntu-ports foc
Hi guys !
I managed to get it working by upgrading the mesa driver to the latest version
using the Kisak-mesa PPA as described there :
https://itsfoss.com/install-mesa-ubuntu/
I followed the paragraph : "Install the latest stable version of Mesa driver in
Ubuntu [Latest point release]"
Note tha
I have another workaround, which actually makes sddm-greeter work again.
I had my doubts so I went to confirm my assumptions. You can skip my
detective work and rambling by going under the asterisk line.
And it is true that both programs which JohnDoe_71Rus (johndoe99)
mentions have similar issues
** Tags added: verification-done-focal verification-needed verification-
needed-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925971
Title:
SRU bluetooth fixes and CVEs to focal and groovy
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pam (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/1927796
Title:
[SRU]p
Tj, from irc #ubuntu, says "I can see the problem. it's the onegrub
builds for i386 going back to 16.04 ... the updater is picking the FIRST
in the list which is for Version: 1.167+2.04-1ubuntu44"
I think this is in reference to a change in grub2: grub2-unsigned
(2.04-1ubuntu44) hirsute; urgency=m
Still causing SIGSEV with 3.1.1-1ubuntu1.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926057
Title:
nextcloud crashes with SIGSEV
To manage notifications about this bug go to:
https://bugs.la
1 - 100 of 504 matches
Mail list logo
