Are you by chance using NFS mounted directories? Or external entity for authentication such as LDAP or SSSD?
> -----Original Message----- > From: Thomas Stewart <tho...@stewarts.org.uk> > Sent: Wednesday, January 27, 2021 8:33 > To: Limonciello, Mario > Cc: 943...@bugs.debian.org > Subject: Re: Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh > fwupd metadata and update motd. > > > [EXTERNAL EMAIL] > > On 27 Jan 2021, at 14:18, Limonciello, Mario wrote: > > Can you check if fwupdmgr works as a standard user to talk to the daemon for > you? > > As a normal user I can run "fwupdmgr --version" fine[0]. > > However if I amend the unit to run the above[1] the output stops before > daemon version[2]. > > Kind Regards > -- > Tom > > [0] > $ id > uid=1000(thomas) gid=1000(thomas) > groups=1000(thomas),20(dialout),27(sudo),128(docker) > $ > $ /usr/bin/fwupdmgr --version > client version: 1.5.5 > compile-time dependency versions > gusb: 0.3.5 > > daemon version: 1.5.5 > $ > > [1] > ExecStart=/usr/bin/fwupdmgr --version > > [2] > Jan 27 14:24:38 systemd[1]: Starting Refresh fwupd metadata and update motd... > Jan 27 14:24:38 fwupdmgr[199579]: client version: 1.5.5 > Jan 27 14:24:38 fwupdmgr[199579]: compile-time dependency versions > Jan 27 14:24:38 fwupdmgr[199579]: gusb: 0.3.5 > Jan 27 14:24:38 fwupdmgr[199579]: Failed to connect to daemon: Exhausted all > available authentication mechanisms (tried: EXTERNAL) (available: EXTERNAL) > Jan 27 14:24:38 systemd[1]: fwupd-refresh.service: Main process exited, > code=exited, status=1/FAILURE > Jan 27 14:24:38 systemd[1]: fwupd-refresh.service: Failed with result 'exit- > code'. > Jan 27 14:24:38 systemd[1]: Failed to start Refresh fwupd metadata and update > motd.
