Bug 2260444 - all fwupdmgr commands fail
Summary: all fwupdmgr commands fail
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fwupd
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-01-26 08:59 UTC by Jerry Kiely
Modified: 2024-05-13 11:02 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-13 11:02:33 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
content of /etc/fwupd (3.51 KB, application/gzip)
2024-01-26 08:59 UTC, Jerry Kiely 		no flags Details
View All

Description Jerry Kiely 2024-01-26 08:59:15 UTC 
Created attachment 2010688 [details]
content of /etc/fwupd

Description of problem:

all fwupdmgr commands fail


Version-Release number of selected component (if applicable):

fwupd-1.9.12-1.fc39.x86_64

How reproducible:

always


Steps to Reproduce:
1. execute 'fwupdmgr get-devices' or 'fwupdmgr get-updates' or 'fwupdmgr refresh'
2. fails 
3. 

Actual results:

prints 'Failed to connect to daemon: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer: startup job failed.'


Expected results:

to execute successfully


Additional info:
Comment 1 Jerry Kiely 2024-01-26 09:00:24 UTC 
I should have said that rolling back / downgrading to the previous version restores functionality.
Comment 2 Richard Hughes 2024-01-26 09:25:36 UTC 
I can reproduce the issue, debugging now -- thanks!
Comment 3 Richard Hughes 2024-01-26 09:46:06 UTC 
This is fixed by https://github.com/fwupd/fwupd/pull/6735/commits/887b0f3f2c86c4b1d239657f2c52bca52fffcb52 -- once it's been reviewed and committed I'll build a new version for Fedora.
Comment 4 Richard Hughes 2024-01-26 16:05:49 UTC 
There's a COPR build here -- if that helps: https://copr.fedorainfracloud.org/coprs/rhughes/fwupd/build/6964513/
Note You need to log in before you can comment on or make changes to this bug.