Public bug reported:
Starting Eclipse will 100% likely cause a complete system freeze within a few
minutes.
Same problem occurs using Wayland and X.org.
See the attached kernel stack trace.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-28-generic 5.13.0-28.31
** Changed in: openssh (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/47958
Title:
ssh-agent clobbers LD_LIBRARY_PATH and other environment
Public bug reported:
rerunning the installer solved the problem...
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: ubuntu-advantage-tools 27.6~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (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/1960964
Title:
The test packages solve the problem for us.
thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951490
Title:
Can't print after update to 4.13
To manage notifications about this bug go to:
FYI: I used an
`asus eepc 1000HE (intel atom n270, 1gb, intel mobile 945gse
integrated), wireless RT2790`
for QA-testing releases up to the 19.04 (disco) cycle when i386 ISOs
were dropped for the last two flavors providing i386. I don't know why
you'd try to install a release so far out of
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
@crashbit-gmail: There was no update of zsh in Jammy so far. If an
update fixed this, it was not in zsh but maybe in a library. And indeed,
one day after this bug report, glibc 2.35 (as mentioned in the missing
symbol) got uploaded to jammy as well:
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2011-3389
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2011-4944
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-0845
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2012-1150
** CVE
SUSE-FU-2022:0447-1: An update that solves 54 vulnerabilities, contains
6 features and has 247 fixes is now available.
Category: feature (moderate)
Bug References:
SUSE-FU-2022:0452-1: An update that solves 54 vulnerabilities, contains
6 features and has 247 fixes is now available.
Category: feature (moderate)
Bug References:
SUSE-FU-2022:0450-1: An update that solves 54 vulnerabilities, contains
6 features and has 247 fixes is now available.
Category: feature (moderate)
Bug References:
SUSE-FU-2022:0444-1: An update that solves 51 vulnerabilities, contains
21 features and has 249 fixes is now available.
Category: feature (moderate)
Bug References:
SUSE-FU-2022:0456-1: An update that solves 54 vulnerabilities, contains
6 features and has 247 fixes is now available.
Category: feature (moderate)
Bug References:
SUSE-FU-2022:0445-1: An update that solves 183 vulnerabilities, contains
21 features and has 299 fixes is now available.
Category: feature (moderate)
Bug References:
SUSE-FU-2022:0454-1: An update that solves 54 vulnerabilities, contains
6 features and has 247 fixes is now available.
Category: feature (moderate)
Bug References:
** Changed in: firefox
Importance: Wishlist => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/402621
Title:
Firefox should have resizable form fields like Safari
To manage notifications
[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux-signed-hwe-5.11 (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: linux-signed-hwe-5.11 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for looking into this!
I was hoping to create an IoT package that was agnostic of which device
I deploy it on to, and cloud-init is great for this because it gives me
a universal API for provisioning that's supposed to work across all
ubuntu flavors and even other distros...
So for
** Attachment added: "Files inside /var/log from one of the daily builds of
22.04"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1961079/+attachment/5561526/+files/log.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Description of the feature request:
The DellEMC PowerEdge RAID Controller(PERC) S130/S140 is RAID solution
for the DellEMC PowerEdge systems configured through Chipset SATA
controller. It does not use any dedicated Hardware for RAID operations.
It is set up/configured by the system BIOS. Using
** Attachment added: "partitions of md-raid disk also cannot be chosen as boot
disk - no such option listed in subiquity"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1961079/+attachment/5561525/+files/ubuntu-3.PNG
--
You received this bug notification because you are a member of
** Attachment added: "Cannot choose md-raid disk as Boot disk - no such option
listed for the disk"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1961079/+attachment/5561524/+files/ubuntu-2.PNG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Steps:
1. Setup a DellEMC 14G PE server with 2 Onboard SATA disks.
2. Setup a md-raid (RAID1) on these SATA disks through BIOS S140 controller in
UEFI mode.
3. Start installing Ubuntu 22.04
4. See that user cannot select md-raid disk as boot disk. Installation on
md-raid disk cannot proceed.
**
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/mysql-8.0/+git/mysql-8.0/+merge/415713
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922412
Title:
apport hook fails
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/mysql-8.0/+git/mysql-8.0/+merge/415713
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958641
Title:
Apport hook
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/mysql-8.0/+git/mysql-8.0/+merge/415713
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922413
Title:
mysql's apport
Zero crashes since 20.10 so consider this fixed.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880218
Title:
Great, thanks for the explanation. So blaming just the nvidia-drm kernel
module seems most reasonable right now. It is what's crashing after all.
Most likely the fix will come in the form of a new Nvidia driver. Please
try apt install nvidia-driver-510 or via the 'Additional Drivers' app.
You
I am guessing the problem will be bug 1960387.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336
Title:
No login screen when fprintd crashes
To manage notifications about this bug go to:
Bug 1933633 is a clean exit whereas this bug 1960336 is a segfault. So
the two bugs should be kept separate.
We can make this bug about both your issues though:
(a) fprintd crashes with SIGSEGV; and
(b) login screen can't survive fprintd failure.
Next please follow the steps in
Hi Robie,
Thanks for sharing the changes with other flavors.
Just want to clarify the comment#14-16 are talking about Jammy which shouldn't
blocking Focal#5 and Impish#10 SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: fprintd (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960387
Title:
fprintd crashed with SIGSEGV in log_v() from usbi_log() from
Hi Chris,
For -390, we did find a machine to test it and also provided a corresponding
handler in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1957094
The bug1957094 is completed, does it solve your concerns?
Also CC, Brian and Timo for awareness.
--
You received this
Unfortunately i cant do a clean install since this is my main machine.
As a workarround i set hwdec=drm in /etc/mpv/mpv.conf and it works just fine,
don't know if the vaapi error affects any other programs.
if i set the display to drm in vainfo i get no errors.
vainfo --display drm
libva
There's a new upstream version of telegraf, so I'm working on merging it
now.
** Changed in: telegraf (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade:
installed mysql-server-8.0 package post-installation script subprocess returned
error exit status 1
+ Invalid config from upgrading since old version of mysql: stray config value
Public bug reported:
[Impact]
* MRE for latest stable fixes of Postgres released on February 2022
[Test Case]
* The Postgres MREs traditionally rely on the large set of autopkgtests
to run for verification. In a PPA those are all already pre-checked to
be good for this upload.
Assuming the very same change fixed things in focal, I think we can
safely mark as verified also for impish (not to regress in case of
updates).
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of
[Closing as expired, due to insufficient information provided]
** Changed in: mysql-8.0 (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/1916590
Title:
09:35:28
If you've got involvement of `lxpanel` (LX Panel), as that's not used by
Lubuntu 18.10 upwards, thus I'd recommend re-install as already
outlined. Lubuntu last used that program/package in 18.04 and it won't
exist on LXQt installs.
When Lubuntu switched from LXDE to LXQt; many used applications
** Changed in: mysql-8.0 (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryce)
** Changed in: mysql-8.0 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You say "with no video driver PPAs". As an experiment, you could try, as
I did, with NO PPAs (e.g. by doing a clean reinstall from ISO). Perhaps
it's due to a PPA that is not obviously related. Also, could the fact
that you are on 20.04.3 be a problem? If so, but you require the LTS,
you could use
** Also affects: gjs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gjs (Ubuntu)
Importance: Undecided => Medium
** Changed in: gjs (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gjs (Ubuntu)
Status: New => In Progress
--
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961041
Title:
gnome-shell crashed with SIGSEGV in meta_context_run_main_loop()
To manage
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also use fish shell, so it seems to be the combination of snapd + fish
as @iperry83 outlined.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960972
Title:
All snap applications missing from
AlderHorst, thanks for the feedback.
So gjs in this case should definitely not crash, and I've fixed it there
[1] (will prepare a package soon).
I'm quite curious to understand how is possible that Gio would emit a
null device in such case, but that's another issue I'll have to handle.
I'll try
There are some decisions that are smart. This decision was not one of
those.
I was setting up multiple machines and the default is now to use half a
disk, which means I now need to manually edit every single partition
configuration on each of those machines instead of using the default
full disk
** Changed in: glibc (Ubuntu Focal)
Milestone: ubuntu-20.04.4 => focal-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951033
Title:
20.04 SRU
To manage notifications about this bug go
** Changed in: adsys (Ubuntu Focal)
Milestone: ubuntu-20.04.4 => focal-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929038
Title:
[SRU] Backport to 20.04 LTS
To manage notifications
** Changed in: grub2 (Ubuntu)
Milestone: ubuntu-20.04.4 => focal-updates
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947046
Title:
EFI stub: ERROR: FIRMWARE
** Changed in: ubiquity (Ubuntu Focal)
Milestone: ubuntu-20.04.4 => focal-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875062
Title:
[20.04] Keyboard layout not enabled immediately
This bug was fixed in the package ubuntu-drivers-common -
1:0.9.0~0.20.04.5
---
ubuntu-drivers-common (1:0.9.0~0.20.04.5) focal; urgency=medium
* gpu-manager.c:
- Fall back from on-demand to on if nvidia < 450 (LP: #1957094).
-- Alberto Milone Tue, 18 Jan 2022
08:58:23
The verification of the Stable Release Update for nvidia-settings 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 nvidia-settings -
470.57.01-0ubuntu0.20.04.3
---
nvidia-settings (470.57.01-0ubuntu0.20.04.3) focal; urgency=medium
[ Jeremy Szu ]
* debian/patches/18_remove_power-saving_if_on-demand.patch,
The attachment "mountfix workaround" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
Sorry, forgot this while filling in all the ISO tracker stuff (re-used
the cards for the tests). The permissions were checked on a 3B+, 3A+,
4B, CM4, and Pi 400 under both armhf and arm64. The camera functionality
was tested under armhf and arm64 on the 3B+ and the 4B.
--
You received this bug
** Changed in: fwupd (Ubuntu Focal)
Milestone: ubuntu-20.04.4 => focal-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949412
Title:
Upgrade fwupd for Atomic Docking Support
To manage
** Changed in: raspberrypi-userland (Ubuntu Focal)
Milestone: ubuntu-20.04.4 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958563
Title:
[SRU] Wrong permissions on vcio
To manage
** Package changed: ubuntu => linux-signed-hwe-5.13 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961113
Title:
Problemwith Touchpad and Keyboard on Acer Swift
To manage notifications
Hello
I worked around the problem by removing the words quiet splash from the entry
menus of the /boot/grub/grub.cfg file so that I could enter the password. But
the swap partition is not mounted.
Probably because is name is now SDA2 and not SDC2 which was the name during
installation on a
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/1961123
Title:
package linux-libc-dev:amd64 5.4.0-99.112
@Dave Jones - Could you add some verification details to this bug
report? The SRU team frowns upon just flipping tags from v-needed to
v-done.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958563
*** This is an automated message ***
This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu. As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/smartmontools/+git/smartmontools/+merge/415701
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/smartmontools/+git/smartmontools/+merge/415702
--
You received this bug
Yes, I'm building 4.15.5 currently
** Changed in: samba (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946839
Title:
Merge samba from Debian unstable for
** Description changed:
+ [SRU]
+ [Impact]
+
+ The "drivedb.h" file is the smartmontools drive database file used to
+ perform the scan actions. This file can be updated through update-smart-
+ drivedb command, but debsums may complain about drive.h in the form of a
+ false negative verification
*** This bug is a duplicate of bug 1929213 ***
https://bugs.launchpad.net/bugs/1929213
As it happens I've just started to work on this. It's a duplicate of
another bug though, I'll mark this as such.
** This bug has been marked a duplicate of bug 1929213
Ubuntu server LVM creates clone
Public bug reported:
dpkg: error processing package linux-libc-dev:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
Errors were encountered while processing:
linux-libc-dev:amd64
E: Sub-process /usr/bin/dpkg returned an
** Summary changed:
- No login screen when fprintd is installed
+ No login screen when fprintd is installed and not starting
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960336
Title:
No login
hi, it seems it does not start.
output from terminal:
ubuntu@ubuntu-inspiron-5482:~$ sudo apt install fprintd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
fprintd
0 upgraded, 1 newly installed, 0
check https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/arm64/f/fwupd/20220216_061543_8c886@/log.gz
Seems failed here:
FuMain got hint locale=C.UTF-8
[31m[1mWARNING:[0m The daemon has loaded 3rd party code and is no longer
supported by the upstream developers!
Thanks for review Łukasz.
Fixes and comments inline. With the requested change in the version
number, I'm using a different PPA to upload the version since it is
lower than the one in jammy-package PPA. New one is:
https://launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-jammy
> Remark re: the
This bug was fixed in the package ubiquity - 20.04.15.19
---
ubiquity (20.04.15.19) focal; urgency=medium
* Backport the ability to unhide passwords that are being typed-in during
various stages of the installation (LP: #1960306).
* Automatic update of included source
This bug was fixed in the package partman-auto - 134ubuntu13.1
---
partman-auto (134ubuntu13.1) focal; urgency=medium
* Bump minimum and maximum sizes for /boot partitions on default, x86, and
EFI platforms to a minimum of 768Mb and maximum of 1536Mb. (LP: #1959971)
-- Brian
The verification of the Stable Release Update for ubiquity 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
This bug was fixed in the package ubiquity - 20.04.15.19
---
ubiquity (20.04.15.19) focal; urgency=medium
* Backport the ability to unhide passwords that are being typed-in during
various stages of the installation (LP: #1960306).
* Automatic update of included source
The verification of the Stable Release Update for partman-auto 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 is awaiting verification that the linux-
gcp-5.13/5.13.0-1015.18~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
gcp-5.13/5.13.0-1015.18~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem
Public bug reported:
[Impact]
When amd-sfh is loaded the sensors connected do not change values at all
(ALS sensor).
Here is the monitor sensors output, which doesn't change.
$ sudo monitor-sensor
Waiting for iio-sensor-proxy to appear
+++ iio-sensor-proxy appeared
=== No accelerometer
@till-kamppeter, I'm not certain what you mean by the "upstream source."
The printer auto-installed when I installed Ubuntu 20.04 shortly after
its release.
After your post, I did:
# apt purge cups cups-client cups-bsd
# apt purge hplip hpijs printer-driver-gutenprint
# apt autoremove
# reboot
#
Public bug reported:
[Impact]
AMD Systems don't enter PC6 at runtime and cause failures to enter
s2idle.
Currently the fix is from kernel driver rather than MP2 firmware, which
disable interrupts from kernel driver to fix MP2 firmware blocking
CPUOFF.
[Fix]
[Test]
[Where problems could
The verification of the Stable Release Update for livecd-rootfs 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 livecd-rootfs - 2.664.39
---
livecd-rootfs (2.664.39) focal; urgency=medium
* Switch to building raspi classic images using the 'classic' branch instead
of '18'. This is needed for proper Pi Zero 2 support (LP: #1960950).
-- Łukasz 'sil2100'
** Also affects: subiquity (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/1961079
Title:
[Ubuntu 22.04] Allow ESP installation on md-disks in
Public bug reported:
[Impact]
AMD has a known BIOS bug right now that leads to the following WARN
traceback during s0i3 resume (see below).
This doesn't have (measurable) functional impact to the system or GPU,
but it is an ugly message to have in place and makes it look like a
potentially
This bug was fixed in the package dh-python - 5.20220215
---
dh-python (5.20220215) unstable; urgency=medium
* pybuild plugin: Explicitly unpack wheels using the "deb_system" sysconfig
scheme, allowing python3.10 to change the default sysconfig scheme to
"posix_local". (LP:
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
To purchase an Ubuntu Advantage subscription for extended support beyond
standard,
** Description changed:
In the context of an automatic preseed / subiquity installation usage of
- the efitools fails inside the target chroot provided by the curtin tool.
+ the efitools fail inside the target chroot provided by the curtin tool.
curtin does setup the sys and efivarfs
** Tags added: fr-2060
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960926
Title:
[VROC] Installation on RAID volume fails - ubuntu 22.04
To manage notifications about this bug go to:
Public bug reported:
In the context of an automatic preseed / subiquity installation usage of
the efitools fail inside the target chroot provided by the curtin tool.
curtin does setup the sys and efivarfs filesystems correctly:
curtin in-target --target=/target -- efi-readvar
No efivarfs
Public bug reported:
Title: Vulnerability in Glibc - CVE-2022-23219
Expectation: Glibc needs to be upgraded to glib v2.35 (Feb2022 release)
Details of CVE - https://nvd.nist.gov/vuln/detail/CVE-2022-23219 ;
https://ubuntu.com/security/CVE-2022-23219
Description: The deprecated
** Tags added: needs-packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961024
Title:
Sync liquidsoap 2.0.2-1 (universe) from Debian unstable (main)
To manage notifications about this bug go
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1960083
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1 - 100 of 387 matches
Mail list logo
