** Patch added:
"0134-linuxefi-fail-kernel-validation-without-shim-protoco.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607435/+files/0134-linuxefi-fail-kernel-validation-without-shim-protoco.patch
--
You received this bug notification because you are a me
** Patch added:
"0133-x86-efi-Allow-initrd-params-cmdline-allocations-abov.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607434/+files/0133-x86-efi-Allow-initrd-params-cmdline-allocations-abov.patch
--
You received this bug notification because you are a me
This patch is not from upstream or rhboot but which has been submitted as a MP
to rhboot
https://github.com/rhboot/grub2/pull/102
+0129-Try-to-pick-better-locations-for-kernel-and-initrd.patch
+0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch
+0131-x86-efi-Re-arrange-grub_cmd_linux
** Patch added: "0132-x86-efi-Make-our-own-allocator-for-kernel-stuff.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607433/+files/0132-x86-efi-Make-our-own-allocator-for-kernel-stuff.patch
--
You received this bug notification because you are a member of Ubu
** Patch added: "0131-x86-efi-Re-arrange-grub_cmd_linux-a-little-bit.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607432/+files/0131-x86-efi-Re-arrange-grub_cmd_linux-a-little-bit.patch
--
You received this bug notification because you are a member of Ubunt
** Patch added:
"0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607431/+files/0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch
--
You received this bug notification because you are a me
As my MP from comment#69 doesn't have response from rhboot team.
Shared the debdiff here for review to consider to carry it in Ubuntu.
** Patch added: "0129-Try-to-pick-better-locations-for-kernel-and-initrd.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+attachment/5607
Just received more updates and back to the same issue. 167.047420 MTD
device name must be supplied (device name is empty) stuck at username
prompt.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bug
*** This bug is a duplicate of bug 1979113 ***
https://bugs.launchpad.net/bugs/1979113
This was fixed by installing wireplumber, so I think it's a duplicate of
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1979113
** This bug has been marked a duplicate of bug 1979113
Kinetic sou
This bug was fixed in the package curl - 7.84.0-2ubuntu1
---
curl (7.84.0-2ubuntu1) kinetic; urgency=medium
* d/patches: Fix atomic use for RISC-V (LP: #1982545)
-- Alexandre Ghiti Thu, 21 Jul 2022
18:59:11 +0200
** Changed in: curl (Ubuntu)
Status: New => Fix Released
Unfortunately, from what I'm reading in the description and logs, it
appears as though this USB device isn't "standards compliant", meaning
it reports values outside of the standard range that Apple created and
Linux adopted for audio devices to be driverless.
I'm seeing these warnings:
> Warning
The latter option sounds nicer.
BTW can someone comment on
https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/1392954
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad
But I do believe it's simply the wrong package being upgraded here. The
new apt package removes the conffiles the old library version needs, so
it doesn't protect anything, so we need to make sure that apt Breaks
libapt-pkg6.0 (<< 1.6.15) [or Depends on >= 1.6.15, whatever ends up
nicer).
--
You
Jarno, you do realize that you need to upgrade libapt-pkg6.0, not apt?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may rem
Thereafter I installed the proposed apt by
$ sudo apt install apt -t=bionic-proposed
$ apt --version
apt 1.6.16 (i386)
$ apt autoremove -s
$ uname -r
5.4.0-121-generic
$ apt autoremove -s
NOTE: This is only a simulation!
apt needs root privileges for real execution.
Keep also in mi
** Package changed: ubuntu => alsa-driver (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1983998
Title:
USB sound card not detected
Status in alsa-driver pac
You have been subscribed to a public bug:
usbc mics https://www.boya-mic.com/lavaliermicrophones/1430.html
connects and immediately disconnects, ls usb hangs for a while, when usbc
device is connected.
it works on win laptop well.
```
[10877.622942] usb 3-4: new full-speed USB device number 28
For some reason the test case worked even with apt 1.6.14 as the
following shows:
$ apt policy apt
apt:
Installed: 1.6.14
Candidate: 1.6.14
Version table:
1.6.16 400
400 http://mirrors.nic.funet.fi/ubuntu bionic-proposed/main i386
Packages
*** 1.6.14 500
500 http://mir
I have the same issue on Ubuntu 22.04:
[4.528478] systemd[1]: Starting Load Kernel Module mtdpstore...
[4.533051] mtd device must be supplied (device name is empty)
[4.833395] mtd device must be supplied (device name is empty)
--
You received this bug notification because you are a m
Note for reader: The wrong version is in the list of packages to be
removed.
** Changed in: apt (Ubuntu)
Importance: Undecided => Low
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
Having the same problem since the upgrade from Ubuntu 21.04 to Ubuntu
22.04.1 LTS. SSL vpn does not connect with certificate error (Server
certificate verify failed: signer not found) followed by a 404. Tried
selecting root intermediate & appliance cert via the vpn config (next to
the option 'CA ce
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://
Thanks, I’ll look at that.
I note that this issue is now a confirmed bug. What does that mean in
practical terms? Will it be dealt with this week, this month, this
year…?
I need to be able to boot from NFSv4. If RaspiOS can do that it might
make sense for me to move after 15 years from Ubuntu to
Regarding zlib focal-proposed migration:
For libbio-samtools-perl it's the same situation like on kinetic.
samtools-legacy requires the PR #1258, and libbio-samtools-perl a rebuild (to
link against the new libbio-dev). See update-excuse bug LP#1983255.
On top vcftools misses the 'Remove compress
Thanks Fabian, creating a containerd config and putting `SystemdCgroup =
true` there did fix it for me
By the way, how did you manage to find the cause of this issue? I want
to have the same debugging skills as you do.
** Also affects: containerd (Ubuntu)
Importance: Undecided
Status: N
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
If an update for a package is available but not installed, simulating a
purge shows the wrong version.
On that 20.04 system, an update to libxml2 2.9.10+dfsg-5ubuntu0.20.04.4
was available but only the ".3" one was installed. Simulating a purge
gives this bogus output (with `
I am having the same issue. Unfortunately the systems are already in
production so testing is a bit limited and the issue was not present at
first (not sure why or we didn't notice somehow).
I can confirm that I am seeing approx. 8% loss and huge latency > 1s sometimes.
Both tested with Ubuntu 18.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409272#14 for a
work-around which replaces nfsmount in the initrd with /sbin/mount.nfs.
But that probably pulls in dependencies and blows up the size of the
initrd.
--
You received this bug notification because you are a member of Ubuntu
Touch
Debian 11 is also broken if an intird is being used but Raspberry Pi OS
is *not* using an initrd hence not using nfsmount.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/195471
Verified.
For bionic I ran
mmdebstrap -v --keyring /usr/share/keyrings/ubuntu-archive-keyring.gpg
--aptopt='Acquire::http::proxy "http://localhost:8000/";;' bionic bionic-
proposed http://archive.ubuntu.com/ubuntu 'deb
http://archive.ubuntu.com/ubuntu/ bionic-proposed main'
to enable proposed an
The upstream bug is in Debian 11. The current version of RaspiOS, which
seems to support booting from NFSv4, is a Debian 11 derivative. That
means that RaspiOS has fixed it for Debian 11. Is it possible to copy
the RaspiOS solution?
--
You received this bug notification because you are a member o
Public bug reported:
When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty
much always) a crash from tracker-extract, as described in the following
error report:
https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0
The crash occurs during the upgrade, which mean
This bug was fixed in the package gdk-pixbuf - 2.40.0+dfsg-3ubuntu0.3
---
gdk-pixbuf (2.40.0+dfsg-3ubuntu0.3) focal-security; urgency=medium
* SECURITY UPDATE: Buffer overwrite in io-gif-animation.c
composite_frame() (LP: #1982898)
- debian/patches/CVE-2021-46829.patch: gif:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: klibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/b
Hello Jarno, or anyone else affected,
Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.16 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Te
Hello Julian, or anyone else affected,
Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.16 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/T
Hello David, or anyone else affected,
Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.16 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Te
Thanks for the bug report. This may be caused by:
* The Intel kernel graphics crash mentioned in CurrentDmesg.txt
* An Nvidia driver problem (if the HDMI port is wired to the Nvidia GPU)
* Something else
Firstly, to see if we can stop the Intel graphics crash from happening
please try adding t
Public bug reported:
In the windows, hdmi display monitor work.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidi
40 matches
Mail list logo
