To me it looks like the crash is in glib.
** Information type changed from Private to Public
** Package changed: fwupd (Ubuntu) => glib2.0 (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpa
Although your stack probably does a better job on all the pieces you can
control than UEFI + secure boot, the root of trust doesn't come back to
hardware and that's what BootGuard is about.
I don't feel there is any work in Ubuntu for this at this time, but it's
worth iterating on the conversation
> Now the problem is I can't reproduce this so far. gnome-shell/xwayland
randomly exits at some point without any explanation (you can see it
just starts broken pipe at 12:31:54, no crash before, I need to find the
cause for that and report another bug :(
Maybe this:
https://gitlab.gnome.org/GNOM
> Attaching the Journal, the initial crash can be seen at 12:31:54, lots
going on there, but nothing root-causing this.
[ 3300.659129] WARNING: CPU: 1 PID: 65823 at
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
This is the assertion yo
This appears to be a kernel driver or platform firmware bug. If it's new
to this kernel upgrade then it's more likely a kernel bug.
You should report it against the Thinkpad ACPI driver upstream.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: power-pro
Dear Marco, Can you help me understand from which point in time you'd
like to get the trace? Gnome does not typically crash for me, I got a
crash only once. My problem is more the garbled display configuration,
that makes high resolution modes unusable for me. Do you mean I should
try to provoke mo
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2083538
Title:
amdgpu: [mmhub] page fault (src_id:0 ring:8 vmid:6 pasid:32781 /
I have deleted ~/.config/monitors.xml, then rebooted and logged in
again.
The file is not recreated automatically, it seems? The new default
display configuration for Gnome is now already 4K@60 Hz. I have waited
once, until the displays go into suspend, then resumed, and the problem
appeared immed
> but the GPU restarts are failing and the driver apparently deadlocks
or something (quite a bunch of mutex backtraces).
Yes; poor clean up/recovery should be tracked as a separate bug report
at https://gitlab.freedesktop.org/drm/amd/-/issues
--
You received this bug notification because you are
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 Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bu
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 Desktop
Packages, which is subscribed to mesa in Ubuntu.
htt
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2081199
Title:
[nvidia] On high resolution modes
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https:/
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
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
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 Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bu
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
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
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
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 Desktop
Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/2061886
Title:
Under VMWare resoluti
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 Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2061880
Title:
Crash on Xubuntu 24.
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
Package
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:
g
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
Title:
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 wo
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
+ th
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 pl
Anyone still affected by this, can I please ask you to check the 0.21
release? It's been uploaded to Noble. I've also got it backported on a
PPA that can be used on Jammy or Mantic:
https://launchpad.net/~superm1/+archive/ubuntu/ppd
After upgrading if you're seeing this message still, can you p
Public bug reported:
Due to the "input deck" the Framework 16 has a "USB" internal keyboard.
This throws off heuristics for detection of keyboards to turn off when
you select disable touchpad when typing.
This is fixed in upstream libinput with the following change:
https://gitlab.freedesktop.org
untu 22.04-LTS to fix many more bugs, but
apparently that is too late now, according to
https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476
Thanks,
-mario
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Tags: gstreamer pipewire pulseaudio so
Pulseaudio upgraded to
version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
apparently that is too late now, according to
https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476
Thanks,
-mario
To manage notifications about this bug go to:
https://bugs.lau
.04-LTS to fix many more bugs, but
apparently that is too late now, according to
https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476
Thanks,
-mario
** Affects: gst-plugins-good
Importance: Unknown
Status: Unknown
** Affects: pipewire
Importance: Unknown
This should be fixed in Noble in power-profiles-daemon 0.20.
** Changed in: power-profiles-daemon (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to power-profiles-daemon in Ubuntu.
https://
It's marked failed to upload on all architectures right now:
INFOgir1.2-glib-2.0-dev_1.78.1-15_amd64.deb: Version older than that in the
archive. 1.78.1-15 <= 2.79.1-1
INFOgir1.2-glib-2.0_1.78.1-15_amd64.deb: Version older than that in the
archive. 1.78.1-15 <= 2.79.1-1
I guess that me
https://launchpad.net/ubuntu/+source/power-profiles-daemon/0.20-1
** Changed in: power-profiles-daemon (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to power-profiles-daemon in Ubuntu.
https
Do you have something in /usr/local perhaps? Or did you have a snap
installed for fwupd?
** Package changed: gnome-software (Ubuntu) => fwupd (Ubuntu)
** Changed in: fwupd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packag
Public bug reported:
The current version of power-profiles-daemon (0.13) has support both for
amd/intel pstate drivers as well as the ACPI platform profile drivers.
If the system supports both types of drivers then only the ACPI platform
profile driver gets used.
This doesn't do a great job as a
Something I want to mention is that some drivers in the kernel and some
implementations of vendor's EC firmware internally handle AC vs battery
differently within a given platform profile. So you "automatically" get
a better power savings just going to battery compared to AC.
Thus I don't think t
This is a firmware or kernel bug, not a power profiles daemon bug.
Please report it to Lenovo to investigate the details.
** Changed in: power-profiles-daemon (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
Closing it here as this is a firmware bug not a software bug.
** Changed in: power-profiles-daemon (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to power-profiles-daemon in Ubuntu.
https://bugs
Public bug reported:
AMD testing of some Goodix MOC devices shows that this device fails to
work properly:
[ 208.586084] usb 1-2: New USB device found, idVendor=27c6,
idProduct=6496, bcdDevice= 1.00
The issue is specifically that there is a problem with the 'enroll create'
state.
It has been f
OK thanks for clarifying. Can you please still try latest 6.5.13 and
6.6.6 and see if it happens in either of those?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amd
Is this happening possibly when there is a resolution change for the
eDP? If so, can you please try the latest linux-6.5.y kernel:
https://kernel.ubuntu.com/mainline/v6.5.13/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubun
This is the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573
Here is a commit that fixes the issue by changing default pre-emption
policy since the kernel can't know about your mesa version.
https://github.com/torvalds/linux/commit/d6a57588666301acd9d42d3b00d74240964f07f
Can you please try to reproduce using a mainline upstream build?
https://kernel.ubuntu.com/mainline/v6.7-rc2/
If you can reproduce please share a new kernel log from a boot it
occurs.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xser
Public bug reported:
While upgrading procedure abort
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cups-ppdc 2.3.1-9ubuntu1.2
ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126
Uname: Linux 5.15.0-89-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
AptOrdering:
libx
Public bug reported:
While updating
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libx11-6 2:1.6.9-2ubuntu1.2
ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5Check
Public bug reported:
bugs while updating
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libx11-6 2:1.6.9-2ubuntu1.6
ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5
I've published a PPA here:
https://launchpad.net/~superm1/+archive/ubuntu/gitlab2971/+packages
This has builds both for 22.04 (Jammy) and 23.04 (Lunar). Please
upgrade to that, drop the module parameter and see if things improve.
# sudo add-apt-repository ppa:superm1/gitlab2971
# sudo apt upgrad
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Package changed: mutter (Ubuntu) => mesa (Ubuntu)
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
**
This should be a different issue than the mutter issue; please open it
up separately for investigation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2034619
Title:
[amdgpu] gnome-she
From the upstream bug this is caused by PSR, so it's not a mesa issue.
** No longer affects: mesa (Ubuntu)
** No longer affects: mesa (Ubuntu Jammy)
** No longer affects: mesa (Ubuntu Lunar)
** No longer affects: mesa (Ubuntu Mantic)
** No longer affects: mesa (Ubuntu Noble)
--
You received
It's unclear if this is a BIOS, mesa or kernel bug at this time, but
it's certainly not an Xorg bug as it was reproduced in Wayland.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2954
https://gitlab.free
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2042054
Title:
22.04.3, zen 4 7840, screen turn white exception
Status in mesa package
Please also take this fix at the same time for this same laptop. It
will fix s2idle for it.
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
drivers-x86.git/commit/?h=fixes&id=3bde7ec13c971445faade32172cb0b4370b841d9
** Changed in: libinput (Ubuntu)
Status: Confirmed => Inv
Here is the upstream patch for this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent&id=38d54ecfe293ed8bb26d05e6f0270a0aaa6656c6
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=218003
Importance: Unknown
Status: Unknown
-
#75
You can turn on proposed and then use ppa-purge command to remove my
PPA.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2034619
Title:
[amdgpu] gnome-shell gets SIGKILL'd when lo
conflict since they will be different binaries.
Please reject the *ubuntu4 version from the mantic-proposed queue and
accept the *ubuntu3.1 version (if it looks good).
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received this bug notific
/+packages
I've also uploaded the mutter package into the proposed queue for SRU
team to look at.
** Changed in: mutter (Ubuntu Mantic)
Status: Fix Committed => In Progress
** Changed in: mutter (Ubuntu Mantic)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
*** This bug is a duplicate of bug 2034619 ***
https://bugs.launchpad.net/bugs/2034619
** This bug has been marked a duplicate of bug 2034619
[amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in
Wayland
--
You received this bug notification because you are a member
6.5.6 has the fix for preemption issue, it should get fixed when stable
updates come in Mantic.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039868
Title:
amdgpu reset during usage of
This is the upstream fix for this issue:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3324
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubunt
I've split up the GDM for Jammy change into
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039757
** No longer affects: gdm3 (Ubuntu Jammy)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
[ Impact ]
When the kernel has been compiled with FB_EFI=n, FB_VESA=n, SIMPLEDRM=y a
series of events can occur that cause simpledrm to race with GDM. When GDM
loses the race then a user is left with a black screen.
This series of events doesn't currently happen in Jammy k
The issue won't occur in Lunar. It's only specifically a problem with gdm when
a kernel has been configured this way.
It's not a problem in Jammy yet, but will be a problem when such a kernel gets
backported as HWE.
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Ne
Ok in this case can you please open an upstream mesa bug?
** Changed in: mesa (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037641
Title:
Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed
right after you reported this issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you ar
I'd say that's very likely. That mesa upgrade just landed in the archive
a few days ago and the trace you reported looks more like how a mesa bug
manifests.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
You r
Are you up to date on the current version of mesa in 23.10?
23.2.1-1ubuntu2?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpa
Random resets are "typically" triggered by mesa or application bugs.
Can you still trigger them in the latest mantic (which has a more up to
date mesa and kernel)?
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: New => Invalid
** Changed in: mesa (Ubuntu)
Status: New => In
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1987792
Title:
Totem and VLC crash when playing dvd with VAAPI radeon mesa dr
> NonfreeKernelModules: fglrx
Nothing that will be done in mesa for an issue with fglrx anyway these
days.
** Changed in: mesa (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubunt
In this case the kernel is the "messenger" for the page fault. This is
more likely to be a mesa or application issue than a kernel issue.
Can you please raise a ticket to the upstream mesa bug tracker?
https://gitlab.freedesktop.org/mesa/mesa/
** Also affects: mesa (Ubuntu)
Importance: Undec
** Description changed:
- The fbdev subsystem has been deprecated for a long time. We should drop
- it in favour of using simpledrm with fbdev emulation layer.
+ [ Impact ]
+ The fbdev subsystem has been deprecated for a long time. We should drop it in
favour of using simpledrm with fbdev emulat
Mantic has 45~beta-1ubuntu1 which picks up the fix for this. Jammy is
still open.
** Changed in: gdm3 (Ubuntu Mantic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.la
I think that this should be changed in gnome software not to try to
start fwupd then when in WSL2.
** Package changed: fwupd (Ubuntu) => gnome-software (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
ht
** Also affects: mesa (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu
I believe this likely needs the VCN fixes from
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 backported.
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9728
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728
** Also affects: mesa (Ubuntu)
Importance: Undecided
** Also affects: xserver-xorg-video-amdgpu (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: Fix Committed => Fix Released
** Chan
This is fixed in mantic which just upgraded to the 0.13 release, but you
will also need to add amd_pstate=active to your kernel command line.
** Changed in: power-profiles-daemon (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Public bug reported:
0.13
This release adds support for the AMD P-State driver that's been added to the
6.3 Linux kernel. This release also fixes mismatched profiles on some HP
laptops and some miscellaneous bug fixes.
** Affects: power-profiles-daemon (Ubuntu)
Importance: Undecided
I believe the same thing can likely happen if llvm updates but mesa
stays the same. Can you embed both into the string?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
Afte
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2017142
Title:
[jam
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Xenial)
Stat
Public bug reported:
[ Impact ]
VA-API decoding doesn't work on DCN 3.1.4.
Mesa 22.2.5 includes all the code to support it but is missing the chip ID.
The device ID was included in upstream mesa 22.3.1.
[ Test Plan ]
* Verify that VA-API works using "mpv" or a similar tool that uses VA-API
*
It happen to me to.
I also removed snap as it doesn't support SSO i use in my daily work.
My /etc/apt/preferences.d/mozillateamppa:
Package: firefox*
Pin: release o=LP-PPA-mozillateam
Pin-Priority: 501:
So after each removal, i simply do:
sudo apt remove firefox && sudo apt install firefox, but i
Public bug reported:
problema para abrir qualquer vídeo seja com o totem ou usando o opencv,
apenas consigo abrir video com ffmpeg ( não se aplica ao opencv )
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: libgstreamer1.0-0 1.20.3-1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
At least from AMD's tests, backported mesa stack is working properly
with RDNA3. Adjusting tag accordingly.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of D
I tested 42.5-0ubuntu1 on a Z13 (which prompted the heuristics change)
and can confirm it's working with Wayland and the non-functional
resolutions are no longer offered.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
Yo
Public bug reported:
Version 1.1.0 (released in March 2022) brings MP3 encoding/decoding
support. It would be great if the version here could be updated.
** Affects: libsndfile (Ubuntu)
Importance: Undecided
Status: New
** Tags: upgrade-software-version
--
You received this bug
> A default Ubuntu install only gets us "Security Level 1". The highest
level is "Security Level 3".
It's not a function of the OS, it's a function of the underlying hardware,
firmware, and firmware configuration for your given system.
The "!" in the HSI string is controlled by OS behavior (such
FYI - 1.8.4 synced from Debian to Ubuntu kinetic now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1987162
Title:
43: New Device Security feature is confusing and unhel
One possible solution is to split the fwupd package along it's possible plugins
into multiple packages.
However I tend to agree that it has no use in a cloud or container seed.
I also agree libmm-glib0 shouldn't recommend modem manager.
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bolt in Ubuntu.
https://bugs.launchpad.net/bugs/1962349
Title:
Bolt doesn't work with native USB4 hosts
Sta
Just to correct a few of the targets on this issue.
* The reverts mentioned in #30 need to be pulled into linux-firmware for focal.
* They're already included in jammy.
** Changed in: amd
Status: New => Fix Released
** No longer affects: mesa (Ubuntu)
** Also affects: linux-firmware
> The comment at
https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992
suggests that disabling the DynamicUser= setting makes the service work
again. Maybe that's worth a try, in order to get both problems solved?
(i.e. shipping an override config for fwupd)
> $cat /etc/systemd/system
> https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907
This appears to have caused a regression in fwupd in Ubuntu 20.04 with
details at https://github.com/fwupd/fwupd/issues/3037
fwupd-refresh.service uses DynamicUser and now hi
1 - 100 of 669 matches
Mail list logo
