** Changed in: ubuntu-kernel-tests
Status: In Progress => 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/1880645
Title:
icmp_redirect.sh in net from ubuntu_kernel_selftests
attached journal.log file, done after trying to boot with 5.13.13
(kernel panic) and rebooting with functional kernel (5.13.8)
** Attachment added: "journal.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+attachment/5521049/+files/journal.log
--
You received this bug
Reuploading the script
** Attachment removed: "nvidia_supported"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5521045/+files/nvidia_supported
** Attachment added: "nvidia_supported"
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1941773/+attachment/5521047/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941773
apport information
** Description changed:
I do not know how to find information to help debug.
The laptop is lenovo E15 with latest BIOS 1.13
kubuntu 21.04
laptop boots correctly with 5.13.8 and trackpad works.
with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic.
---
** Tags added: originate-from-1941823 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940262
Title:
The modalias in 470 is not compatible to 460
To manage notifications about this bug go
I would like to propose fix to nvidia_supported script that parses
README.txt.
On the line with RTX A5000, there are 2 spaces after the PCI IDs.
Current nvidia_supported script assumes there are at least 3 spaces
before VDPAU features column, which is not the case in this line.
My proposal of
** Tags added: 4.15 5.10 5.11 5.13 5.4 bionic focal hirsute
** Tags added: impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941829
Title:
ubunut_kernel_selftests: memory-hotplug: avoid
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Bionic)
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1941829
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
[Impact]
The memory-hotplug test has been intermittently timing out (or trashing the test
VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now.
While the offline memory test obey ratio limit, the same test with
error injection does not and tries to
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (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/1933686
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Assignee: (unassigned) => zeeshan saleem (zeeshan-saleem)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853277
Title:
Lenovo ThinkBook 14-IML
Could you run `apport-collect 1941773` again since lots of file missing.
And can you paste the kernel panic here? Doing `journalctl -k -b -1 >
journal.log` after reboot and attach the journal.log here would be
helpful. Thanks
--
You received this bug notification because you are a member of
@Michael and Robert,
All patches were sent to the ubuntu kernel maillist to review, and
please wait for the formal 5.11.0-generic kernel of the next cycle.
@Robert,
All patches were backported from sofproject or upstream kernel, and
maybe the kconfig is not same when building the sof kernel and
The dmesg of 5.13 kept showing the error as follow
août 26 11:18:46 syncom kernel: Workqueue: kacpid acpi_os_execute_deferred
août 26 11:18:46 syncom kernel: RIP: 0010:acpi_ds_exec_end_op+0x182/0x779
But it didn't show in kernel 5.11. That's pretty confusing to me. I may
need more ACPI debug
The issue is still reproduced:
# dpkg --list | grep 1.1.1f
ii libssl-dev:arm64 1.1.1f-1ubuntu2.9
arm64Secure Sockets Layer
toolkit - development files
ii libssl1.1:arm64
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1940377
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => AaronMa (mapengyu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940377
Title:
The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1]
@Gabriel
Can you also check linux-image-generic-hwe-20.04 on focal ? it's 5.11 as
well.
linux-image-generic-hwe-20.04
5.11.0.27.29~20.04.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940377
** Also affects: linux (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/1940377
Title:
The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zim (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/1250391
Title:
Open
Public bug reported:
Ubuntu version: 18.04
ncurses version:6.1
Hello,I found some potential bugs in package ncurses-6.1 .Would you help
me check whether the bugs mentioned below are true? Thank you very much
for your patience.
I have a worse bug : after setting alsamixer to 6ch and restarting pulseaudio,
I have no rear sound and no dialog in 5.1 application (I select a 5.1 profile
in pulseaudio
+ the sound section in Ubuntu setting pannel is unable to test the speakers
(they remain silent while the system sound can
I'm not aware of ppc64 being expected to work, but it appears the
binaries can build. Sounds like some test cases need to be skipped??
** Tags added: ppc64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks again. That confirms the crash happens only in the live session
on:
gnome-shell --sm-disable --mode=ubiquity
but it also confirms the crash is unreportable because "Invalid core
dump". Apparently the expected core file size is about 400MB but only
8MB is found. I wonder if you waited
Thanks for the bug report. Unfortunately since you have an unsupported
PPA ("oibaf") and kernel installed, we can't technically call this an
Ubuntu bug. Does the same problem happen with the official Ubuntu
kernel?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: amdgpu
**
Thanks for the bug report. Please also report the issue to the
developers at:
https://gitlab.gnome.org/GNOME/mutter/-/issues
and then tell us the new issue ID.
** Tags added: amdgpu
** Summary changed:
- Only half of MST display is visible after boot or sleep
+ Only half of MST tiled
unity-control-center depends on indicator-sound. Either:
- indicator-sound needs its build-dependency fixed; or
- unity-control-center needs to drop its dependency on indicator-sound; or
- both of these packages need to be removed for impish.
** Also affects: unity-control-center (Ubuntu)
Removing packages from impish-proposed:
movim 0.17.1-1.1build1 in impish
Comment: FTBFS; LP: #1931315
1 package successfully removed.
** Changed in: movim (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Removing packages from impish:
ceph-deploy 2.0.1-0ubuntu1 in impish
ceph-deploy 2.0.1-0ubuntu1 in impish amd64
ceph-deploy 2.0.1-0ubuntu1 in impish arm64
ceph-deploy 2.0.1-0ubuntu1 in impish armhf
ceph-deploy 2.0.1-0ubuntu1 in
We must build armhf glibc which is y2038 safe, like our v5.1+ kernels
are (bionic-hwe and up). Thus yes, glibc should assume TIME64 SYSCALLS,
on armhf.
Also, maybe our farm can move to focal and focal kernel; or like at
least to bionic-hwe kernel.
--
You received this bug notification because
Removing packages from impish:
shim-canonical 2 in impish
shim-canonical-unsigned 2 in impish amd64
shim-canonical-unsigned 2 in impish arm64
Comment: Ubuntu-specific, superseded by functionality in shim; LP: #1934662
1 package successfully removed.
**
Removing packages from impish:
ndpi 3.0-1build1 in impish
libndpi-bin 3.0-1build1 in impish amd64
libndpi-bin 3.0-1build1 in impish armhf
libndpi-dev 3.0-1build1 in impish amd64
libndpi-dev 3.0-1build1 in impish armhf
Removing packages from impish:
ntopng 3.8.1+dfsg1-1build2 in impish
ntopng 3.8.1+dfsg1-1build2 in impish amd64
ntopng 3.8.1+dfsg1-1build2 in impish armhf
ntopng-data 3.8.1+dfsg1-1build2 in impish amd64
ntopng-data
Removing packages from impish:
redkite 1.3.1-0ubuntu1 in impish
libredkite-dev 1.3.1-0ubuntu1 in impish amd64
libredkite-dev 1.3.1-0ubuntu1 in impish arm64
libredkite-dev 1.3.1-0ubuntu1 in impish armhf
libredkite-dev
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939205
Title:
sound dummy output 21.04
To manage notifications about this bug go
Removing packages from impish:
gudev-sharp-1.0 0.1-4build1 in impish
libgudev1.0-cil 0.1-4build1 in impish amd64
libgudev1.0-cil 0.1-4build1 in impish arm64
libgudev1.0-cil 0.1-4build1 in impish armhf
libgudev1.0-cil
It seems correct to remove the binaries on riscv64 and s390x, because
stylish-haskell 0.12.2.0-1 is in Debian testing without binaries for
these architectures. But Debian has arm64 and armhf built; why is it
correct to remove these binaries, rather than fixing the build failure
in Ubuntu?
**
Removing packages from focal-updates:
openjdk-14 14.0.2+12-1~20.04 in focal
openjdk-14-dbg 14.0.2+12-1~20.04 in focal amd64
openjdk-14-dbg 14.0.2+12-1~20.04 in focal arm64
openjdk-14-dbg 14.0.2+12-1~20.04 in focal armhf
Removing packages from focal-updates:
openjdk-13 13.0.7+5-0ubuntu1~20.04 in focal
openjdk-13-dbg 13.0.7+5-0ubuntu1~20.04 in focal amd64
openjdk-13-dbg 13.0.7+5-0ubuntu1~20.04 in focal arm64
openjdk-13-dbg 13.0.7+5-0ubuntu1~20.04 in focal
This change was made by a bot.
** Changed in: linux (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/1941808
Title:
AMD desktop fails to suspend
To manage
Removing packages from impish-proposed:
qemu-web-desktop 21.05.03-1 in impish armhf
qemu-web-desktop 21.05.03-1 in impish riscv64
qemu-web-desktop 21.05.03-1 in impish s390x
Comment: NBS
3 packages successfully removed.
** Changed in: qemu-web-desktop (Ubuntu)
The other packages do not have release critical bugs in Debian, have not
been removed from testing, and are not reported to fail to build from
source in Ubuntu. They therefore don't meet the criteria for removal
and blacklisting in Ubuntu. As long as they are maintainable, we keep
them in the
Removing packages from impish:
gauche-gtk 0.6+git20160927-3 in impish
gauche-gtk 0.6+git20160927-3 in impish amd64
gauche-gtk 0.6+git20160927-3 in impish arm64
gauche-gtk 0.6+git20160927-3 in impish armhf
gauche-gtk
Override component to main
python-oslo.limit 1.4.0-0ubuntu2 in impish: universe/python -> main
python3-oslo.limit 1.4.0-0ubuntu2 in impish amd64:
universe/python/optional/100% -> main
python3-oslo.limit 1.4.0-0ubuntu2 in impish arm64:
universe/python/optional/100% -> main
python3-oslo.limit
Removing packages from impish:
sip5 5.5.0+dfsg-3 in impish
python3-sipbuild 5.5.0+dfsg-3 in impish i386
python3-sipbuild-dbg 5.5.0+dfsg-3 in impish i386
sip5-doc 5.5.0+dfsg-3 in impish amd64
sip5-doc 5.5.0+dfsg-3 in impish
Actually it appears that one usb device was the source of the problem.
It's not a common USB device so it's not likely worth fixing.
Bus 005 Device 003: ID 28f3:4000 Clover Network, Inc. Flex
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Since upgrading to 5.11.0-31-generic from 5.11.0-25-generic my system is
no longer able to enter deep sleep when I choose "Suspend" from the
Gnome power menu. The display goes blank for about 3 seconds and then
comes back to the login screen.
Machine setup:
Desktop PC
Public bug reported:
Aspectc++ is currently FTBFS with glibc 2.34. The package is fairly
active upstream, so when it is fixed we should be able to re-upload it.
jawn-smith@desktop:~$ reverse-depends -b src:aspectc++
No reverse dependencies found
jawn-smith@desktop:~$ reverse-depends
This bug was fixed in the package ceph - 15.2.13-0ubuntu0.20.04.2
---
ceph (15.2.13-0ubuntu0.20.04.2) focal; urgency=medium
[ Chris MacNaughton ]
* d/ceph-base.install: Remove ceph-deploy man page installation
(LP: #1892448).
-- James Page Mon, 26 Jul 2021 11:25:32 +0100
Public bug reported:
E: Unable to locate package liblas-bin
** Affects: liblas (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/1941805
Title:
This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
70~ubuntu2
---
gnome-shell-extension-ubuntu-dock (70~ubuntu2) impish; urgency=medium
[ Daniel van Vugt ]
* extension: Disable starting in the overview
- We don't need it when the GNOME dash is being
Just for comparison, the same PC but a different distribution with the 5.13.12
kernel.
I found not in the Ubuntu /proc/modules amdgpu or radeon, but in the other
Linux installation.
I believe thats is the problem.
** Attachment added: "cat /proc/modules"
The verification of the Stable Release Update for samba 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 samba - 2:4.11.6+dfsg-0ubuntu1.10
---
samba (2:4.11.6+dfsg-0ubuntu1.10) focal; urgency=medium
* d/p/fix-double-free-with-unresolved-credentia-cache.patch: Fix
double free with unresolved credential cache. (LP: #1892145)
-- Paride Legovini
Public bug reported:
SRU Justification:
Add device ID for BlueField-3
* Explain the bug(s)
Not a bug
* How to test
System should recognize BlueField-3 from lspci
* What it could break.
Nothing will break
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
--
** Changed in: gnome-calculator (Ubuntu)
Status: Triaged => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210607
Title:
Scientific Notation not given proper order of operations
To
** Attachment added: "lspci vmlinuz-5.11.0-31-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520997/+files/lspci-vmlinuz-5.11.0.-31-generic.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "lspci vmlinuz-5.11.0-25-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520996/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg vmlinuz-5.11.0-25-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520995/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "cat/proc/asound/cards vmlinuz-5.11.0-25-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520994/+files/ProcAsoundCards.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "lsmod vmlinuz-5.11.0-25-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520993/+files/lsmod.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "alsa-info vmlinuz-5.11.0-31-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520992/+files/alsa-info-vmlinuz-5.11.0.-31-generic.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "alsa-info vmlinuz-5.11.0-25-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520991/+files/alsa-info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Exactly the same problem occurs with the 5.11.0-31-generic kernel, only
the audio output does not work. I think I'm déjà vu.
https://bugzilla.kernel.org/show_bug.cgi?id=207515
** Bug watch added: Linux Kernel Bug Tracker #207515
https://bugzilla.kernel.org/show_bug.cgi?id=207515
--
You
** Attachment added: "aplay -l vmlinuz-5.11.0-25-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520990/+files/aplay.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
installation can't run grub install on boot partition or bootloader
partition
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
A quick guess would be the problem is glibc upstream commit
13c51549e2077f2f3bf84e8fd0b46d8b0c615912, combined with upstream commit
a26918cfda4bc4b9dad8aae1496e3ef7cbb63d96 setting
__ASSUME_TIME64_SYSCALLS based on the *build* time kernel (not runtime
kernel), and since our build farm runs a
I spoke too soon. WLAN does not work in some cases, maybe if there is
the same ID for 2 and 5 GHz.
** Attachment added: "dmesg-suspend.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.13/+bug/1941741/+attachment/5520982/+files/dmesg-suspend.txt
--
You received this bug
Is this still reproducible with snapd 2.51?
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757073
Title:
Snap stopped working
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-terminal (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/1791337
** Changed in: hedgewars (Ubuntu Xenial)
Status: Incomplete => Won't Fix
** Changed in: hedgewars (Ubuntu Trusty)
Status: Incomplete => Won't Fix
** Changed in: hedgewars (Ubuntu Precise)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are
This package didn't make into 20.10 but is included in 21.04 so I'm
setting this to Fix Released.
** Changed in: iotop-c (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: snapd
Status: Confirmed => Fix Committed
** Changed in: snapd
Milestone: None => 2.53
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940467
Title:
[snap] Nitrokey FIDO2
Setting to invalid since a hint fixed this.
** Changed in: bambam (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/1914441
Title:
fails autopkgtest on arm &
Public bug reported:
This merge is needed because there are changes in Ubuntu that are not
present in Debian.
** Affects: openssh (Ubuntu)
Importance: Undecided
Assignee: William Wilson (jawn-smith)
Status: In Progress
** Changed in: openssh (Ubuntu)
Assignee:
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
If a new library is required, that would be better suited for the GTK3 / .NET5
branch of Pinta (https://github.com/PintaProject/Pinta/tree/gtk3-v2).
Ideally we could load the metadata at the same time as the image data ..
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package postfix - 3.4.13-0ubuntu1.1
---
postfix (3.4.13-0ubuntu1.1) focal; urgency=medium
* d/postfix.postinst: tolerate search domain with a leading dot
(LP: #1906970)
-- Paride Legovini Thu, 12 Aug 2021 14:26:09 +0200
** Changed in: postfix
Apparently this is a known issue with PackageKit, but hasn't been
addressed by the developers.
https://github.com/PackageKit/PackageKit/issues/450
** Bug watch added: github.com/PackageKit/PackageKit/issues #450
https://github.com/PackageKit/PackageKit/issues/450
** Changed in: discover
Hello TimK., or anyone else affected,
Accepted zfs-linux into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.3-1ubuntu12.13 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Attachment added: "networkd-glib-2.34.trace"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+attachment/5520981/+files/networkd-glib-2.34.trace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can now confirm that the bug has been introduced strictly by the glibc
2.34, and not another package in the -proposed pocket.
My reproduction steps were as following:
Boot an Ubuntu Impish qemu VM (fully up-to-date (funnily enough, far
from being a trivial thing to do, see at the bottom for
I'm okay with this being uploaded for Impish. Thanks!
** Changed in: strace (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941750
Title:
FFe: strace FTBFS
** Description changed:
- Currently, this package will FTBFS on ppc64 when building with go 1.16.
+ Currently, this package will FTBFS on ppc64el when building with go 1.16.
This looks as follows:
go build fmt: /usr/lib/go-1.16/pkg/tool/linux_ppc64le/compile: signal:
segmentation fault (core
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
I tested this on the regular gnome ubuntu 20.04.3 and did not see the
same error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917062
Title:
Decryption passphrase prompt not displayed until
Public bug reported:
Only left half of a 4K display in MST mode visible after sleep. The same
problem often appears after boot as well. Changing mode to any arbitrary
resolution and reverting back resolves the problem.
Display Asus PQ321qe
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Defintely agree on automating this.
It's always a challenge decided which library to choose.
I would hope that is a .NET one which would make it easy for portability.
A quick google came up with this:
https://github.com/oozcitak/exiflibrary/
--
You received this bug notification because you
Public bug reported:
Please merge https://salsa.debian.org/kernel-team/linux-
base/-/commit/1ed6758e3c3f4ee21a8988d2cd83637ede095892 into Ubuntu's
linux-base package. It allows recognizing custom kernels (as often
needed for embedded scenarios) that are uncompressed, thus prefixed
vmlinux-.
See
Public bug reported:
This happens with both 40.2-1ubuntu2 and 40.2-1ubuntu3. Before uploading
the latter I could successfully build for ppc64el in PPA, though.
From the build log:
1/7 CSS styling support FAIL 0.23s (exit status 1)
--- command ---
18:49:35
Public bug reported:
Currently, this package will FTBFS on ppc64 when building with go 1.16.
This looks as follows:
go build fmt: /usr/lib/go-1.16/pkg/tool/linux_ppc64le/compile: signal:
segmentation fault (core dumped)
Sample log: https://autopkgtest.ubuntu.com/results/autopkgtest-
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => Fix Committed
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch
$ sudo apt install libgtk3-nocsd0
May be a workround. Works for me!
on Ubuntu 20.04.3
Regards
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932579
Title:
snap pt_BR locale shows warning
In terms of shim-signed and grub, the bug is the same. If you think
this is a separate bug, then please assign it away from shim-signed to
where you think the bug lies, because from a shim-signed perspective it
is the same bug.
--
You received this bug notification because you are a member of
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Found on xenial/linux-oracle/4.15.0-1080.88~16.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917616
Title:
vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
To manage notifications
Also on: xenial/linux-oracle/4.15.0-1080.88~16.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932966
Title:
kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
To manage notifications
Since 20.04.3 got released today, where this is solved, I'm closing this
ticket as Fix Released.
** Changed in: livecd-rootfs (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug
1 - 100 of 278 matches
Mail list logo
