Comments

39 Comments

Failed to load config: Key file does not have group “redfish”

Can you attach the contents of /etc/fwupd/ to the upstream or downstream bug please.

@cowboysmall -- can you open a bugzilla or open issue please. I need the output from sudo /usr/libexec/fwupd/fwupd --verbose from your system. Just negative karma isn't super useful to maintainers I'm afraid.

Anyone with problems, can you please test https://copr.fedorainfracloud.org/coprs/rhughes/fwupd/ -- I'm going to release that as 1.9.9 on Monday if there are no reported problems.

This update has been unpushed.

This update has been unpushed.

I need one of you to either open a Fedora bug or comment on the upstream issue -- I can't really continue to debug in this bohdi update. I need the output of "sudo strace fwupdtool --plugins synaptics_mst --plugins kinetic_dp --plugins linux_display get-devices -vv" where the copr build is installed.

Can you add your "sudo strace fwupdtool --plugins synaptics_mst -vv get-devices" output to https://github.com/fwupd/fwupd/issues/6379 please

re-test without docking station

Lenovo Thunderbolt 4 dock by any chance?

Out of interest -- are you both using daisy-chained DP monitors?

@marmijo: we're in freeze until the release.

Adam, much appreciated -- thanks!

I think 1.9.5 basically upstreamed the downstream change, no? I'm happy to push either the patched fwupd 1.9.4 into F39 or this package.

This update has been unpushed.

@freddyw gah, I get the same. on some remotes. Debugging now.

@freddyw -- how are you refreshing the metadata now? what command or program are you using?

This fixes the fwupd emulation tests.

karma

This fixes gnone-control-center, thanks!

BZ#2129343 systemd returns an empty string for the chassis type

crash when start

@jpbn that's not super helpful. Can you link to a bugreport please.