** Also affects: linux-hwe-6.8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-6.8 (Ubuntu)
Status: New => Confirmed
** Description changed:
- [ Workaround ]
+ [ Workaround for 24.04 and later ]
- Add to /etc/environment (in Ubuntu 22.04):
+ Add to /etc/en
--
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/2095291
Title:
kernel Patch to Fix Low and Inverted Brightness Value on AMD Devices
Status in linux package in Ubuntu:
Confirmed
Bug des
[Expired for linux-hwe-6.8 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-hwe-6.8 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https
Public bug reported:
I'm trying to copy files from internal filesystems to an external
Samsung SSD T5 EVO. I'm copying a long list of large files. The first
one copies fine. The next one hangs.
If I let it run, files after the first one copy at about 3M/s, which is
extremely slow. The drive i
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/2095291
Public bug reported:
I have a problem on Linux with my "AMD Ryzen 5 5600H with Radeon Graphics"
which is brightness is so low & brightness controls inverted. An important
detail is the backlight is at max brightness during the grub screen and halfway
into the boot process, just around the time
why is the expected result 80%? we have historical data that
consistently demonstrates this the expectation or its some number we
have just decided on? so far this looks to me like a performance
enhancement request which we would not do for a stable kernel,
especially as there is a viable workaro
Public bug reported:
[Impact]
TBT monitors can not reach 4K@60Hz with two 4K@60Hz monitors connected to dock
on Lunar lake platform.
[Fix]
Intel provide a fix for this issue.
73900dce57e4 drm/xe/dp: Enable DP tunneling
[Test]
1. Connect Dell dock to the lunar lake platform.
2. Plug in two/three
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Koichiro Den (koichiro
*** This bug is a duplicate of bug 1968040 ***
https://bugs.launchpad.net/bugs/1968040
Let's group it with bug 1968040 so everyone is part of the same
discussion.
** This bug has been marked a duplicate of bug 1968040
[i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.11 (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: linux
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
** Tags added: jira-wtn-183 oem-priority
** Description changed:
[Impact]
When doing suspend test, the system will fail to be suspended since the
MT7925 controller couldn't be suspended. The root cause is caused by the
command timeout issued from mt7925 driver.
[Fix]
Cherry-pick the
Focal 5.4.0-206.226 was tested using the test plan and confirmed that it
is functioning as expected.
root@focal-iouring:~# uname -a
Linux focal-iouring 5.4.0-206-generic #226-Ubuntu SMP Mon Jan 13 07:29:08 UTC
2025 x86_64 x86_64 x86_64 GNU/Linux
** Tags removed: verification-needed-focal-linux
*
** Also affects: linux-oem-6.11 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.11 (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
S
Public bug reported:
[Impact]
When doing suspend test, the system will fail to be suspended since the MT7925
controller couldn't be suspended. The root cause is caused by the command
timeout issued from mt7925 driver.
[Fix]
Cherry-pick the following two patches from linux-next:
1b97fc8443ae wi
This bug is awaiting verification that the linux-
bluefield/5.15.0-1059.61 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-jammy-linux-bluefield' to
'verification-done-jammy-linux-blue
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oracular)
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:
18 matches
Mail list logo