For the records:
Up to and including systemd 250.3 (testing), the service worked (with
libnss-systemd installed).
After upgrade to systemd 250.4, yet another failure mechanism seems to
have popped up:
"DynamicUser is denied access to dbus-daemon after a recent lockup bugfix"
Hi there,
looking into the same issues on multiple Bullseye systems,
I can confirm the cause to be an incorrect /etc/nsswitch.conf.
After fixing that I had to reboot for the fix to work,
I guess restarting some systemd or dbus service would have done the
trick as well.
Now for a proper fix:
Package: fwupd
Version: 1.5.7-2
Followup-For: Bug #943343
This started out as what I thought may be the same essential data as Ross
Vandergrift reported above, but I think I've figured out the problem.
I'm seeing this same issue on a bullseye system. Interestingly, not on
_all_ of my bullseye
Package: fwupd
Version: 1.5.7-3
Followup-For: Bug #943343
X-Debbugs-Cc: rvandegr...@debian.org
I have a pair of laptops, one where fwupd-refresh.service is broken and one
where it works. Both are running bullseye with the same versions of fwupd,
systemd, and dbus. No remote users, nfs, freeipa,
Just chiming in here. I see this issue on Debian Testing with
fwupd-1.5.3.-2. Removing DynamicUser=yes resolves the issue.
On 29 Jan 2021, at 03:29, Limonciello, Mario wrote:
> I'm unsure what to do here, it seems to me that there is a problem with
> systemd using DynamicUser and sssd when the service uses dbus.
> Perhaps this should be re-assigned to systemd.
I will attempt to reproduce on a non freeipa joined
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]
>
> Yes, I'm using sssd against FreeIPA.
>
> Tom
>
>
> On 28 Janua
Yes, I'm using sssd against FreeIPA.
Tom
On 28 January 2021 02:12:11 GMT, "Limonciello, Mario"
wrote:
>Are you by chance using NFS mounted directories? Or external entity
>for authentication such as LDAP or SSSD?
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?
>
Can you check if fwupdmgr works as a standard user to talk to the daemon for
you?
> -Original Message-
> From: Thomas Stewart
> Sent: Wednesday, January 27, 2021 5:42
> To: 943...@bugs.debian.org
> Subject: Bug#943343: fwupd: fwupd-refresh.service failed to start
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
Hi,
I'm running testing/sid and have fwupd-1.5.5-2 installed. I have found
that when fwupd-refresh.service restarts either with the timer or
manually that if DynamicUser=yes is enabled then the service fails to
start[0]. When I remove DynamicUser from the unit it restarts fine.
I noticed that
On Thu, 19 Mar 2020 15:02:13 +0100 Diederik de Haas
wrote:
> On donderdag 19 maart 2020 14:59:56 CET mario.limoncie...@dell.com wrote:
> > Sorry - I see now that was from a while back.
>
> And also a different user (OP).
After some upstream discussion, any remaining issues with 1.3.x this is
On donderdag 19 maart 2020 14:59:56 CET mario.limoncie...@dell.com wrote:
> Sorry - I see now that was from a while back.
And also a different user (OP).
signature.asc
Description: This is a digitally signed message part.
> From: Limonciello, Mario
> Sent: Thursday, March 19, 2020 8:58 AM
> To: Diederik de Haas
> Cc: 943...@bugs.debian.org
> Subject: RE: Bug#943343: fwupd: fwupd-refresh.service failed to start
> Refresh fwupd metadata and update motd.
>
> > -Original Message-
> -Original Message-
> From: Diederik de Haas
> Sent: Thursday, March 19, 2020 8:53 AM
> 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.
>
> On
On donderdag 19 maart 2020 14:42:56 CET mario.limoncie...@dell.com wrote:
> Has your system been rebooted recently?
Yes. I usually shutdown my system at night.
> I check on my (working) system and I don't have /run/motd.d as a symlink to
> /run/private/motd.d. For my system /run/motd.d is a real
> -Original Message-
> From: Diederik de Haas
> Sent: Thursday, March 19, 2020 7:57 AM
> 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.
>
> O
On woensdag 18 maart 2020 22:40:22 CET mario.limoncie...@dell.com wrote:
> I suspect this is related to an upgrade from the intermediary version that
> had problematic objects/permissions created.
> Can you please try to check whether there are broken symlinks in
> /var/lib/private or
e Haas
> Sent: Saturday, March 14, 2020 7:26 AM
> To: Debian Bug Tracking System
> Subject: Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh
> fwupd metadata and update motd.
>
>
> [EXTERNAL EMAIL]
>
> Package: fwupd
> Version: 1.3.9-2
> Followup-For
Package: fwupd
Version: 1.3.9-2
Followup-For: Bug #943343
Essentially the same issue as initially reported, but just got version
1.3.9-2 and it's still happening.
Running the 'ExecStart' line manually succeeded successfully.
root@bagend:~# systemctl status fwupd-refresh.service
●
Package: fwupd
Version: 1.3.4-1
Followup-For: Bug #943343
This is still broken with current mentioned version in Debian Testing. I
thought this was fixed a couple months ago.
rrs@priyasi:/var/tmp/Debian-Build/Result$ systemctl status fwupd-refresh.service
● fwupd-refresh.service - Refresh fwupd
Internal Use - Confidential
> -Original Message-
> From: Werner Mahr
> Sent: Tuesday, December 3, 2019 6:52 AM
> To: 943...@bugs.debian.org
> Subject: Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh
> fwupd
> metadata and update motd.
&g
> > Internal Use - Confidential
> >
> > In 1.3.2-5 the service is disabled by default (and also this issue should
be fixed).
> Okay. So, the bug can be closed, I guess.
I'm sorry, but it seems that it at least was reintroduced somewhen. I have
1.3.4-1 installed on testing and it fails to
Wed, 23 Oct 2019 16:40:37 +
wrote :
Hi Mario,
> Internal Use - Confidential
>
> In 1.3.2-5 the service is disabled by default (and also this issue should be
> fixed).
Okay. So, the bug can be closed, I guess.
Jean-Marc
https://6jf.be/keys/ED863AD1.txt
pgpwpc8u5Cvgq.pgp
Description:
refresh.service failed to start Refresh
> fwupd metadata and update motd.
>
>
> [EXTERNAL EMAIL]
>
> Package: fwupd
> Version: 1.3.2-2
> Severity: normal
>
> Dear Maintainer,
>
> On my PC, fwupd-refresh.service failed to start.
>
> $ systemctl status fwupd-
Package: fwupd
Version: 1.3.2-2
Severity: normal
Dear Maintainer,
On my PC, fwupd-refresh.service failed to start.
$ systemctl status fwupd-refresh.service
● fwupd-refresh.service - Refresh fwupd metadata and update motd
Loaded: loaded (/lib/systemd/system/fwupd-refresh.service; static;
27 matches
Mail list logo
