** Changed in: grub2-signed (Ubuntu Bionic)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: grub2-signed (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Kernel
Packages, wh
Actions: cherry-pick two patches for kinetic and upload new upstream
release to lunar.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990964
Title:
FTBFS on kinetic
Status in linux pac
Well surely not more than the past year, this is not a new bug after
all, the regression was introduced with the initial boothole update when
we did the one grub split.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in Ubunt
@jeremyszu (os369510) Did you see #90, it seems your patch would cause
boot failures on older system unable to handle this memory range.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/18423
Our goal should be to merge the entire patch series into kinetic, worst
case, kinetic will not be installable for some users. This means we will
have decent results from people trying that in the next 4 weeks (by Oct
27 the release has been out 1 week).
In the meantime, next week we should push ou
OK the patch set here is broken, we gotta do this from scratch properly.
So I'm going to start cherry picking the rhboot patches for memory
management. I have applied so far from bug 1989446 the backport of "Try
to pick better locations for kernel and initrd" and cherry-picked from
rhboot the "x86-
Public bug reported:
The 5.19 kernel only reads the db and dbx keys:
jak@jak-t480s:~:master$ journalctl -b -1 -k | grep integrity
Jul 09 21:34:14 jak-t480s kernel: integrity: Platform Keyring initialized
Jul 09 21:34:14 jak-t480s kernel: integrity: Machine keyring initialized
Jul 09 21:34:14 jak-
In the logs I see different values for MOKvar from efi: so maybe it's
calculating something wrongly (or it's just not that stable).
jak@jak-t480s:~:master$ journalctl -k | grep MOK -i
Jul 12 15:14:51 jak-t480s kernel: efi: TPMFinalLog=0xbb592000 SMBIOS=0xba693000
SMBIOS 3.0=0xba69 ACPI=0xbb5f
In case you wonder: Yes I have the ubuntu UEFI PPA key in db as I needed
to test out shims signed from there :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981449
Title:
5.19 kernel
There seems to be an invalid hash presented in MokX, it fails to import
that and then doesn't load MokX (which seems reasonable). I need to
recheck with 5.15 if it still boots, maybe firmware got corrupted or
something (or 5.19 loads the key from the wrong place).
$ mokutil --list-enrolled --mokx
Here's the 5.15 log, the 5.19 one was attached by apport as
CurrentDmesg.txt already.
** Attachment added: "dmesg-5.15.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981449/+attachment/5602675/+files/dmesg-5.15.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirm
*** This bug is a duplicate of bug 1842320 ***
https://bugs.launchpad.net/bugs/1842320
** This bug has been marked a duplicate of bug 1842320
Out of Memory on boot with 5.2.0 kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
@aaronmfeld If you have an upgrade issue, please file a separate issue,
this particular one has been verified as fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2078720
Title:
Tagging this for the apt/noble and apt/oracular uploads.
** Changed in: apt (Ubuntu)
Milestone: None => ubuntu-24.10
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
** Changed in: apt (Ubuntu Noble)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Chan
One thing I wonder, the crash is one thing; but the inability of the
kernel/firmware to recover from that is another. As in, new mesa fixing
that particular crash is ok, but optimally you'd also be able to recover
from the crash with the old mesa; but the GPU restarts are failing and
the driver app
Happy to sponsor. We need to fill out the SRU template, and need to add
some test plan there as per:
https://canonical-sru-docs.readthedocs-hosted.com/en/latest/howto/standard/
https://canonical-sru-docs.readthedocs-hosted.com/en/latest/reference/bug-template/#reference-sru-bug-template
--
You r
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2083538
Title:
amdgpu: [mmhub] page fault (src_id:0 ring:8 vm
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2083176
Title:
grub-efi/install_devices becoming stale due to by-id/nvme-
Public bug reported:
It turns out that amdgpu in kernel 6.11 on the Ryzen 6850U is quite
crashy and laggy. I have attached the previous boot log which shows a
lot of errors.
It does not seem to like firefox.
Behavior visible is that it hangs, then tries resets, fails to reset and
then the screen
To the best of my knowledge the issue started happening when the kernel
was upgraded. That being said, the Firefox process that seemingly causes
stalls is a snap so it is using its own mesa and not the host one, and I
can't speak to the snap's mesa version.
--
You received this bug notification b
Attaching the Journal, the initial crash can be seen at 12:31:54, lots
going on there, but nothing root-causing this.
** Attachment added: "Journal.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+attachment/5830742/+files/Journal.txt
--
You received this bug notification b
Public bug reported:
This is a very weird case: The GNOME session crashed 3 times today, the
last time, it went to gdm, but then gdm did not recognize it was docked
and suspended. I think the kernel needed two attempts to resume, it got
suspended again after the first one; and it produced a whole
I enabled that debug option thingy. I'll try to have a go at a mainline
kernel build at some point.
Now the problem is I can't reproduce this so far. gnome-shell/xwayland
randomly exits at some point without any explanation (you can see it
just starts broken pipe at 12:31:54, no crash before, I ne
It seems your system is slow, but I can't say why. Note that your sda1
disk is corrupted:
Sep 19 10:56:08 hostname kernel: FAT-fs (sda1): Volume was not properly
unmounted. Some data may be corrupt. Please run fsck.
I assume that is your flash drive.
I also see a couple of nouveau bugs, and most
I think ~ubuntu-sponsors was subscribed by accident and am unsubscribing
it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2083538
Title:
amdgpu: [mmhub] page fault (src_id:0 ring:8 vmi
** Tags removed: rls-jj-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2055825
Title:
fips-updates: upgrade from 20.04 to 22.04 fails
Status in
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2093338
Title:
Keyboard not working after kernel upgrade
Status in
Mate has cherry-picked the fix into the branch for the pending security
update.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2098641
Title:
FAT filesystem probing fails if a
This is not a regression in valgrind; as the old valgrind works fine.
Adding a kernel task.
A smaller reproducer is `valgrind true`
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, whic
This is fine in gnome-terminal (ulimit -n is 1024) but broken in ptyxis
(ulimit -n is 1073741804)
** Package changed: linux (Ubuntu) => ptyxis (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
** Changed in: boot-managed-by-snapd (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
ht
So simply speaking
dpkg-divert --package boot-managed-by-snapd --divert
/lib/firmware.unused --no-rename /lib/firmware
would make dpkg unpack all files below /lib/firmware to
/lib/firmware.unused instead; allowing wireless-regdb to be upgraded
(and other firmware packages to be installed but be n
Diverting directories does not work of course, but we can divert the
files...
root@p:~# apt install wireless-regdb
I'm going to have a lot of fun abusing the package manager here. The
obvious first step is preventing wireless-regdb updates which is
comparatively easy.
The 2nd step is ensuring that we can actually remove the wireless-regdb
package such that you don't get held back packages. So we need to
convin
Resetting the verification tag.
Marat, it seems you have managed to remove the boot-managed-by-snapd
package, leaving you with an unsupported system configuration. This is
quite a hard thing to achieve, since the package is protected from being
removed, i.e. you need to run apt remove --allow-remo
Please be careful changing bug states, the plucky one was released.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/2096979
Title:
wireless-regdb update problem at Ubuntu 24.04.1
** Tags added: regression-updates
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/2096979
Title:
wireless-regdb update problem at Ubuntu 24.04.1 TPM-backed Full Disk
Encryption
** Changed in: boot-managed-by-snapd (Ubuntu Noble)
Importance: Undecided => Critical
** Changed in: boot-managed-by-snapd (Ubuntu Oracular)
Importance: Undecided => Critical
** Changed in: boot-managed-by-snapd (Ubuntu Plucky)
Importance: Undecided => Critical
--
You received this bug
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2100893
Title:
kernel regression where suspending worked in kernel 6
Seems I missed tagging this todo
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/2096979
Title:
wireless-regdb update problem at Ubuntu 24.04.1
301 - 340 of 340 matches
Mail list logo
