Possibly the same issue as fixed in mesa 24.1
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11138
Please uprev mesa in the snap and see if it helps.
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11138
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11138
--
You receiv
Can you check that? Was this maybe when the snap refreshed silently in
background? Or try a version without snap so you could use the host
mesa?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083538
T
Thanks @rpil2 for the reply! However, I'm not so much concerned about
the content of the messages. My challenge is, that the messages are
broken into multiple lines. That makes it harder to usefully apply tools
like logcheck.
For the life of me, I could not find how I can configure the line
breaki
This is most likely a mesa issue. Have you upgraded mesa recently to
match when it showed up?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
I have been using logcheck for automatic even emails since at least
Ubuntu 18.04 successfully. Recently I upgraded from Ubuntu 22.04 to
Ubuntu 24.04, and ever since, I have a problem with long kernel
messages. The message appears to be split into multiple lines in
/var/log/sys
Do you need anything else from me, or is this enough to continue the
investigation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081199
Title:
[nvidia] On high resolution modes, after screen resum
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821790/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081199
apport information
** Attachment added: "modified.conffile..etc.init.d.apport.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821789/+files/modified.conffile..etc.init.d.apport.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821788/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081199
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821786/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821787/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081199
apport information
** Tags added: apport-collected
** Description changed:
This is a follow-up issue from
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/2075525, and some of the information from the earlier issue
may apply here.
I have configured the host scre
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821785/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Actually the second is in 6.11 already.
> git describe --contains bf5641eccf71bcd13a849930e190563c3a19815d
v6.11-rc2~2^2~4
This is just an ask for 6.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
I see the same message on 0x60. Please pull in the this commit too.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bf5641eccf71bcd13a849930e190563c3a19815d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
onf helped same
some bits, but I still need some extra 50 MB or so...
Thanks,
Mario
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1988299
Title:
Can't upgrade from 20.04 to 22.04 due to extreme sp
Public bug reported:
This is a follow-up issue from
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/2075525, and some of the information from the earlier issue
may apply here.
I have configured the host screen with two monitors extending the desktop.
They are both configured
For anyone coming here, the follow-up issue is in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/2081199
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075525
Title:
After scr
> I don't know why i use dkms
When you installed the packaged version of ROCm you can use arguments to
decide whether or not to build the DKMS package. I don't expect you
really need it with this kernel version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I'm sorry for coming back to this, but the new display cable does *not*
help.
I have just had actually my worst Gnome crash so far, and it happened
immediately on the first try, after upgrading my HDMI cable to a
supposedly decent 2.1 standards cable, and switching again to 4K
resolution at 60 Hz
I am tending to agree with Juerg, this is not Ubuntu's bug. They picked
up a stable update that fixed a problem, but it just so happens this
DKMS doesn't compile anymore.
I think the DKMS package will need to be re-spun due to this change.
I suggest reporting it here: https://gitlab.freedesktop.o
Ok, so, for what its worth, here is my current summary:
- I already have `ubuntu-drivers-common` `1:0.9.7.6ubuntu3.1` installed since
a few days, and it did not help resolve the problem.
- I have reduced the monitor resolution, and this reliably circumvents the
problem (no more issues since 24h
This definitely isn't an Ubuntu kernel bug, I will reject it as such.
You can file an issue here:
https://gitlab.freedesktop.org/drm/amd/-/issues if you have problems
stemming from that script.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notificati
> That's an unsupported DKMS, not a kernel problem. Is there any reason
why you don't use the kernel's amdgpu driver?
The DKMS driver takes an upstream snapshot of amdgpu for use with older
kernel versions. As I notice that in the above error log the DKMS
driver is from "6.8.5-2009582.24.04" you
Also, the issue goes away when I turn down the resolution to 1920x1080
again. So it is certainly tied to the high resolution.
The problem may have something to do with the HDMI cable on one of the
two monitors. Only one monitor uses HDMI, the second monitor uses
DisplayPort. Before I switched to H
Dear @vanvugt and all,
I am so happy to find this issue, because I suffer from the same problem.
However I am very surprised to see this issue closed as fixed, when @raffaeler
was saying that the proposed fix does *not* solve the main problem (and it does
not solve it for me either)!
So the ori
Thanks for checking. I believe what's going on is that it resets the
topology, but the policy to re-authorize it doesn't happen because bolt
is missing until the rootfs is loaded. So initramfs needs a hook to
include bolt.
--
You received this bug notification because you are a member of Ubuntu
Fwupd only reports the security of the firmware that it can measure.
It's not a fwupd bug if there is a problem.
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Thanks for confirming it. You can also try to add thunderbolt to
/etc/initramfs-tools/modules to see if that's enough to fix the issue
instead of the kernel command line workaround.
I suspect it's not though, and that a hook will be needed to add:
* /lib/udev/rules/90-bolt.rules
* bolt.service
*
Try adding thunderbolt.host_reset=0 to your kernel command line.
Suspect it's the changes that came in
https://launchpad.net/ubuntu/+source/linux/6.8.0-38.38:
- thunderbolt: Introduce tb_port_reset()
- thunderbolt: Introduce tb_path_deactivate_hop()
- thunderbolt: Make tb_switch_reset(
This appears to be a different problem even if it leads to same symptom.
Please open a separate issue.
--
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: S
> But building a new kernel and switching to it without deeper
experience and a fallback would be too hard for me.
No need to build a new kernel. There are binaries in the link that was
posted above. You can grab some of those to try. Just note that you
need to turn off secure boot if you have i
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077411
Title:
[Ubuntu 24.04] Somtimes unable to exit 'fwupd' install excution via
That regression isn't real. Looks like an infra problem.
0s autopkgtest [15:16:00]: starting date and time: 2024-08-23 15:16:00+
0s autopkgtest [15:16:00]: git checkout: fd3bed09 nova: allow more retries
for quota issues
0s autopkgtest [15:16:00]: host
juju-7f2275-prod-proposed-migratio
Verified that ESP is still being identified properly on my test systems.
❯ sudo fwupdtool esp-list
Loading… [ ]15:24:50.821
FuHistoryLoading…
[** ]
Selected volume: /org/freedesk
KC - Yes, I've already uploaded it to unapproved queue. It's waiting
for SRU team member review (see comment #8).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076151
Title:
[SRU] Support new hard
Bryce,
I can report the following:
Am 14. Aug 2024, um 15:22:30 schrieb Bryce Harrington:
> Mario, can you provide a log showing the assertion failure?
It simply says:
gpsmon: assertion failure, probable I/O error
Or with gpsmon -D5 to provide some more details:
gpsmon:INFO: startup at 2
Perhaps a dumb question - but why even bother to put any of the GPU
binaries in the initramfs? There should be a good enough display from
the pre-boot framebuffer that none of them should be needed with
simpledrm.
Punt i915.ko, xe.ko, amdgpu.ko, nvidia.ko out of the initramfs and let
them get loa
As this is really a development effort not a bug I've also filed it at
https://github.com/canonical/ubuntu-desktop-provision/issues/800.
** Bug watch added: github.com/canonical/ubuntu-desktop-provision/issues #800
https://github.com/canonical/ubuntu-desktop-provision/issues/800
--
You receiv
** Description changed:
- Please see offical fwupd bug report ticket and the maintainer fixed it and
commited it already
+ [Impact]
+ Please see offical fwupd bug report ticket and the maintainer fixed it and
commited it already
* https://github.com/fwupd/fwupd/issues/7593
And following
** Changed in: fwupd (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076151
Title:
[SRU] Support new hardware system in mediatek_scalar
** Changed in: fwupd (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077411
Title:
[Ubuntu 24.04] Somtimes unable to exit 'fwupd' instal
** Changed in: fwupd (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077553
Title:
ESP detection failures
To manage notifications about
I've uploaded the 1.9.24 release to unapproved queue for SRU team to
review (reminder of
https://wiki.ubuntu.com/StableReleaseUpdates#fwupd_and_fwupdate)
I also have it staged on a PPA for anyone that would like to test in advance of
SRU team's review.
https://launchpad.net/~superm1/+archive/ubun
I've uploaded the 1.9.24 release to unapproved queue for SRU team to
review (reminder of
https://wiki.ubuntu.com/StableReleaseUpdates#fwupd_and_fwupdate)
I also have it staged on a PPA for anyone that would like to test in advance of
SRU team's review.
https://launchpad.net/~superm1/+archive/ubun
I've uploaded the 1.9.24 release to unapproved queue for SRU team to
review (reminder of
https://wiki.ubuntu.com/StableReleaseUpdates#fwupd_and_fwupdate)
I also have it staged on a PPA for anyone that would like to test in advance of
SRU team's review.
https://launchpad.net/~superm1/+archive/ubun
** Changed in: fwupd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065874
Title:
Can't update firmware on TPM-backed FDE systems
To manage notificatio
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072612
Title:
Lenovo touchpad intermittently stops working with i2c_designware
err
FWIW I don't feel this is likely a kernel regression but rather a
platform firmware problem.
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=219101
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bug
** Changed in: fwupd (Ubuntu)
Status: New => Triaged
** Also affects: fwupd via
https://github.com/fwupd/fwupd/issues/7520
Importance: Unknown
Status: Unknown
** Also affects: fwupd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: fwupd (Ubuntu Orac
fwupd (Ubuntu Oracular)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076151
Title:
[SRU] Support new hardware system in mediatek_scalar p
This is fixed in both main and 1_9_X branches upstream and will be part
of the fwupd 1.9.24 release. When that's released this will be updated
in Ubuntu.
** Changed in: fwupd (Ubuntu Oracular)
Assignee: (unassigned) => Mario Limonciello (superm1)
** Changed in: fwupd (Ubuntu
user manually names their ESP using anything in the heuristics list
it will no longer be identified properly.
** Affects: fwupd
Importance: Unknown
Status: Unknown
** Affects: fwupd (Ubuntu)
Importance: High
Assignee: Mario Limonciello (superm1)
Status: Triaged
** Af
** Also affects: ubuntu-desktop-provision
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064023
Title:
Installer should detect small ESP in a dual boot
T
** Changed in: fwupd (Ubuntu Oracular)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077411
Title:
[Ubuntu 24.04] Somtimes unable to e
fwupd has an exception in SRU process and is supposed to be updated to
upstream point releases for SRU.
https://wiki.ubuntu.com/StableReleaseUpdates#fwupd_and_fwupdate
https://wiki.ubuntu.com/firmware-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There are going to be a few things Dell needs too on 1.9.24. I suggest
once it's released an update happens for both reasons.
** Also affects: fwupd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: fwupd (Ubuntu Oracular)
Importance: Undecided
Status: New
**
have tested the other unit
tested and be in a position to discuss (if needed with upstream) what
needs to be done. I will also want to manually build latest -git to
verify that maybe this issue has been fixed by upstream in the meantime.
Best regards,
Mario
Am 14. Aug 2024, um 15:22:30 schrieb Bryce
** Changed in: linux-oem-6.8 (Ubuntu Noble)
Status: Confirmed => 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/2064595
Title:
AMD Rembrandt & AMD Rembrandt-R: Suspend hangs syst
I'll keep you posted.
Best regards,
Mario,
DL5MLO
Am 08. Aug 2024, um 17:25:36 schrieb Mitchell Dzurick:
> Hi, I've kicked off a build in my PPA here[0].
>
> Mario, feel free to test the package in my PPA once it finishes building
> (should hopefully take about 4-5 hours fr
Since this is the only GPS hardware I have here at the moment, I can not know
if it only affects my hardware.
I had gdb'd the issue down and it was obvious enough. I then found that it has
been already been fixed in upstream gpsd gitlab -master.
I only assume that this is triggered only under ce
.
Regards,
Mario
** Affects: gpsd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076191
Title:
gpsmon crashes (segfault)
To manage
I feel it should also backport to jammy since 6.8 kernel will be in
jammy too.
--
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:
sddm/simpledrm race conditions leads to frequent black dis
** 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 notificatio
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 bug
*** 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 f
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 kernel
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: https://bugs.la
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 -0100
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.
https://bugs.launchpad.net/bugs/20700
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 3a0fa3bc245ef92838a82
** 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 bla
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 gir1
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 longe
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 no
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 of
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:
[S
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 bug
*** 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
Bugs
** 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 are
*** 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
Bugs
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.
Ubuntu-6.5.
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 thi
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 U
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 ins
#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 notif
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 from
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 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: Suspend
> 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 res
*** 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.
https://bugs.launch
*** 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 you
*** 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.
https://bugs.launch
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
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
Casp
1 - 100 of 10447 matches
Mail list logo
