https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=7be6ce7043b4cf293c8826a48fd9f56931cef2cf
DOes not seem to have been upstream tagged for stable updates, hence manual
submission needed.
--
You received this bug notification because you are a member of Kernel
Packages
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: linux (U
You have been subscribed to a public bug:
== Comment: #0 - SEETEENA THOUFEEK - 2024-08-06 00:20:57
==
+++ This bug was initially created as a clone of Bug #206372 +++
---Problem Description---
L2 Guest hung during LTP Tests. Back trace of paca->saved_r1
(0xc00c1bc8bb00) (possibly stale) @
Hi
A new bug was filed in upstream kernel bug at
https://bugzilla.kernel.org/show_bug.cgi?id=219128
** Bug watch added: Linux Kernel Bug Tracker #219128
https://bugzilla.kernel.org/show_bug.cgi?id=219128
--
You received this bug notification because you are a member of Kernel
Packages, which
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-August/152623.html
(unstable, oracular)
* https://lists.ubuntu.com/archives/kernel-team/2024-August/152626.html (noble)
* https://kernel.ubuntu.com/gitea/kernel/noble-linux-oem/pulls/20 (oem-6.10)
* https://kernel.ubuntu.com/gitea/kernel/no
** Package changed: mutter (Ubuntu) => linux (Ubuntu)
** Tags added: noble
--
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/2076109
Title:
Audio randomly cuts out via hdmi with external m
You have been subscribed to a public bug:
Background audio coming from browsers (firefox, opera, etc...) or vlc,
the audio cuts out randomly as if there was a lag. This only happens
with audio via hdmi, the integrated audio of the laptop (ASUS K550J)
works very smoothly and correctly.
The error p
** Description changed:
+ [SRU Justification]
+
[Impact]
+
+ Power consumption measurements are worse than Windows while using HW
+ accelerated video decoding.
+
[Fix]
+
+ Two commits from upstream v6.11-rc1 to add a unified queue to VCN for
+ more power saving.
+
[Test Case]
+
+ This
** Description changed:
+ [Impact]
+ [Fix]
+ [Test Case]
+ [Where problems could occur]
+ [Other Info]
+
+ = original bug report =
+
Affected platforms are AMD Phoenix, Phoenix2, Kracken, Strix and Strix-
Halo.
Patches being upstreamed:
* https://lore.kernel.org/all/2024071020
** Changed in: linux-oem-6.8 (Ubuntu Noble)
Importance: Undecided => High
** Changed in: linux-oem-6.8 (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux-oem-6.8 (Ubuntu Noble)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-oem-6.10 (Ubuntu Nobl
I don't have a better idea about this, it looks like it's a h/w issue to me.
The GPE17 is triggerred by EC, so I can't figure out a proper fix for this
issue.
The feasible workaround would be ignore it by adding below line to the kernel
cmdline
acpi_mask_gpe=0x17
There is no updated BIOS to
Can we get this patch or some variation on it committed? The regression
is affecting many Debian autopkgtest runs.
--
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/2056461
Title:
autopkgte
Same here. Freeze after resume on my Lenovo ThinkPad T14 Gen 3, model
21CFCTO1WW.
Additionally, with this 6.8.0-x kernel, I can no longer boot without my LID
open and just use the docking station monitors. It boots, docking station is
working (both displays are working) - I can enter my decrypti
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
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/2071471
Title:
[UBUNTU 24.04] IOMMU DMA mode
This bug is awaiting verification that the linux-oem-6.10/6.10.0-1006.6
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.10' to 'verification-done-
noble-linux-oem-6.1
Syslog shows a bunch of these repeated with the -40 kernel:
kernel: [ 21.617137] nvidia: disagrees about version of symbol sme_me_mask
kernel: [ 21.617149] nvidia: Unknown symbol sme_me_mask (err -22)
kernel: [ 21.617213] nvidia: disagrees about version of symbol
acpi_walk_namespace
kernel:
I can happily report that installing 5.15.0-117-generic
#127+TEST2073267v20240731b1-Ubuntu from the PPA cited in comment #74
here allows VirtualBox 6.1.50-dfsg-1~ubuntu1.22.04.1 to run VMs just
fine on my test Jammy system!
--
You received this bug notification because you are a member of Kernel
Dear,
this working arround change nothing - equal shift key cant been used to
come in the boot menu!
Equal many other users has the same problem many years. So, why not change
this to an other resolution?
b, for grub issue, please change grub setting like:
https://askubuntu.com/questions/16042/ho
After upgrading to Ubuntu 24.04 LTS on the Vivobook Go, the problem with
the messed up display seem to be solved. Abount 24 hours experience so
far is a lot better than before the upgrade.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
This problem does not seem to exist with the latest mainline kernel
(6.10.3-061003-generic).
--
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/2076048
Title:
My system freezes after waking
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Changed in: linux-xilinx-zynqmp (Ubuntu Noble)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu.
https://bugs.launchpad.net/bugs/2072456
Title:
boot failure on kv
It’s a visualized tool for installing Ubuntu maintained mainline kernel.
sudo add-apt-repository ppa:cappelikan/ppa
sudo apt update
sudo apt install mainline
Please try the kernel version >= 6.9 and see if it works or not
--
You received this bug notification because you are a member of Kernel
*** This bug is a duplicate of bug 2076004 ***
https://bugs.launchpad.net/bugs/2076004
** This bug has been marked a duplicate of bug 2076004
Shows Unknown display with 6.8.0-39
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Seems the fix in now on the current kernel source
https://github.com/torvalds/linux/blob/master/drivers/media/usb/uvc/uvc_driver.c
--
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/2000947
Ti
This issue was reported publicly to https://lore.kernel.org/linux-
wireless/caov16xesck0-smenjfxvwikqogbj4pqwa2dvjbvwq-g+ntv...@mail.gmail.com/T/#u
Therefore, I am making this bug report public as well.
The new report claims that "Debian systems are not affected.".
If Ubuntu is truly the only di
@mapengyu
Thanks you for the advice.
I "installed" the latest firmware/ddc images from the linux-firware git and
they are very different from the ones in
linux-firmware-20240318.git3b128b60-0ubuntu2.1. Uncompressed binary diff is
~1KBytes for .sfi and 1 Byte for ddc.
The firmware works and dev
** Package changed: 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/2076048
Title:
My system freezes after waking from suspend
Status in linux package in Ubuntu:
Public bug reported:
Using softwares like Blender (UPBGE) or dbeaver makes Ubuntu randomly crash.
No pattern found until now.
If I'm editing preferences in dbeaver (no connection active) or if I
close a closing, the Ubuntu crashes.
Same thing with blender (UPBGE). If I'm editing somethin in the
https://erudit.kz/probnyy-ent
https://erudit.kz/podgotovka-k-ent
https://erudit.kz
--
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/1833281
Title:
System freeze when memory is put on SWAP
I'm wondering if it keeps reverting to a less than ideal display mode.
Xrandr.txt says the preferred mode is 59.85Hz, but monitors.xml has
stored 59.883. Does the monitor have a menu in which you
can find out the current refresh rate?
Also please look in Settings > Displays and check if you get an
Yeah - I'm still around.
These days, its become cheap enough to just have more RAM - so to be
honest, I haven't seen an issue like this again in a number of years -
but now I don't bother with less than 32Gb of RAM for a desktop.
Likely, this has just become obsolete now - so closing as such.
--
@mruffell
Thanks for re-verified my comment in #65 and provide the test kernel.
The solutions are under Kernel team's discussion.
Reverting is an option, but not the best. Actually, it's not a kernel
issue.
We are still working on it. Please wait a moment.
If you have more insight in virtualbo
The issue does not happen on GNOME but libinput still shows the KEY_MUTE
being sent from both devices. Currently working on dynamic debug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/b
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux-azure (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
hey mruffell, smb:
This got pulled into Jammy's proposed HWE kernel but I don't see the
kernel bot mentioning the Noble version yet; is that going into proposed
there or is it following a different path?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-az
** Changed in: linux-hwe-6.8 (Ubuntu)
Status: New => Invalid
** Changed in: linux-hwe-6.8 (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-hwe-6.8 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
**
As seen in the modified description, we have decided to revert the commit
"randomize_kstack: Improve entropy diffusion" for now. The updated kernel
should be available in ~2 weeks.
This is against our policy, differing from upstream makes the maintenance of
kernels harder, but the fix from virtu
There are some kernels need you to try
6.8.0-40 has been landed in -proposed, compares with 6.8.0-31 it
includes many stable updates from 6.8.2 to 6.8.12. The issue may has
been fixed by one of the updates.
It the -proposed kernel doesn't help, I'm wondering if the issue has been fix
by the upst
All autopkgtests for the newly accepted linux-meta-azure-5.15
(5.15.0.1070.79~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/245.4-4ubuntu3.23 (arm64)
wireguard-linux-compat/unknown (arm64)
Please visit the excus
** Changed in: ubuntu-drivers-common (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nv
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: debian-installer (Ubuntu Artful)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux-firmware (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
The packaging of libnvidia-compute-515 seems wrong. There's a top level
/NVIDIA-Linux directory with a single library in it.
root@nvidiatest:~# find / -name 'libnvidia-nvvm*' -ls
22924474 4 lrwxrwxrwx 1 root root 19 Mar 27 2023
/usr/lib/x86_64-linux-gn
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux-firmware (Ubuntu Artful)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
@Dominique, any news on this? (For those among us that don't monitor the
mailing lists)
Happy to run further tests, if needed.
--
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/2056461
Title
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: elasticsearch (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
** Changed in: linux (Ubuntu Oracular)
Status: In Progress => Fix Committed
--
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/2074376
Title:
Disable PCI_DYNAMIC_OF_NODES in Ubuntu
S
@Maksim, gentle ping. Could u try my new bisect version in
https://people.canonical.com/~mschiu77/lp2039970/bisect9/?
--
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/2039970
Title:
Kernel
En-Wei,
First, I dropped to root
$ sudo su -
I was unable to echo to /sys/kernel/debug
# echo 'file ucsi.c +p' > /sys/kernel/debug/dynamic_debug/control
-bash: /sys/kernel/debug/dynamic_debug/control: Operation not permitted
so I tried /proc instead:
# cat /proc/dynamic_debug/control|egrep uc
You have been subscribed to a public bug:
== Comment: #0 - Kowshik Jois B S - 2024-05-28
01:07:02 ==
---Problem Description---
While trying virsh attach-interface and virsh detach-interface, It is observed
that, attaching an interface is successful. But trying to detach the same
results in the
*** This bug is a duplicate of bug 2074376 ***
https://bugs.launchpad.net/bugs/2074376
I just noticed that the Canonical kernel team has already a Launchpad bug open
on this and already started to work on it (it's meanwhile Fix Committed for
noble/24.04 and oracular/24.10).
So I'm marking th
** Description changed:
SRU Justification:
[ Impact ]
- * The CPU Measurement Facility (CPU MF) crypto counter set
-is not listed in the device sysfs tree - it's not exported
-in the sysfs directory /sys/devices/cpum_cf/events.
+ * The CPU Measurement Facility (CPU MF) crypto c
Anyone knows if the latest OEM kernel updates have fixed this issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2069357
Title:
Multimonitor support broken on kernel 6.5.0-102
The issue is with the speaker mute key, by the way. Mic mute works fine and
always has (for some reason, probably not sent by the keyboard and only by wmi).
I will see about reporting this to plasma's bug tracker. Thank you for your help
--
You received this bug notification because you are a me
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073049
Title:
No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
Status in l
Hi everyone,
I see that Greg KH just assigned CVE-2024-35918 to "randomize_kstack:
Improve entropy diffusion".
I suppose that means that we cannot revert it now.
https://lore.kernel.org/linux-cve-announce/2024073029-clerk-
trophy-b84c@gregkh/T/
This is going to take some time.
Thanks,
Matthew
Hi Chris,
Yes, jammy-hwe-6.8 got fixed because Stefan Bader had to respin the kernel
for another regression anyway, so he opportunistically pulled it in.
For Noble, I think it will be part of the s2024.07.08 SRU cycle, as per
https://kernel.ubuntu.com/, as Manuel Diewald mentioned when I spoke to
Hi David,
Yes, it does indeed seem that the CVE has now been rejected.
https://lore.kernel.org/linux-cve-announce/2024073029-clerk-
trophy-b84c@gregkh/
https://nvd.nist.gov/vuln/detail/CVE-2024-35918
https://www.cve.org/CVERecord/?id=CVE-2024-35918
Maybe we can revert it after all!
I will have
The commit applies fine to the noble master-next tree (kernel 6.8),
and a test build was triggered here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2074380
However, the cpumf code in jammy master-next (kernel 5.15) is quite different.
git blame tells me that probably the following commits a
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2065128
Title:
rtw89_8852ce - Lost WI
Public bug reported:
I haven't the slightest.
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-36-generic (not installed)
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_6_8_0_31_31_generic_1
Hello Simon, or anyone else affected,
Accepted zfs-linux into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.3-1ubuntu12.18 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
ht
Hello Heinrich, or anyone else affected,
Accepted zfs-linux into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.3-1ubuntu12.18 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Package changed: ubuntu => linux
** Project changed: linux => 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/2075721
Title:
[Ubuntu24.04] virsh detach-interface is cra
Workaround:
1. change the driver in the Driver Manager to another driver, in my case it was
from Nvidia 353 to Open Source.
2. restart
3. switch back to the recommended Nvidia driver
4. disconnect all monitors (cables)
5. restart
And it works again as usual. I then had to switch from Intel proce
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu Noble)
Status: New => 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/2061373
Title:
To future readers: if you're still seeing this, make sure you have the
file `/sys/kernel/mm/lru_gen/enabled` and its value is `0x0007` (it's
just the one I tested). AFAIK kernel doesn't enable MLRU by default; but
at the same time AFAIK all major distros enable it in their kernels.
--
You receive
[ 982.785552] dell_wmi: Received WMI event (02 00 10 00 50 01 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00)
[ 982.785558] dell_wmi: Process buffer (02 00 10 00 50 01
AceLan Kao,
First, I downloaded the image and modules:
$ wget
https://kernel.ubuntu.com/mainline/v6.11-rc1/amd64/linux-image-unsigned-6.11.0-061100rc1-generic_6.11.0-061100rc1.202407281809_amd64.deb
$ wget
https://kernel.ubuntu.com/mainline/v6.11-rc1/amd64/linux-modules-6.11.0-061100rc1-generic
The trigger may be when a) the screen is locked, and b) the screen
blacks out. Logging back in after this leads to the flickering black
rectangle at the top of the secondary monitor. This occurs without any
use of SDL.
Switching the monitor off and on does not fix the problem. Disconnecting
and re
This does not sound like a systemd bug, but more like kernel or the
nouveau driver. From the attached CurrentDmesg.txt:
[ 248.207134] nouveau :01:00.0: Enabling HDA controller
[ 248.310486] [ cut here ]
[ 248.310488] WARNING: CPU: 0 PID: 1530 at kernel/workqueue.c:17
Public bug reported:
We have a repeating (every few hours) kernel OOPS:
BUG: kernel NULL pointer dereference, address: 00a0.
This repeats on several different hardwares so this is not a hardware
issue.
Attached as a file are 5 dmesg logs and kdump reports.
[ 6315.768576] [ T52862]
This bug is awaiting verification that the linux-oem-6.10/6.10.0-1006.6
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.10' to 'verification-done-
noble-linux-oem-6.1
(In reply to Steven Haigh from comment #74)
> These days, its become cheap enough to just have more RAM - so to be honest,
> I haven't seen an issue like this again in a number of years - but now I
> don't bother with less than 32Gb of RAM for a desktop.
>
> Likely, this has just become obsolete n
All autopkgtests for the newly accepted linux-meta-hwe-6.8
(6.8.0-40.40~22.04.2) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
backport-iwlwifi-dkms/unknown (armhf)
dpdk-kmods/unknown (arm64)
fwts/unknown (armhf)
glibc/2.35-0ubunt
** Changed in: ubuntu-drivers-common (Ubuntu Noble)
Status: Triaged => In Progress
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: nvidia-gr
AceLan Kao,
First, I added "noble-proposed" to /etc/apt/sources.list.d/ubuntu.sources:
$ sudo sed -i '/^Suites/ s/$/ noble-proposed/'
/etc/apt/sources.list.d/ubuntu.sources
then I ran, apt update:
$ sudo apt update
Then I was able to install the 6.8.0-40 kernel:
$ sudo apt instal
Public bug reported:
Commit 3bd786f76de2 ("mm: convert do_set_pte() to set_pte_range()")
replaced do_set_pte() with set_pte_range() and that introduced a
regression in the following faulting path of non-anonymous vmas which
caused the PTE for the faulting address to be marked as old instead of
you
This Virtualbox ticket contains a diff that looks like it might be the change
they did to fix compatibility with RANDOMIZE_KSTACK_OFFSET in the 5.13 kernel.
https://www.virtualbox.org/ticket/20456
** Bug watch added: Virtualbox Trac #20456
http://www.virtualbox.org/ticket/20456
--
You receiv
This bug is awaiting verification that the linux-oem-6.10/6.10.0-1006.6
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.10' to 'verification-done-
noble-linux-oem-6.1
This bug is awaiting verification that the linux-oem-6.10/6.10.0-1006.6
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.10' to 'verification-done-
noble-linux-oem-6.1
Hi @Anant,
Could you please run the apport-collect on your 5.15.0-116 kernel? We
need the information of your system when the problem occurred.
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1135.129) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
glibc/2.31-0ubuntu9.16 (arm64)
rtl8821ce/unknown (arm64)
systemd/
Public bug reported:
I have made an update as follows:
https://linuxmint-user-guide.readthedocs.io/en/latest/upgrade-to-mint-22.html
So far it has worked, but now no external monitors are recognized,
whether via HDMI or USB-C. Before the update it worked without any
problems.
In the Display app,
(In reply to Konstantin Kharlamov from comment #70)
> Also, these days the Multi-LRU patchset should pretty much resolve the
> problem. It is not yet upstream, but is used in downstream kernels such as
> linux-zen and liquorix-kernel. There is hope it will be merged by 5.19¹
MLRU patches were merg
** Description changed:
* Explain the bug(s)
We run a simple CPU-only xor application.
int main(void) {
- long i;
- int count = 0;
- for (i=0; i< 100; i++) {
- count = count ^ i;
- }
- return 0;
+ long i;
+ in
** Changed in: linux-nvidia-tegra (Ubuntu)
Status: New => Fix Committed
** Changed in: linux-nvidia-tegra-igx (Ubuntu)
Status: New => Fix Committed
** Changed in: linux-nvidia-tegra (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-nvidia-tegra-igx (Ubuntu Jam
Bug solved on Huawei Matebook D14 AMD, using:
Linux 6.8.0-1010-oem #10-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 25 18:13:14 UTC
2024 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-noble-linux-oem-6.8
** Tags added: verification-done-noble-linux-oem-6.8
--
You received this bug no
** Summary changed:
- Screen Brightness goes to 0 waking from sleep
+ [ThinkPad T495s] Screen Brightness goes to 0 waking from sleep
--
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/2074099
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: ubuntu-drivers-common (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1750047
Hi @Bill,
Sorry for the late reply. It seems like the problem is strongly related to the
error message in comment #3. However, the clue is not that clear. Could you
please try the following steps to help us get more debug info:
1. Blacklist the ucsi_acpi.ko and boot
2. Login as root, then $ echo
Sorry, you'd asked about that, before.
My secondary monitor shows no signal if the resolution is anything but
the maximum, native resolution of the screen.
Changing the refresh rate may temporarily restore drawing to the full
screen. However, locking the screen and then allowing it to sleep will
** Summary changed:
- [nouveau] Top margin of secondary monitor covered with black flickering
rectangle
+ [nouveau][Samsung SyncMaster] Top margin of secondary monitor covered with
black flickering rectangle
--
You received this bug notification because you are a member of Kernel
Packages, whi
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
If you set the monitor to a lower resolution or a different refresh
rate, does it prevent the bug?
--
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/2074559
Title:
[nouveau] Top margin of s
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: glibc (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
1 - 100 of 225 matches
Mail list logo
