[neon] [Bug 432589] fwupd-signed version mismatch
https://bugs.kde.org/show_bug.cgi?id=432589 Xavier Vello changed: What|Removed |Added CC|xavier.ve...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 432589] fwupd-signed version mismatch
https://bugs.kde.org/show_bug.cgi?id=432589 --- Comment #3 from Xavier Vello --- snapd is not welcome on my systems, but I checked the official flatpak and it only ships an unsigned EFI $ find /var/lib/flatpak/app/org.freedesktop.fwupd/ -iname *.efi* /var/lib/flatpak/app/org.freedesktop.fwupd/x86_64/stable/d0fd85cb1b12f7668ab365a4cb066c0928312eb62b33aab00ba840e279042cf0/files/libexec/fwupd/efi/fwupdx64.efi $ sbverify --list /var/lib/flatpak/app/org.freedesktop.fwupd/x86_64/stable/d0fd85cb1b12f7668ab365a4cb066c0928312eb62b33aab00ba840e279042cf0/files/libexec/fwupd/efi/fwupdx64.efi [...] No signature table present Comparing to the grub EFI signed by Canonical: $ sbverify --list /boot/efi/EFI/neon/grubx64.efi signature 1 image signature issuers: - /C=GB/ST=Isle of Man/L=Douglas/O=Canonical Ltd./CN=Canonical Ltd. Master Certificate Authority image signature certificates: - subject: /C=GB/ST=Isle of Man/O=Canonical Ltd./OU=Secure Boot/CN=Canonical Ltd. Secure Boot Signing (2017) issuer: /C=GB/ST=Isle of Man/L=Douglas/O=Canonical Ltd./CN=Canonical Ltd. Master Certificate Authority For users impacted by this, would downgrading to the 1.3.9-4 provided by the focal repositories (and installing the matching fwupd-signed package) be a viable option, or would it break something? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 432589] fwupd-signed version mismatch
https://bugs.kde.org/show_bug.cgi?id=432589 Xavier Vello changed: What|Removed |Added CC||xavier.ve...@gmail.com --- Comment #1 from Xavier Vello --- Hello, I hit the same error updating my T495's firmware. both via Discover and "fwupdmgr update". A workaround for it is to restart and temporary disable secure boot in the BIOS, but this is not ideal on a work laptop. The source for this backport is at https://invent.kde.org/neon/backports-focal/fwupd ; but I am confused about the upstream origin of this packaging: - the gitlab project description links to https://launchpad.net/ubuntu/+source/fwupd, suggesting it's derived from the ubuntu packaging - the commit history suggests an import from https://salsa.debian.org/efi-team/fwupd.git instead I would love to help on this one provided there is no technical hurdle (can the Neon build infrastructure sign UEFI binaries?) and if someone can provide guidance and reviews. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 338759] when using bluetooth speakers, adjusting the volume should change the volume of these speakers, not the internal ones
https://bugs.kde.org/show_bug.cgi?id=338759 Xavier Vello <xavier.ve...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||xavier.ve...@gmail.com Ever confirmed|0 |1 --- Comment #5 from Xavier Vello <xavier.ve...@gmail.com> --- >From my testing in 18.04, kmix does not follow the device preference set in the Multimedia KCM. As a workaround, it is possible to manually set the master channel to the bluetooth headphones once paired. kmix will fallback to the internal mixer if the headphones are disconnected, then switch back to the headphones when they're connected again. I do fear that only works for a single device, what happens if I want to set multiple devices (bluetooth > hdmi > internal)? Should we introduce a Audio Playback > Control category, like we have a Audio Recording > Control one? Should kmix honor such a setting? -- You are receiving this mail because: You are watching all bug changes.
