** 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
** 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
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
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
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
** 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-
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
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
** 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
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
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
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
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
@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:
Upgrading with ubuntu-release-upgrader from proposed also worked
correctly:
$ lxc list -c nft
+--+--+-+
| NAME | BASE IMAGE | TYPE |
+--+--+-+
| jammy-to-noble-p
@sil2100 The regression in time is back to the old behavior prior to
24.04.20; actually it's a bit faster as there is just a single action
group now. But the reason for it was that we iterated over all packages
in the cache and recorded their selected state in case we needed to undo
a change (verif
Verifying the apt/jammy SRU:
I installed libapt-pkg6.0=2.4.13 from proposed, then run `do-release-
upgrade -p` (`-d` should work now too, but was broken before):
The headers for the running kernel are not being removed:
Remove (was auto installed) binutils binutils-common
binutils-x86-64-linu
** Description changed:
(For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates)
[Impact]
Obsolete packages can be removed despite still having reverse dependencies
installed, for example:
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04 vi
** Description changed:
+ (For APT SRU versioning, see https://wiki.ubuntu.com/AptUpdates)
+
[Impact]
Obsolete packages can be removed despite still having reverse dependencies
installed, for example:
-
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04
ubuntu-release-upgrader SRU uploaded to noble and also uploaded to
oracular.
These reintroduce the slow path as a fallback, specifically for APT
versions prior to this SRU (and hence mantic); they also fix that code
to correctly consider running kernels (and KeepInstalledSection) in the
removal of
apt/jammy SRU uploaded. The ones for noble and devel need a bit more
massaging due to test suite failures but are not relevant before
oracular is released (noble's apt is used for noble->oracular updates)
** Also affects: apt (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affe
** Description changed:
+ [Impact]
+ Obsolete packages can be removed despite still having reverse dependencies
installed, for example:
+
+
Now that 24.04.1 has been released, 22.04 users are encouraged to upgrade to
24.04 via the `do-release-upgrade` command. This issue was seen whilst test
Turns out that yes this is a bug in the APT solver:
https://salsa.debian.org/apt-team/apt/-/merge_requests/373/diffs
It was not restoring/keeping obsolete (in its parlance, no longer
downloadable) packages that are marked for removal due to a false
optimization.
--
You received this bug notific
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
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:
Upgrading from jammy to noble results in a lin
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => Triaged
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Kernel
Packages, wh
Thanks this seems to be a bug in the APT solver not undoing the purge
requests here, a regression from when we switched to the new obsoletes
handling. This is odd, I am investigating
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aw
This is missing the /var/log/dist-upgrade information, commonly
collected by ubuntu-bug ubuntu-release-upgrader
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
The starfive and laptop kernels are obsolete, on mantic release version
still, and should be removed per discussion with kernel team on
Mattermost.
$ reverse-depends src:linux-starfive # some reverse-depends bug
$ reverse-depends src:linux-laptop
No reverse dependencies foun
Uploaded procps with the file; leaving gamemode task open because maybe
dynamic enhancements there still make some sense in 24.10
--
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/2057792
Tit
I'm agreeing with desktop in following Fedora to bump to 1048576, the
precedence makes this safe, and this I consider this a bug fix for
crashing software and not a feature request.
** Changed in: procps (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Status: Con
Subscribing Canonical desktop team to get their input.
Basically the ask is to ship this file:
https://src.fedoraproject.org/rpms/systemd/blob/f39/f/10-map-count.conf
I believe if we do it should be shipped in procps; or possibly, gamemode
should set that option?
** Also affects: procps (Ubuntu
Oh but please don't use `[trusted=yes]`, just add the repository with
add-apt-repository ppa:ubuntu-uefi-team/backports-build.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2051999
Ti
There doesn't seem to be anything to sponsor here, so I'm unsubscribing
ubuntu-sponsors. Please make sure to keep your ubuntu-sponsors
subscriptions current so we don't waste time in complex multi package
bugs trying to figure out if there's anything to do for us.
--
You received this bug notific
Waiting for 6.5.13 to actually build but on 6.6.0-14 from proposed now
which is based on 6.6.3 which probably has all the fancy patches too
--
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/20
These ones I don't remember seeing before:
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
--
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/2045899
Title:
More am
I saw similar messages in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032386 but that
only caused hangs and not block the entire desktop (and Firefox is good
now so I don't know)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Attachment added: "OlderDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+attachment/5727266/+files/OlderDmesg.txt
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Pac
Public bug reported:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level but
the GUI doesn't actually recover and I also can switch tty with the
keyboard.
I have attached the two crashes from yesterday, they look slig
Unsubscribing ubuntu-sponsors, please resubscribe when you have new
debdiff(s).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2042902
Title:
ucm2: soundwire: add rt713 SDCA devi
update-initramfs -c call by kernel postinst hook is not covered, but we
need to make sure the initramfs is there at kernel configuration point
because we need it to be there when updating boot loaders.
e.g. if we triggered both in that case, update-grub could run before
update-initramfs.
if we in
Draft fix for update-grub: https://salsa.debian.org/grub-
team/grub/-/merge_requests/46
Still need to take care of grub-install at some point, haven't figured
out the best approach there yet.
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
**
@Andy I'm unassigning you and changing the bug status as the initramfs
part has been resolved, update-initramfs does
if [ -n "$DPKG_MAINTSCRIPT_PACKAGE" ] && [ $# = 1 ] && [ "$1" = -u ]; then
if dpkg-trigger --no-await update-initramfs; then
** Tags removed: rls-jj-incoming
** Tags added: foundations-todo
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** Tags removed: rls-mm-incoming
** Changed in: systemd (Ubuntu)
Importance: High => Medium
--
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/2036968
Title:
Mantic minimized/minimal clo
** Also affects: grub2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2-unsigned (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Jammy)
Another occurence in latest boot.
Actually the same call chain it seems.
** Attachment added: "Dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035028/+attachment/5700876/+files/Dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, whic
FWIW, this was after this morning's UEFI firmware update.
Devices that have been updated successfully:
• Battery (1.1.6 → 1.2.7)
Public bug reported:
I was locking my screen, so my gnome-shell got killed
(https://bugs.launchpad.net/ubuntu/+bug/2034619) but this time I logged
in again and opened firefox and then everything froze except cursor and
magic sysrq.
(Of course after sysrq-b I rebooted and my USB hub failed to init
Complete journal from 15:40 to 16:00
** Attachment added: "JournalAt1540To1600.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035028/+attachment/5699730/+files/JournalAt1540To1600.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Public bug reported:
In 6.5.0-4-generic, tried switching Momentum 4 wireless headphones
between headset and handsfree profiles and I think also ended up cycling
it on/off, causing a kernel bug in the memory management.
Sep 08 15:54:45 jak-t14-g3 kernel: [ cut here ]
Sep 08
There doesn't appear to be anything to sponsor here (yet?), so
unsubscribing ubuntu-sponsors. You may resubscribe once there's a
debdiff that needs sponsoring by us.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https
Right so it seems we forgot to bump the size requirements in ubuntu-
release-upgrader when bumping them in the installer in bug 1959971, you
probably should not have been able to upgrade. Albeit the size it seems
is determined from the initramfs that is in /boot.
We also don't seem to acccount for
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- APT installs 3 kernels at once so /boot runs out of free space left and
partition size does not increase alongside with newer ubuntu versions
+ Bump minimum /boot size in ubuntu-re
We generally don't know how much space is going to be needed. APT only
keeps 2 kernel versions around, and the /boot partition is sized
accordingly for 3.
If you override this by marking kernels as manually installed, or
manually installing other versions you need to ensure that there is
enough sp
** Changed in: thermald (Ubuntu Jammy)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1995606
Title:
Upgrade thermald to 2.5.1 for Jammy (22.04)
Stat
The bug description does not match the requirements for an SRU,
particularly "low" is no reasonable answer to "where problems could
occur"
** Changed in: thermald (Ubuntu Jammy)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Pack
Unsubscribing ubuntu-sponsors as this seems done except for this
firmware-sof kinetic tag which is New and I hereby mark Incomplete as
it's not clear if there's anything left to do there to me
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Unsubscribing ubuntu-sponsors as this seems done except for this
firmware-sof kinetic tag which is New and I hereby mark Incomplete as
it's not clear if there's anything left to do there to me
** Changed in: firmware-sof (Ubuntu Kinetic)
Status: New => Incomplete
--
You received this bug
I don't see anything sponsorable for backport-iwlwifi-dkms/focal and the
other tasks are in various done states, so I am going to mark this task
Incomplete and unsubscribe ubuntu sponsors.
** Changed in: backport-iwlwifi-dkms (Ubuntu Focal)
Status: New => Incomplete
--
You received this b
Unsubscribing Ubuntu Sponsors, as this issue seems to be fairly complex
and the patch seems controversial and incomplete.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libatasmart in Ubuntu.
https://bugs.launchpad.net/bugs/1581594
Title
*** This bug is a duplicate of bug 1936857 ***
https://bugs.launchpad.net/bugs/1936857
** This bug has been marked a duplicate of bug 1936857
grub-install: error: efibootmgr: not found.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I'm going to set this to Won't Fix because that seems to be an important
part of the solver logic, and the workarounds - running upgrade first,
or using ubuntu-drivers - are easy to do and the potential for
regression significantly outweighs them.
This will get solved eventually by a nicer solver
** Changed in: apt (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513
Title:
apt will not install nvidia-dri
I think we debugged this recently but I'm not sure where the end result
of this is that we do not mark packages for removal that have an upgrade
available, hence we end up without a removal request after the first
stage solver, and the Conflicts solver that runs after can't solve that.
--
You rec
Reproduced issue and dumped test case into https://salsa.debian.org/apt-
team/apt-tests/-/blob/main/edsp/fail-ubuntu-1992513.edsp.log for future
analysis when doing solver work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphi
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513
Title:
apt will not install nvidia-driver-470-server if nvidia-
dr
Please decide whether you are reporting a missing sound driver or the
grub-install crash, you can't put two bugs into one report.
Regarding the grub crash it's curious but an issue in the firmware
variable handling, not grub.
** Package changed: grub2-signed (Ubuntu) => linux (Ubuntu)
** Changed
Actually let me reassign to Linux and mark incomplete.
--
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/2007286
Title:
Ubuntu does not clean out old kernel module files (in /lib/modules)
There can be many reasons why files remain. Did you purge the packages
for those Linux versions? Did you do any dkms modules.
This is not a bug in apt, apt is not responsible for those files.
** Changed in: apt (Ubuntu)
Status: New => Invalid
** Package changed: apt (Ubuntu) => linux (Ubu
This fix will be included in grub2-unsigned/2.06-2ubuntu14.1 for
kinetic, jammy, focal, bionic. Binaries have been built in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages
for kinetic.
Signing request: https://answers.launchpad.net/canonical-signing-
jobs/+question/704589
**
The entire upload will be uploaded to all older releases but we do have
a security upload already in the unapproved queues that should go out
first, but that needs approving those first, them passing the SRU
verification, a resigning against the new signing key the new shim
needs, and finally someo
The term you're looking for is workaround, not triage or fixes. Triage
is the process of understanding the bug and marking it the correct
things.
Not using the same language as everyone else and writing very long
comments makes it hard to understand.
First I thought you reported an out of memory
Hi ybdjkfd I don't really understand what you are doing and how it's
relevant. This issue should be fixed in lunar-proposed 2.06-2ubuntu16,
please only add comments if you have meaningful insights regarding the
verification of that update.
--
You received this bug notification because you are a m
** Changed in: grub2-unsigned (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: grub2-signed (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
I see it was marked Fix released for linux (Ubuntu), however it's not
actually fixed in lunar, not even the update from kinetic-proposed has
been copied up to lunar-proposed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 i
I have now picked all the rhboot patches in 2.06-2ubuntu16~ppa1 in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages
and will boot that before uploading to the archive.
This *should* allow initrds over 4GB but obviously bugs could be there.
The important bit is that we are now
I think kernel team needs patch sent to ML, but I don't do a lot of
kernel stuff. FWIW, here's the log from 6.1-rc5 which includes the fix:
Nov 29 20:03:28 jak-t14-g3 kernel: PM: suspend exit
Nov 29 20:03:28 jak-t14-g3 kernel: ath11k_pci :02:00.0: BAR 0: assigned
[mem 0x8000-0x801f 64
Dear kernel bot, this bug has enough info, and there's a patch upstream
that's part of 6.1 that fixes the issue.
Though I can say I now hit a failure to restart the device / load
firmware after a 2nd resume.
This is likely another race; if you just suspend by echo mem >
/sys/power/state in a loop
@Craig The limit in Debian is actually much lower than in Ubuntu even,
but fixing it there is even harder as that misses a lot more patches.
--
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/1
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
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
** 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
** Changed in: grub2-unsigned (Ubuntu)
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
** Tags added: fr-2934
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status
Really the workaround is to set MODULES=dep in /etc/initramfs-
tools/initramfs.conf, this yields a much smaller initramfs (but you
can't take out the disk and boot it in another machine), disabling
secure boot or sgx should not be doing anything.
** Also affects: grub2-unsigned (Ubuntu)
Importa
** Tags removed: foundations-triage-discuss
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513
Title:
apt will not instal
It does yeah, and obviously that's a solver bug that's going to need
some more work to root cause.
** Changed in: apt (Ubuntu)
Status: Incomplete => Triaged
** Changed in: apt (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of K
** Changed in: grub2-signed (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1991676
Title:
Package grub-efi-arm64-signed 1.173.2~18.04.1+2.0
On my kinetic system, /dev has nosuid, but no noexec.
** Tags added: foundations-triage-discuss
--
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/1991975
Title:
dev file system is mounted
Is there anything left to do here?
** Changed in: klibc (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: klibc (Ubuntu Cosmic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
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-
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
@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
We believe the kernel handles RAs itself, adding a task for it.
** Also affects: linux (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/1
** Package changed: dpkg (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/1984203
Title:
/var/run/reboot-required not created after installing new kernel
Status
Yes, grub will be fixed eventually, but we are blocked by the security
update not being out yet. This is not a blocker for enabling upgrades to
22.04.1, as it only affects a small number of systems and grub fixes
itself by using the previous kernel version if the new one fails.
--
You received th
*** 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
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
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
1 - 100 of 327 matches
Mail list logo
