On 10/22/23 3:19 PM, Jorge Fábregas wrote:
> My DAC supports S24_3LE and S16_LE formats, but Pipewire seems to
> default to S24_3LE even for 16-bit files from CDs.
Ok I found the answer to my dilemma straight from the horse's mouth:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2411
On 10/23/23 22:51, Tim via users wrote:
And people actually write software to encourage users to take a break
from spending too much time at their computer... ;-)
I rage-quit using my computer at least once a day, because of all the
terrible software out there. Does that count?
--
==
This what I get:
rpm -qa | grep pubkey
gpg-pubkey-d651ff2e-5dadbbc1
gpg-pubkey-94843c65-5dadbc64
gpg-pubkey-6dc1be18-5ca9b41f
gpg-pubkey-c0aeda6e-5ad45327
gpg-pubkey-100bcd92-5ca9b382
gpg-pubkey-9db62fb1-59920156
gpg-pubkey-cfc659b9-5b6eac67
gpg-pubkey-be1229cf-5631588c
gpg-pubkey-7f858107-595fba
On 10/25/23 13:35, Patrick Dupre via users wrote:
rpm -qi $(rpm -qa | grep pubkey)
error: rpmdbNextIterator: skipping h# 132
Header RSA signature: BAD (header tag 268: invalid OpenPGP signature: Parsing
an OpenPGP packet:
Failed to parse Signature Packet
because: Signature appears
Samuel Sieb wrote:
> On 10/25/23 13:35, Patrick Dupre via users wrote:
>> rpm -qi $(rpm -qa | grep pubkey)
>> error: rpmdbNextIterator: skipping h# 132
>> Header RSA signature: BAD (header tag 268: invalid OpenPGP signature:
>> Parsing an OpenPGP packet:
>>Failed to parse Signature Packet
On 10/25/23 17:47, Todd Zullinger wrote:
There is some guidance for how to handle this in Common
Issues:
https://discussion.fedoraproject.org/t/third-party-rpms-with-an-invalid-signing-key-might-cause-errors-during-package-operations/80077
Oh, it's on "discussion". No wonder I couldn't find i
