Yes since you didn't clone using git you can't use git revert.
Once you can successfully build and test that kernel I'll post you a
revert patch' with explanation how to use it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yeah I know they're different symptoms but the reason for that revert might
have a similar root cause.
I'm saying this because I've got a different system that fails to boot up that
reverting that helps.
In terms of specific instructions, I'd start with this:
From: Mario Limonciello
When the "panel power saving" property is set to forbidden the
compositor has indicated that userspace prefers to have color
accuracy and fidelity instead of power saving.
Verify that the sysfs file behaves as expected in this situation.
Signed-off-by: Mario L
From: Mario Limonciello
When the "panel power saving" property is set to forbidden the
compositor has indicated that userspace prefers to have color
accuracy and fidelity instead of power saving.
Verify that the sysfs file behaves as expected in this situation.
Signed-off-by: Mario L
color fidelity.
This set of IGT changes introduces a new subtest that will cover the
expected kernel behavior when switching between Allowed and Forbidden.
Mario Limonciello (2):
tests/amdgpu/amd_abm: Make set_abm_level return type int
tests/amdgpu/amd_abm: Add support for panel_power_savin
color fidelity.
This set of IGT changes introduces a new subtest that will cover the
expected kernel behavior when switching between Allowed and Forbidden.
Mario Limonciello (2):
tests/amdgpu/amd_abm: Make set_abm_level return type int
tests/amdgpu/amd_abm: Add support for panel_power_savin
From: Mario Limonciello
In order to bubble of cases of expeted errors on set_abm_level()
change the return type to int.
Signed-off-by: Mario Limonciello
---
tests/amdgpu/amd_abm.c | 33 +++--
1 file changed, 23 insertions(+), 10 deletions(-)
diff --git a/tests
From: Mario Limonciello
In order to bubble of cases of expeted errors on set_abm_level()
change the return type to int.
Signed-off-by: Mario Limonciello
---
tests/amdgpu/amd_abm.c | 33 +++--
1 file changed, 23 insertions(+), 10 deletions(-)
diff --git a/tests
on
will get an -EBUSY return code.
When the compositor has restored the value back to "Allowed" then the
previous value that would have been programmed will be restored.
Mario Limonciello (2):
drm: Introduce panel_power_saving drm property
drm/amd: Add panel_power_saving drm property
When the `panel_power_saving` property is set to "Forbidden" ABM
should be disabled immediately and any requests by sysfs to update
will return an -EBUSY error.
When the property is restored to "Allowed" the previous value of
ABM will be restored.
Signed-off-by: Mario Limon
The `panel_power_saving` DRM property is an optional property that
can be added to a connector by a driver.
This property is for compositors to indicate intent of allowing
policy for the driver to use power saving features that may
compromise color fidelity.
Signed-off-by: Mario Limonciello
The `panel_power_saving` DRM property is an optional property that
can be added to a connector by a driver.
This property is for compositors to indicate intent of allowing
policy for the driver to use power saving features that may
compromise color fidelity.
Signed-off-by: Mario Limonciello
When the `panel_power_saving` property is set to "Forbidden" ABM
should be disabled immediately and any requests by sysfs to update
will return an -EBUSY error.
When the property is restored to "Allowed" the previous value of
ABM will be restored.
Signed-off-by: Mario Limon
on
will get an -EBUSY return code.
When the compositor has restored the value back to "Allowed" then the
previous value that would have been programmed will be restored.
Mario Limonciello (2):
drm: Introduce panel_power_saving drm property
drm/amd: Add panel_power_saving drm property
Errors in amdgpu_dm_init() are silently ignored and dm_hw_init()
will succeed. However often these are fatal errors and it would
be better to pass them up.
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 6 +-
1 file changed, 5 insertions(+), 1
As a random guess; could this be the same as
https://bugzilla.kernel.org/show_bug.cgi?id=218849?
Try reverting d410ee5109a1 ("ACPICA: avoid "Info: mapping multiple BARs.
Your kernel is fine."")
** Bug watch added: Linux Kernel Bug Tracker #218849
Fixed upstream.
https://github.com/fwupd/fwupd/pull/7264
** Changed in: fwupd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065948
Title:
fwupdmgr
This is the original bug for deb fwupd:
https://github.com/canonical/ubuntu-desktop-installer/issues/2371
This is the original bug for snap fwupd:
https://github.com/fwupd/fwupd/issues/6264
The problem is that fwupd (both deb and snap) don't understand the
layout that TPM FDE uses.
As
It's saying the same thing the GUI does.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942616
Title:
Settings Power says high hardware temperature
To manage notifications about this bug go to:
How about the command line tool (powerprofilesctl)? Can you switch
using that? If it really is a pure GCC bug then you can file it here:
https://launchpad.net/ubuntu/+source/gnome-control-center for Ubuntu and
here: https://gitlab.gnome.org/GNOME/gnome-control-center for upstream.
--
You
You can file it here:
https://bugzilla.kernel.org/
Mention your reproduction using a mainline kernel and add your logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942616
Title:
Settings Power
This sure sounds like an intel-pstate bug. If you can reproduce it with
the latest mainline kernel you should file a bug with the intel-pstate
maintainers.
You can find some kernel binaries for mainline kernel here:
https://kernel.ubuntu.com/mainline/
--
You received this bug notification
On 5/9/2024 16:50, Pratap Nirujogi wrote:
Add the isp driver in amdgpu to support ISP device on the APUs that
supports ISP IP block. ISP hw block is used for camera front-end, pre
and post processing operations.
Signed-off-by: Pratap Nirujogi
Reviewed-by: Mario Limonciello
---
Changes made
On 5/9/2024 14:35, Pratap Nirujogi wrote:
Enable ISP for ISP V4.1.0 and V4.1.1 in amdgpu_discovery.
Signed-off-by: Pratap Nirujogi
Reviewed-by: Mario Limonciello
---
drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c | 22 +++
1 file changed, 22 insertions(+)
diff --git
On 5/9/2024 14:35, Pratap Nirujogi wrote:
ISP hw block is supported in some of the AMD GPU versions, add support
to discover ISP IP in amdgpu_discovery.
Signed-off-by: Pratap Nirujogi
Reviewed-by: Mario Limonciello
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 +
drivers/gpu/drm
On 5/9/2024 14:35, Pratap Nirujogi wrote:
Add the isp driver in amdgpu to support ISP device on the APUs that
supports ISP IP block. ISP hw block is used for camera front-end, pre
and post processing operations.
Signed-off-by: Pratap Nirujogi
Change-Id:
On 5/9/2024 07:43, Linux regression tracking (Thorsten Leemhuis) wrote:
On 18.04.24 21:43, Harry Wentland wrote:
On 2024-03-07 01:29, Wayne Lin wrote:
[Why]
Commit:
- commit 5aa1dfcdf0a4 ("drm/mst: Refactor the flow for payload
allocation/removement")
accidently overwrite the commit
- commit
On 5/9/2024 07:43, Linux regression tracking (Thorsten Leemhuis) wrote:
On 18.04.24 21:43, Harry Wentland wrote:
On 2024-03-07 01:29, Wayne Lin wrote:
[Why]
Commit:
- commit 5aa1dfcdf0a4 ("drm/mst: Refactor the flow for payload
allocation/removement")
accidently overwrite the commit
- commit
On 5/9/2024 07:43, Linux regression tracking (Thorsten Leemhuis) wrote:
On 18.04.24 21:43, Harry Wentland wrote:
On 2024-03-07 01:29, Wayne Lin wrote:
[Why]
Commit:
- commit 5aa1dfcdf0a4 ("drm/mst: Refactor the flow for payload
allocation/removement")
accidently overwrite the commit
- commit
OLED panels don't support the ABM, they shouldn't offer the
panel_power_savings attribute to the user. Check whether aux BL
control support was enabled to decide whether to offer it.
Reported-by: Gergo Koteles
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3359
Signed-off-by: Mario
On 5/8/2024 09:50, Pratap Nirujogi wrote:
Add the isp driver in amdgpu to support ISP device on the APUs that
supports ISP IP block. ISP hw block is used for camera front-end, pre
and post processing operations.
Signed-off-by: Pratap Nirujogi
---
drivers/gpu/drm/amd/amdgpu/Makefile |
The pixel_clock_mhz property is populated in amdgpu_dm when Freesync is setup,
but it is not used anywhere in amdgpu_dm. Remove the dead code.
Cc: chiahsuan.ch...@amd.com
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 3 ---
drivers/gpu/drm/amd/display
orary Disable MST DP Colorspace
Property").
Reported-and-tested-by: Tyler Schneider
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/d
orary Disable MST DP Colorspace
Property").
Reported-and-tested-by: Tyler Schneider
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/d
ses: https://gitlab.freedesktop.org/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
b/drivers/gpu/drm/amd/display
ses: https://gitlab.freedesktop.org/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
b/drivers/gpu/drm/amd/display
/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/drm_mode_object.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_mode_object.c
b/drivers/gpu/drm/drm_mode_object.c
index 0e8355063eee..b077547a2db4 100644
--- a/drivers/gpu/drm
/drm/amd/-/issues/3353
Signed-off-by: Mario Limonciello
---
drivers/gpu/drm/drm_mode_object.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_mode_object.c
b/drivers/gpu/drm/drm_mode_object.c
index 0e8355063eee..b077547a2db4 100644
--- a/drivers/gpu/drm
This is certainly a false negative. This firmware only affects DCN 3.5
which isn't available for arm64 or armhf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063002
Title:
Add support for DCN
I just tested on a Phoenix based laptop and tested video playback on
OEM-6.5 (1022) with VP9 content in mpv and things look good to me.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 2063143 ***
https://bugs.launchpad.net/bugs/2063143
** This bug has been marked a duplicate of bug 2063143
Frequent boot to black display
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 2063143 ***
https://bugs.launchpad.net/bugs/2063143
** This bug is no longer a duplicate of bug 2064815
Always black screen on first reboot after fresh install 24.04, Intel and AMD
GPU
** This bug has been marked a duplicate of bug 2063143
Frequent
The issue here is the same one that happened in gdm last year where the
startup would race with the load of DRM graphics drivers.
GDM fixed it by essentially running the equivalent of 'udevadm settle'.
The same kind of fix needs to be ported to sddm or systemd needs to be
modified to not emit
The issue here is the same one that happened in gdm last year where the
startup would race with the load of DRM graphics drivers.
GDM fixed it by essentially running the equivalent of 'udevadm settle'.
The same kind of fix needs to be ported to sddm or systemd needs to be
modified to not emit
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2008958
Title:
please backport 0.21 to jammy
To manage notifications about this bug go to:
Thanks for testing! By chance do either of those have batteries? Could
you test with AC unplugged too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2008958
Title:
please backport 0.21 to jammy
On 5/3/2024 07:05, fililip wrote:
This patch allows setting a low power cap if |ignore_min_pcap| is set to 1.
Signed-off-by: fililip
Rather than an attachment you should send the patch inline. That would
mean that your commit message and SoB should be at the top of the patch
itself.
If
org/drm/amd/-/issues/3351
Signed-off-by: Mario Limonciello
---
I tested this on SMU 13.0.4 for ~85 cycles with this script, BIOS 1.1.0.2a and
didn't observe any hangs.
```
#!/bin/sh
echo test_resume > /sys/power/disk
i=1
while [ : ]; do
echo "Starting cycle $i"
echo disk > /sys
-foundations-team, but admittedly I have not
conferred closely with other members.
I would invite discussion on any opposing views from other members.
On Sun, Feb 18, 2024 at 12:11:48AM -0600, Mario Limonciello wrote:
Considering all of that, I wanted to discuss with the release team to
modify
t was just introduced that regressed VRR disable it for now
so that problem can be properly root caused.
Cc: Tom Chung
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3344
Fixes: 5950efe25ee0 ("drm/amd/display: Enable Panel Replay for static screen
use case")
Signed-off-b
On 4/29/2024 08:38, Alex Deucher wrote:
This reverts commit 31729e8c21ecfd671458e02b6511eb68c2225113.
This causes problems with reboots/shutdowns for some users.
Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3351
Signed-off-by: Alex Deucher
Cc: Tim Huang
It would be unfortunate
I've tested the jammy upload against two AMD Phoenix laptops and
everything is working as I would expect.
However; I don't think it's appropriate to add the verification-done-
jammy tag until we have some information from people on Intel machines
to ensure we didn't cause any unintended side
And so it's clear how this size is determined by fwupd it's based on the
size of the payload the system will be using (IE the SPI size):
https://github.com/fwupd/fwupd/blob/9713cead62e79da26d4c5637dd9682b21a9f0b21/plugins/uefi-
capsule/fu-uefi-device.c#L635
The size is doubled because often the
Public bug reported:
If someone sets up Windows before Ubuntu, Windows will create an EFI
system partition that gets reused by Ubuntu.
This is generally fine, but a major problem is that the EFI system
partition is also where firmware updates are staged during a BIOS
update.
If the ESP is too
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059215
Title:
HDMI Display Not detected: AMD Ryzen 5 7530U/LENOVO IdeaPad Flex 5
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2059215
Title:
HDMI Display Not detected: AMD Ryzen 5
On 4/13/2024 03:51, Gergo Koteles wrote:
Hi>
ABM will reduce the backlight and compensate by adjusting brightness and
contrast of the image. It has 5 levels: 0, 1, 2, 3, 4. 0 means off. 4 means
maximum backlight reduction. IMO, 1 and 2 look okay. 3 and 4 can be quite
impactful, both to
On 4/13/2024 03:51, Gergo Koteles wrote:
Hi>
ABM will reduce the backlight and compensate by adjusting brightness and
contrast of the image. It has 5 levels: 0, 1, 2, 3, 4. 0 means off. 4 means
maximum backlight reduction. IMO, 1 and 2 look okay. 3 and 4 can be quite
impactful, both to
For the plymouth part I think the suggestion above "plymouth.use-
simpledrm" makes sense.
--
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/2063143
Title:
Frequent boot to black display
For the plymouth part I think the suggestion above "plymouth.use-
simpledrm" makes sense.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
To manage
For the plymouth part I think the suggestion above "plymouth.use-
simpledrm" makes sense.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to sddm in Ubuntu.
https://bugs.launchpad.net/bugs/2063143
Title:
Frequent boot to black display
To
> No longer in progress. You can get to 100% fixed by adding kernel
parameter 'plymouth.use-simpledrm' but I'm not totally sure that's
something everyone will want.
The main reasons that can be problematic are rotation right? I wonder
if the right way to go about it is a heuristic within
> No longer in progress. You can get to 100% fixed by adding kernel
parameter 'plymouth.use-simpledrm' but I'm not totally sure that's
something everyone will want.
The main reasons that can be problematic are rotation right? I wonder
if the right way to go about it is a heuristic within
** Description changed:
- Products with DCN 3.5 need linux-firmware to be added for noble.
- Matching kernel support is already in kernel 6.8.
+ [Impact]
+ Products with DCN 3.5 need linux-firmware to be added for noble. Matching
kernel support is already in kernel 6.8.
+ Without this
** Description changed:
- Products with DCN 3.5 need linux-firmware to be added for noble.
- Matching kernel support is already in kernel 6.8.
+ [Impact]
+ Products with DCN 3.5 need linux-firmware to be added for noble. Matching
kernel support is already in kernel 6.8.
+ Without this
Public bug reported:
Products with DCN 3.5 need linux-firmware to be added for noble.
Matching kernel support is already in kernel 6.8.
6bfdacdd amdgpu: add DMCUB 3.5 firmware
cb59bf73 amdgpu: add VPE 6.1.0 firmware
3ca35ef5 amdgpu: add VCN 4.0.5 firmware
9a3a6c61 amdgpu: add UMSCH 4.0.0
Public bug reported:
Products with DCN 3.5 need linux-firmware to be added for noble.
Matching kernel support is already in kernel 6.8.
6bfdacdd amdgpu: add DMCUB 3.5 firmware
cb59bf73 amdgpu: add VPE 6.1.0 firmware
3ca35ef5 amdgpu: add VCN 4.0.5 firmware
9a3a6c61 amdgpu: add UMSCH 4.0.0
There is a second commit with a similar problem and really the one I
should have linked; this one is much more severe.
Here is that fix:
https://github.com/torvalds/linux/commit/37bee1855d0e3b6dbeb8de71895f6f68cad137be
It also came into 6.8.3.
3e52444ed190 ("ASoC: amd: yc: Revert "add new YC
There is a second commit with a similar problem and really the one I
should have linked; this one is much more severe.
Here is that fix:
https://github.com/torvalds/linux/commit/37bee1855d0e3b6dbeb8de71895f6f68cad137be
It also came into 6.8.3.
3e52444ed190 ("ASoC: amd: yc: Revert "add new YC
The problem is that the "Pink Sardine" (Phoenix) laptops were being
applied to the "Yellow Carp" (Rembrandt) driver. This is improper
behavior and will cause other problems even if it fixed the immediate
microphone issue.
The Phoenix Lenovo laptops are supposed to have something in the ACPI
The problem is that the "Pink Sardine" (Phoenix) laptops were being
applied to the "Yellow Carp" (Rembrandt) driver. This is improper
behavior and will cause other problems even if it fixed the immediate
microphone issue.
The Phoenix Lenovo laptops are supposed to have something in the ACPI
This is the upstream solution:
https://github.com/torvalds/linux/commit/861b3415e4dee06cc00cd1754808a7827b9105bf
Here is the commit from 6.8.3:
b44a34f581b0 ("ASoC: amd: yc: Revert "Fix non-functional mic on Lenovo
21J2"")
--
You received this bug notification because you are a member of
This is the upstream solution:
https://github.com/torvalds/linux/commit/861b3415e4dee06cc00cd1754808a7827b9105bf
Here is the commit from 6.8.3:
b44a34f581b0 ("ASoC: amd: yc: Revert "Fix non-functional mic on Lenovo
21J2"")
--
You received this bug notification because you are a member of
I've uploaded a 1.9.16 fwupd and 0.3.18 libxmlb (build-dependency for
fwpud 1.9.16) to the archive for an SRU team member to review. It
should fall under
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages
I've got build logs and a diff of the uploads posted at this PPA as well:
I've uploaded a 1.9.16 fwupd and 0.3.18 libxmlb (build-dependency for
fwpud 1.9.16) to the archive for an SRU team member to review. It
should fall under
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages
I've got build logs and a diff of the uploads posted at this PPA as well:
I've uploaded a 1.9.16 fwupd and 0.3.18 libxmlb (build-dependency for
fwpud 1.9.16) to the archive for an SRU team member to review. It
should fall under
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages
I've got build logs and a diff of the uploads posted at this PPA as well:
I've uploaded a 1.9.16 fwupd and 0.3.18 libxmlb (build-dependency for
fwpud 1.9.16) to the archive for an SRU team member to review. It
should fall under
https://launchpad.net/~superm1/+archive/ubuntu/uefi/+packages
I've got build logs and a diff of the uploads posted at this PPA as well:
I suggest redoing the diff to fwupd-efi 1.6. It "basically" is the same
as 1.5 but drops all the debian patches that were upstreamed.
** Summary changed:
- [FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18
+ [FFe] [HWE] fwupd-efi 1.6 and gnu-efi 3.0.18
--
You received this bug notification because
According to the upstream bug, this appears to be a new intended
behavior with newer gnupg2:
https://dev.gnupg.org/T6871
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
I managed to get it working as a user by manually starting pcscd.service
and with the following to force scdaemon to use it.
# cat ~/.gnupg/scdaemon.conf
card-timeout 5
disable-ccid
To me this seems to be a regression in behavior from 2.2.27-3ubuntu2.1
to 2.4.4-2ubuntu17.
** Bug watch added:
I managed to get it working as a user by manually starting pcscd.service
and with the following to force scdaemon to use it.
# cat ~/.gnupg/scdaemon.conf
card-timeout 5
disable-ccid
To me this seems to be a regression in behavior from 2.2.27-3ubuntu2.1
to 2.4.4-2ubuntu17.
** Bug watch added:
According to the upstream bug, this appears to be a new intended
behavior with newer gnupg2:
https://dev.gnupg.org/T6871
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/2061708
According to the upstream bug, this appears to be a new intended
behavior with newer gnupg2:
https://dev.gnupg.org/T6871
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061708
Title:
Yubikey
I managed to get it working as a user by manually starting pcscd.service
and with the following to force scdaemon to use it.
# cat ~/.gnupg/scdaemon.conf
card-timeout 5
disable-ccid
To me this seems to be a regression in behavior from 2.2.27-3ubuntu2.1
to 2.4.4-2ubuntu17.
** Bug watch added:
Public bug reported:
In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
If I run this as root it
Public bug reported:
In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
If I run this as root it
Public bug reported:
In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but
since upgrading to Noble I get the following trying to access it.
$ gpg --card-status
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
If I run this as root it
** Changed in: libxmlb (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899036
Title:
failed to build silo: failed to compile
Variable sized arrays have fallen out of fashion.
There are various patches like that which fix this issue every time it
crops up.
If you can still reproduce on the latest 6.9-rc kernels you should
report a bug upstream to get the remaining cases fixed. Or if you feel
comfortable you can write a
https://patchwork.freedesktop.org/patch/588305/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039926
Title:
Error UBSAN: array-index-out-of-bounds amdgpu
I've updated the description to the SRU template. I do feel that this
meets the "other safe cases" section.
** Description changed:
+ [ Impact ]
+
+ power-profiles-daemon has the ability to make drastic improvements to
+ the power consumption of machines. This increases the likelihood of
+
Variable sized arrays have fallen out of fashion.
There are various patches like that which fix this issue every time it
crops up.
If you can still reproduce on the latest 6.9-rc kernels you should
report a bug upstream to get the remaining cases fixed. Or if you feel
comfortable you can write a
https://patchwork.freedesktop.org/patch/588305/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039926
Title:
Error UBSAN: array-index-out-of-bounds amdgpu
That's great to hear!
I'll close this issue then since we have the newer version in Noble and a
wishlist bug to backport it to Jammy:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2008958
If anyone else encounters this again, please ensure you're on 0.21 and if you
are
** Description changed:
[ Impact ]
power-profiles-daemon has the ability to make drastic improvements to
the power consumption of machines. This increases the likelihood of
them passing energy certifications such as Energy Star.
On AMD laptops the following improvements are made:
I've updated the description to the SRU template. I do feel that this
meets the "other safe cases" section.
** Description changed:
+ [ Impact ]
+
+ power-profiles-daemon has the ability to make drastic improvements to
+ the power consumption of machines. This increases the likelihood of
+
That's great to hear!
I'll close this issue then since we have the newer version in Noble and a
wishlist bug to backport it to Jammy:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2008958
If anyone else encounters this again, please ensure you're on 0.21 and if you
are
As this is going to be staged on the PPA and copied; how about staging
it "now" rather than waiting for the release manager?
This will allow at least testing it with secure boot turned off (using
the unsigned binary).
--
You received this bug notification because you are a member of Ubuntu
It was confirmed by many people this is fixed in the upgraded Framework
BIOS 3.05.
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445
** This bug has been marked a duplicate of bug 2056445
external monitors flash white with every interrupt
--
You received this bug notification because you are a member of Kernel
Packages, which is
1 - 100 of 13478 matches
Mail list logo
