** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071889
Title:
a critical typo in the code managing the ASPM settings for PCI
Express devices
To manage
I do have a theory.
Maybe it's bug 2071889
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064595
Title:
AMD Rembrandt & AMD Rembrandt-R: Suspend hangs system
To manage notifications about this
*** This bug is a duplicate of bug 2071889 ***
https://bugs.launchpad.net/bugs/2071889
** This bug has been marked a duplicate of bug 2071889
a critical typo in the code managing the ASPM settings for PCI Express
devices
--
You received this bug notification because you are a member of
Matthew, Chris,
Maybe one of you guys can add a kernel with that revert for people to
use?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070020
Title:
Lenovo dock no longer working after upgrade
It sure sounds like there are some other patches in Ubuntu's kernel
causing problems.
Could you check mainline v6.9 and v6.9.7? I know they backported some
ASPM patches. Maybe those cause issues for some of these machines?
If those are fine then what I suggest doing is bisecting Ubuntu's
If I was to guess it's one of these patches that causes it.
965f593401bd PCI/ASPM: Update save_state when configuration changes
c12dda119c7a PCI/ASPM: Disable L1 before configuring L1 Substates
7fe5ec02955e PCI/ASPM: Call pci_save_ltr_state() from pci_save_pcie_state()
014516361233 PCI/ASPM: Save
Canonical 6.5 series seems to have picked up at least one bad commit
that was reverted upstream.
commit 15c983d0cbb5a158eafb9cb88e6d8dfc4477d9c2
Author: Melissa Wen
Date: Fri Dec 29 15:25:00 2023 -0100
drm/amd/display: fix bandwidth validation failure on DCN 2.1
BugLink:
I don't know if it's the same issue; but there is another relatively
similar issue that occurred very recently: bug #2070096
As I mentioned there, this commit is at least PART of the problem:
commit 15c983d0cbb5a158eafb9cb88e6d8dfc4477d9c2
Author: Melissa Wen
Date: Fri Dec 29 15:25:00 2023
And that commit did go back to stable:
https://git.kernel.org/stable/c/6266b3a312b7f69c883c2d7c82d85772464421d2
So I guess Canonical team missed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's at least part of the problem.
commit 15c983d0cbb5a158eafb9cb88e6d8dfc4477d9c2
Author: Melissa Wen
Date: Fri Dec 29 15:25:00 2023 -0100
drm/amd/display: fix bandwidth validation failure on DCN 2.1
BugLink: https://bugs.launchpad.net/bugs/2059068
commit
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-failed verification-failed-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066275
Title:
[SRU] Fix
Public bug reported:
m2a0@m2a0-Default-string:~$ sudo apt upgrade
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias... Hecho
Leyendo la información de estado... Hecho
Calculando la actualización... Hecho
The following upgrades have been deferred due to phasing:
dracut-install
BTW - Several commits are in your list twice as different IDs. You
should double check that nothing landed twice...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070020
Title:
Lenovo dock no
Of that list b47f813e0303 does look suspicious to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070020
Title:
Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
To manage
We never saw a report upstream on any of the stable kernels like this.
To me; I suspect this is a case that a commit back ported to Canonical
6.5 without a matching dependency, but a bisect will be really helpful
to understand it.
--
You received this bug notification because you are a member
I also think it should target Jammy because eventually the 6.8 kernels
will backport there and introduce this bug to even more people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066275
Title:
I do think it makes sense to pull in the change you're doing for now,
but I do want to mention this is tech debt to pick up that approach to
avoid this issue as that isn't merged and there isn't really line of
sight to a proper fix:
https://github.com/sddm/sddm/pull/1924
--
You received this
*** This bug is a duplicate of bug 2070020 ***
https://bugs.launchpad.net/bugs/2070020
** This bug has been marked a duplicate of bug 2070020
Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
--
You received this bug notification because you are a member of Ubuntu
** Also affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: regression
** Tags removed: regression
** Tags added: regression-update
** Changed in: linux-oem-6.5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you
*** This bug is a duplicate of bug 2070020 ***
https://bugs.launchpad.net/bugs/2070020
** This bug has been marked a duplicate of bug 2070020
Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
--
You received this bug notification because you are a member of Ubuntu
I read on that link that mainline 6.9.3 is fine. So there is some bad
backport.
Can you handle building a kernel? If so; it would probably be best to
find the cause by bisecting [1].
You would clone the Ubuntu kernel tree [2] that has these tags and use them for
your start and end.
In my opinion, a weak key indirectly (not far from "almost directly")
compromises the whole system.
This is highest possible level Importance / priority.
Security urgency.
That goes for any other weak RSA in any launchpad PPAs.
TODO: replace all Launchpad weak keys with at least RSA4096 and
That's a BIOS bug with VCN not a GPU F/W bug. We can reproduce it on
the same BIOS as you, and updating to a newer BIOS it goes away.
You can workaround it by masking the VCN IP block like this:
amdgpu.ip_block_mask=0xfcff
--
You received this bug notification because you are a member of
Please try 6.8.5 mainline and 6.8.12 mainline. There are binary builds
created here:
https://kernel.ubuntu.com/mainline/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064595
Title:
AMD Rembrandt
#46:
That's this bug:
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/2063143
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268
Title:
Phantom "Unknown Display" shown in Settings after
#19/#20.
Your issue is not that one that you linked. 6.8.0-38.38 picks up the
fix for #2064595. So if that helps, your issue is a duplicate of
#2064595. If that doesn't help, you have a different issue. You should
open up your own issue for triage in this case.
--
You received this bug
The GUI button triggers the lock action and dpms. Grab a newer kernel or
backport that patch linked in the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067945
Title:
Restart after resume
I can explain your result. The issue is specifically a race condition
with the lock screen triggering after the suspend sequence starts. The
driver change that helps it flushes content during the suspend sequence
to ensure engines are not running when suspend starts.
By using pm utils you don't
** Summary changed:
- S2idle regression
+ AMD Rembrandt & AMD Rembrandt-R: Suspend hangs system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064595
Title:
AMD Rembrandt & AMD Rembrandt-R:
> Command "sudo pm-suspend" does not work properly on my notebook, just
blank screen but without going to sleep mode - hard restart needed.
FYI pm-utils is orphaned and outdated. You should be using `systemctl
suspend` to suspend from CLI.
> Yes, CPU on my ASUS notebook is AMD Ryzen 7 6800H, so
If this is AMD Rembrandt, it's probably this bug:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2064595
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067945
Title:
Restart after
*** This bug is a duplicate of bug 2064595 ***
https://bugs.launchpad.net/bugs/2064595
** This bug has been marked a duplicate of bug 2064595
S2idle regression
--
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 2069357 ***
https://bugs.launchpad.net/bugs/2069357
** This bug has been marked a duplicate of bug 2069357
Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo
Thunderbolt 3 Gen 2 USB-C dock
--
You received this bug notification because
*** This bug is a duplicate of bug 2064595 ***
https://bugs.launchpad.net/bugs/2064595
** This bug has been marked a duplicate of bug 2064595
S2idle regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
AFAIK It's a bad backport to 5.15 stable. If it's what I think, here's
the fix (IIRC).
https://lore.kernel.org/amd-gfx/20240523173031.4212-1-w_ar...@gmx.de/
Try applying that to your 5.15 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
AFAIK It's a bad backport to 5.15 stable. If it's what I think, here's
the fix (IIRC).
https://lore.kernel.org/amd-gfx/20240523173031.4212-1-w_ar...@gmx.de/
Try applying that to your 5.15 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
versuch, mysql-server zu installieren
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: mysql-server-8.0 8.0.36-2ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
Uname: Linux 6.8.0-35-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
*** This bug is a duplicate of bug 2064595 ***
https://bugs.launchpad.net/bugs/2064595
** This bug has been marked a duplicate of bug 2064595
S2idle regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Should be a duplicate of that. It was fixed in upstream 6.8.5, Ubuntu's
6.8.0-35 is still on 6.8.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067997
Title:
Lenovo T14 Gen3 AMD laptop freezes
Ping?
From: Mario Limonciello
Sent: Wednesday, May 1, 2024 10:32:49 AM
To: Robie Basak ; Mario Limonciello
Cc: ubuntu-release@lists.ubuntu.com ; Richard
Hughes
Subject: Re: Refine the firmware-updates exception
Robie,
My apologies; my email didn't get
I posted some idea over to the systemd bug on a way to approach this
from systemd instead of each greeter.
https://github.com/systemd/systemd/issues/32509#issuecomment-2134152084
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The discussion upstream on dri-devel has mostly settled upon userspace greeters
need to support hot-unplug.
https://lore.kernel.org/dri-devel/ZkyZCmMU86nUV4TO@phenom.ffwll.local/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can someone with an affected system raise a bug report upstream to lightdm?
There was a very similar bug that occurred in GDM last year:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2909
And there is a similar report opened with SDDM:
https://github.com/sddm/sddm/issues/1917
** Summary
** Summary changed:
- Frequent boot to black display
+ sddm/lightdm race conditions leads to frequent black display on bootup
** Summary changed:
- sddm/lightdm race conditions leads to frequent black display on bootup
+ sddm/simpledrm race conditions leads to frequent black display on bootup
** Package changed: linux (Ubuntu) => lightdm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063983
Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system
Same setup as #2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065250/comments/2
The failing monitor is 1080p old NEC MustySync EA231EMi
The main monitor is 4K, it has no issues
Lowering resolutions to 1600x900 on failing monitor or 1080p on 4k monitor
solves the issue
Lowering refresh
*** 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 should be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2064595
The fix is
https://github.com/torvalds/linux/commit/ca299b4512d4b4f516732a48ce9aa19d91f4473e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Do you have secure boot enabled? if so, turn it off and hopefully the
kernel you built should be bootadble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065838
Title:
System crash on resume from
It may be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065250, but
hardware is different
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066293
Title:
External screen
As the firmware is on it's own stable and by the time this hardware is
in market that kernel fix should be picked up adding verification done
tag.
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Internal team tested this SRU against current generic and OEM kernel and
it fails on both because they're missing the fix for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2066233.
After adding in that fix it works.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: linux (Ubuntu)
Status: New => Invalid
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065839
Title:
UBSAN: array-index-out-of-bounds
To
Save the below as a patch file and then apply using "patch -p1 < FILE".
Build your kernel and see if it has helped.
diff --git a/drivers/acpi/acpica/exregion.c b/drivers/acpi/acpica/exregion.c
index 8907b8bf4267..ca060ec6936e 100644
--- a/drivers/acpi/acpica/exregion.c
+++
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:
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
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
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
Robie,
My apologies; my email didn't get a response a while and I was on leave
a while when your response came back and I totally missed it.
Your comment on bug 1979963 prompted me to find it though!
On 3/7/24 08:00, Robie Basak wrote:
Hi Mario,
Thank you for caring for the fwupd package
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
Public bug reported:
When attempting to run the "orange-canvas" command, I encountered an
import error in Python that prevented me from running the app.
Traceback (most recent call last):
File "/bin/orange-canvas", line 5, in
from Orange.canvas.__main__ import main
File
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
> 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
Initials I was wrong, the display does get adjusted but no bigger than
1920x1024.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061886
Title:
Under VMWare resolution does not change automaticaly
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
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
Until problem is resolved, as workaround You may install snap version,
which seems to be unaffected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061880
Title:
Crash on Xubuntu 24.04 Beta when
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:
Public bug reported:
When resizing a VMWare Workstation, under Ubuntu20 the resolution would
change automaticaly. It does not in the Ubuntu 24 Beta. During
installation I have enabled download of third party driver.
I can see vmtoold running.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Public bug reported:
Created a panel with only one launcher item. on xfce4-panel --quit I get
GLib-GObject:ERROR:../../../gobject/gtypemodule.c:119:g_type_module_finalize:
assertion failed: (module->type_infos == NULL)
Bail out!
Core dump of xfce4-panel
** Attachment added:
"core.xfce4-panel.1000.964bba1a3ab04dc7b8c5e1f94939b015.49381.171327937300.zst"
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
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039926
Title:
Error UBSAN: array-index-out-of-bounds amdgpu
** 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:
1 - 100 of 11393 matches
Mail list logo
