=== Feature test ===
On a unit with Lunar Lake CPU (202412-36119) where "Unsupported
condition 59 (UNKNOWN)" and "Unsupported condition 60 (UNKNOWN)" appears
in thermald 2.5.6-2ubuntu0.24.04.1, the message does not appear in
2.5.6-2ubuntu0.24.04.2
On a unit with Meteor Lake CPU (202404-33961), th
** Tags removed: verification-needed-noble-linux-oem-6.11
** Tags added: verification-done-noble-linux-oem-6.11
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2095287
Title:
Ena
Public bug reported:
Ongoing packaging developments for the noble tegra kernels.
** Affects: linux-nvidia-tegra (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-nvidia-tegra (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-nvidia-te
linux (6.8.0-53.55) noble; urgency=medium
* Noble update: upstream stable patchset 2024-11-29 (LP: #2089884)
- Revert "ALSA: hda: Conditionally use snooping for AMD HDMI"
-- Mehmet Basaran Fri, 17 Jan 2025
15:05:44 +0300
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Rele
Hello Mutamammil, thank you for reporting this issue.
Looking back, is there a time when the issue did not happen? Was there a
specific update which seemed to cause the behavior? I'm trying to
establish a starting point that will help in debugging.
In running a quick search, it seems that there a
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 2097710
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a commen
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856361/+files/RfKill.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/2097710
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856365/+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
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856362/+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/2097710
Commits are at the tip of the release. Will be further tested by
Microsoft prior to stakeholder-signoff.
** Changed in: linux-azure (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Tags removed: verification-needed-jammy-linux-azure
** Tags added: verification-done-jammy-linux-azure
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856368/+files/Lspci-vt.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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856357/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856376/+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: "acpidump.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856363/+files/acpidump.txt
** Description changed:
I just downloaded and installed last version of Linux Mint 22.1
And it flickers randomly - but regularly - as mentioned for in
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856379/+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/2097710
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856355/+files/PaInfo.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/2097710
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856378/+files/RfKill.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/2097710
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856380/+files/WifiSyslog.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/bug
OK it's done
I apologize. You should have received 2 reports. The first one was not
done with administrator privileges the second one yes.
Thank you
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856364/+files/AlsaInfo.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: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856370/+files/Lsusb-t.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/2097
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856371/+files/Lsusb-v.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/2097
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856373/+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/2097710/+attachment/5856359/+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-vt.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856351/+files/Lspci-vt.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: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856372/+files/PaInfo.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/2097710
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856366/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856352/+files/Lsusb.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/2097710
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856348/+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
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856353/+files/Lsusb-t.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/2097
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856354/+files/Lsusb-v.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/2097
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856367/+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/2097710
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856374/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856375/+files/ProcEnviron.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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856358/+files/ProcEnviron.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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856356/+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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856349/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856350/+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/2097710
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856369/+files/Lsusb.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/2097710
Hello Donovan, thank you for reporting this issue and for helping to
improve Ubuntu.
Per the wiki, let's see if we can determine whether this is a kernel bug
or an xorg bug. Could you please attach the output of running the
following command from a terminal window:
$ cat /proc/bus/input/devices
https://gitlab.freedesktop.org/agd5f/linux/-/commit/9b908d788090911d339a217c015e0022e8020b75
--
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/2094986
Title:
randomly graphic glitch on some
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856360/+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
Hi Angelo, thank you for reporting this issue.
Looking back, is there a point in time when you did not experience the
system halts? Is it possible to identify a kernel version where this
didn't happen? I'm hoping to establish a starting point for debugging
when the behavior was introduced.
Also,
** Changed in: linux (Ubuntu)
Importance: Undecided => 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/2097693
Title:
Occasional crashes referencing btcoexist
Status in linux p
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856377/+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
I just want to add that, contrary to other reports, it happens wherever
the mouse is, and even if it does not move...
--
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/2097710
Title:
Same f
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2097710/+attachment/5856381/+files/acpidump.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
Public bug reported:
SRU Justification:
[Impact]
Google has requested these upstream commits be applied in order to fix
bugs preventing the boot of 5.15 kernel instances on their Intel TDX
enabled infrastructure.
These patches aim to resolve problems with incorrect assessment of the
CPU's addre
Same bug appears when attempting to boot the generic Jammy kernel on a
TDX-enabled host, so I'll send a patchset to the mailing list for
generic and gcp separately for the purpose of getting it into the gcp
kernels this cycle and the generic kernels next cycle (since the patch
window's already clos
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
This bug was fixed in the package linux - 6.8.0-53.55
---
linux (6.8.0-53.55) noble; urgency=medium
* noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)
* Packaging resync (LP: #1786013)
- [Packaging] debian.master/dkms-versions -- update from kernel-versions
(ma
Can confirm Nvidia 570 works also with the new kernel 6.12.0-15.15 on
both affected systems.
--
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/2096642
Title:
No outputs detected on Nvidia 5
apport information
** Tags added: apport-collected xia
** Description changed:
I just downloaded and installed last version of Linux Mint 22.1
And it flickers randomly - but regularly - as mentioned for instance in
bug report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951
Hi Bin,
Update my experiments as follows:
#1 if firstly installed ubuntu 24.04.1 which version default kernel is 6.8.0-52
and works normally.
#2 if firstly installed ubuntu 22.04.1 which version default kernel is 5.15, by
upgrade, commands as follows:
$ sudo apt update
$ sudo apt dist-upgrade
ke
** Changed in: linux-nvidia-6.8 (Ubuntu Jammy)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2093957
Title:
Enable Coresight in Perf
St
Thanks.
It's hard to tell because I did not report this immediately and over
time have been trying to figure out if it had something to do with a
wireless driver I could replace. But I started noting this problem
shortly after upgrading from the last LTS release to 24.04
Yes, I can definitely in
Hello Morozov, I'm sorry but the build is failing in a 3rd-party dkms
driver that Ubuntu doesn't natively support. I'm afraid we cannot assist
you in debugging this failure.
The problem seems to be that your kernel (version 6.8.0-52-generic) has
been updated such that the rtl8821CU driver (version
You have been subscribed to a public bug:
Testing ISO dated Feb 7
Live session starts with wrong resolution 1024x768 instead 1920x1080
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: gnome-shell 47.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 6.12.0-12.12-generic 6.12.4
Uname: Linux 6.12.0-12-
thanks for your help, but unfortunately the problem won't fix after tried
some of the solution you've suggest. i hope there is a way to fix this and
also i can install packages with apt normally
Pada Sel, 11 Feb 2025 pukul 07.05 Tim Whisonant <2097...@bugs.launchpad.net>
menulis:
> Hello Mutamamm
Hello, thank you for reporting this issue and for helping to improve
Ubuntu.
I see that the commit in question 18676c6 has landed upstream at
v6.11-rc1~151^2~12 and that it should be available via our normal update
rollouts to Oracular. Because this bug is not critical to fix, I'm not
sure that we
Hello astroscion, thank you for filing this issue and for helping to
improve Ubuntu.
To help further debug the issue, could you please run the following
command from a terminal window on the affected system with the 6.8.0-53
kernel:
$ apport-collect 2097801
This will collect data about your hard
6.11.0-17.17, which is currently in 24.10/Oracular proposed repo, has
the same fix. For some reason, Launchpad requires you to have privileges
to open a release-specific task for a bug, or I would have done that to
make it clearer.
--
You received this bug notification because you are a member of
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Live session starts w wrong resolution 1024x768 instead 1920x1080
+ i915 not loaded in live session wi
This bug still exists in 24.04 LTS. Tested today with all updates.
** Attachment added: "Ubuntu sets device read-only no matter what"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/719013/+attachment/5856313/+files/Screenshot%20from%202025-02-10%2015-39-43.png
--
You received this bug
** Bug watch added: Debian Bug tracker #100
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=100
** Also affects: pulseaudio (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=100
Importance: Unknown
Status: Unknown
** Package changed: alsa-lib (Ubuntu) =>
Will the kernel that comes with 24.04.2 resolve the issue? I understand
that the commands I provided above are not a solution, but I've been
enjoying my Ubuntu media center since I run them. Of course, they only
have mini dp to HDMI.
--
You received this bug notification because you are a member
Even added myself to floppy group and it made no difference. Format
fails due to read-only but disk does not have READ-ONLY tab slid to that
position.
** Attachment added: "format fails due to read only"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/719013/+attachment/5856314/+files/Scr
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => New
--
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/2094795
Title:
Kernel 6.11 on Oracular Oriole incompatible with ZFS
Public bug reported:
After updating the Linux kernel image to 6.8.0-53 (Ubuntu 24.04) from
6.8.0-52, Network Manager, Bluetooth, and other services no longer load
at startup and disappear from the menu.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/2093390
Is this a new installation? Are you booting from an ISO? Did this work
in the past? Did it break after an upgrade? You need to provide more
details if you want us to help.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a memb
*** This bug is a duplicate of bug 2073399 ***
https://bugs.launchpad.net/bugs/2073399
User aborted the removal of the running kernel. This should not trigger
a bug report.
** This bug has been marked a duplicate of bug 2073399
Aborting the removal of the running kernel triggers apport
-
I've figured out this issue by disabling fast start in windows 11.
--
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/2062972
Title:
ntfs partition does not mount with linux 6.8 and
CONFIG
*** This bug is a duplicate of bug 2068107 ***
https://bugs.launchpad.net/bugs/2068107
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2068107, so it is being marked as such. Please look
*** This bug is a duplicate of bug 2073399 ***
https://bugs.launchpad.net/bugs/2073399
User aborted the removal of the running kernel. This should not trigger
a bug report.
** This bug has been marked a duplicate of bug 2073399
Aborting the removal of the running kernel triggers apport
--
That missing firmware hasn't been released by the vendor, so there's
nothing we can do.
** Changed in: linux-firmware (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https
*** This bug is a duplicate of bug 2068107 ***
https://bugs.launchpad.net/bugs/2068107
Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.8.0-52-generic -C /lib/modules/6.8.0-52-generic/build
M=/var/lib/dkms/facetimehd/0.1/build...(bad exit status: 2)
ERROR: Cannot create report
6.12.0-15.15 has now landed in plucky release with nvidia 570.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/209
*** This bug is a duplicate of bug 2068107 ***
https://bugs.launchpad.net/bugs/2068107
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2068107, so it is being marked as such. Please look
*** This bug is a duplicate of bug 2068107 ***
https://bugs.launchpad.net/bugs/2068107
** This bug has been marked a duplicate of bug 2068107
package linux-headers- failed to install/upgrade:
installed linux-headers- package post-installation script subprocess
returned error exit status
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
This bug was fixed in the package linux-xilinx - 6.8.0-1012.13
---
linux-xilinx (6.8.0-1012.13) noble; urgency=medium
* noble/linux-xilinx: 6.8.0-1012.13 -proposed tracker (LP: #2094997)
* linux-xilinx: add dwarfdump package in the Build-Depends (LP: #2095556)
- [Packaging] A
Removing from the 24.04.2 since this will likely not making it in time,
and creating noise in the release process. Feel free to target that to
another milestone later (.3 when created).
** Changed in: linux-firmware (Ubuntu Noble)
Milestone: ubuntu-24.04.2 => None
--
You received this bug no
This bug was fixed in the package linux-meta-xilinx - 6.8.0.1012.13
---
linux-meta-xilinx (6.8.0.1012.13) noble; urgency=medium
* Bump ABI 6.8.0-1012
* n:linux-meta-xilinx: migrate linux-xilinx-zynqmp package to linux-xilinx
(LP: #2095151)
- [Packaging] Add transitional p
This bug was fixed in the package linux-xilinx - 6.8.0-1012.13
---
linux-xilinx (6.8.0-1012.13) noble; urgency=medium
* noble/linux-xilinx: 6.8.0-1012.13 -proposed tracker (LP: #2094997)
* linux-xilinx: add dwarfdump package in the Build-Depends (LP: #2095556)
- [Packaging] A
Re-tagging, as this is actually being handled today by the kernel team.
** Changed in: linux-firmware (Ubuntu Noble)
Milestone: None => ubuntu-24.04.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Public bug reported:
I'm trying to upgrade my kernel via apt, but it can't build. Some errors
referrers to Realteck Network drivers. If it needed I can upload logs of
make build
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-52-generic 6.8.0-52.53
ProcVersionSignatu
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.9
---
linux-firmware (20240318.git3b128b60-0ubuntu2.9) noble; urgency=medium
* Add firmware for 6.11 HWE kernel (LP: #2097240)
- ath10k: WCN3990: hw1.0: move firmware back from qcom/ location
-
Yup, I had already done that «grub-edit», and I do not need any power
saving on this system, so for me the workaround should be fine - let me
run it for a few days to make sure. :-)
This is still an issue that should be forwarded / handled, since others
might simply find a freezing system, and wit
1 - 100 of 122 matches
Mail list logo
