The verification also needs to be re-done, "unblocking proposed since
the fix is in proposed" is not an acceptable way to verify that the bug
is fixed. It needs to include which version was tested and that the
test plan was being followed.
--
You received this bug notification because you are a
This is blocked by bug 2094190; the verification here is also missing
the version number but oh well, I wouldn't necessarily require re-
verification.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.l
This is still blocked by various regressions in jammy that need to be
sorted out.
Regression in autopkgtest for linux-aws-6.8 (arm64): test log
Regression in autopkgtest for linux-azure-6.5 (arm64): test log
Regression in autopkgtest for linux-gcp-6.5 (arm64): test log
Regression in autopkgtest fo
** Tags removed: rls-pp-incoming
--
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/2102236
Title:
plucky/s390x does not come up after kernel update + reboot, due to
udev rules missing in
I'd appreciate someone doing an end-to-end test of the package in
https://code.launchpad.net/~ubuntu-core-dev/+git/boot-managed-by-
snapd/+merge/482761
that is, build it and install it in a hybrid FDE system, then upgrade
wireless-regdb. Ta!
--
You received this bug notification because you are
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
** 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
** 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
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
Diverting directories does not work of course, but we can divert the
files...
root@p:~# apt install wireless-regdb
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
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
** 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
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 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
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
** 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
** Attachment added: "/proc/version_signature"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707486/+files/version.log
** Attachment removed: "cat /proc/version_signature"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038685/+attachment/5707462/+files/ve
why it says that as this is a Ubuntu VM downloaded from the Ubuntu site,
upgraded by doing `pro attach` and then updated to the latest ESM kernel.
- ---
- ProblemType: Bug
- ApportVersion: 2.20.9-0ubuntu7.29
- Architecture: amd64
- AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /d
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2038685/+attachment/5707484/+files/UdevDb.txt
--
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/2038685
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/2038685/+attachment/5707483/+files/PulseList.txt
--
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/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2038685/+attachment/5707482/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2038685/+attachment/5707480/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2038685/+attachment/5707479/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2038685/+attachment/5707481/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2038685/+attachment/5707478/+files/Lspci.txt
--
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/2038685
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2038685/+attachment/5707477/+files/IwConfig.txt
--
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
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2038685/+attachment/5707476/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
test ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installe
Ubuntu site,
upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pulseaudio
Cur
aded from the Ubuntu site,
upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pulseaudio
Cur
aded from the Ubuntu site,
upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pulseaudio
Cur
ownloaded from the Ubuntu site,
upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pu
D ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2021-05-18 (870 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64
(20200806.1)
Lsusb:
tu VM downloaded from the Ubuntu site,
upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pu
aded from the Ubuntu site,
upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pulseaudio
Cur
Ubuntu site,
upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pulseaudio
Cur
aded from the Ubuntu site,
upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pulseaudio
Cur
aded from the Ubuntu site,
upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pu
Ubuntu site,
upgraded by doing `pro attach` and then updated to the latest ESM kernel.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.29
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andres 3050 F pulseaudio
Cur
/dev/snd/controlC0: andres 3050 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2021-05-18 (870 days ago)
+ InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64
(20200806.1)
+ Lsusb:
+ Bus 001
Public bug reported:
This is a follow-up from: https://discourse.ubuntu.com/t/ask-us-
anything-about-ubuntu-kernels/27664/142
Older Ubuntu distributions come with a kernel image that support eBPF
but are not built with a BTF file published (/sys/kernel/btf/vmlinux).
This BTF file is crucial when
** 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
1 - 100 of 482 matches
Mail list logo
