Bug 1762494 - Gnome-Software updates check fails because fwupd fails to start. It cannot even be started manually.
Summary: Gnome-Software updates check fails because fwupd fails to start. It cannot ev...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fwupd
Version: 30
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-16 20:50 UTC by Asiri Iroshan
Modified: 2020-05-26 17:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 17:59:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Journalctl -xe information (1.17 KB, text/plain)
2019-10-16 20:50 UTC, Asiri Iroshan
no flags Details

Description Asiri Iroshan 2019-10-16 20:50:06 UTC
Created attachment 1626607 [details]
Journalctl -xe information

Description of problem: Gnome-Software throws the error "Unable to get list of updates. Error calling StartServiceByName for org.freedesktop.fwupd:Timeout was reached".

When run systemctl status fwupd, it has failed to start.

'systemctl restart fwupd' gives the following error

Job for fwupd.service failed because the control process exited with error code.
See "systemctl status fwupd.service" and "journalctl -xe" for details.



Version-Release number of selected component (if applicable):
Operating system is Fedora thirty and is been updated to Kernel 5.3.5

How reproducible:
Error can be reproduced by opening up gnome-software and run an updates check.
And running systemctl status fwupd.

Steps to Reproduce:

1. Run an updates check on gnome-software
2. Run 'systemctl start fwupd'


Actual results:

systemctl status fwupd

● fwupd.service - Firmware update daemon
   Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2019-10-17 02:13:15 +0530; 2min 39s ago
     Docs: https://fwupd.org/
  Process: 4878 ExecStart=/usr/libexec/fwupd/fwupd (code=exited, status=226/NAMESPACE)
 Main PID: 4878 (code=exited, status=226/NAMESPACE)

Oct 17 02:13:15 iropc systemd[1]: Starting Firmware update daemon...
Oct 17 02:13:15 iropc systemd[4878]: fwupd.service: Failed to set up mount namespacing: No such file or directory
Oct 17 02:13:15 iropc systemd[4878]: fwupd.service: Failed at step NAMESPACE spawning /usr/libexec/fwupd/fwupd: No such file or direct>
Oct 17 02:13:15 iropc systemd[1]: fwupd.service: Main process exited, code=exited, status=226/NAMESPACE
Oct 17 02:13:15 iropc systemd[1]: fwupd.service: Failed with result 'exit-code'.
Oct 17 02:13:15 iropc systemd[1]: Failed to start Firmware update daemon.


journalctl -xe

-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An ExecStart= process belonging to unit fwupd.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 226.
Oct 17 01:59:34 iropc systemd[1]: fwupd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit fwupd.service has entered the 'failed' state with result 'exit-code'.
Oct 17 01:59:34 iropc systemd[1]: Failed to start Firmware update daemon.
-- Subject: A start job for unit fwupd.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit fwupd.service has finished with a failure.
-- 
-- The job identifier is 4637 and the job result is failed.
Oct 17 01:59:34 iropc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fw>
Oct 17 01:59:34 iropc polkitd[800]: Unregistered Authentication Agent for unix-process:3935:161365 (system bus name :1.722, object pat>
~


Expected results:

fwupd active

Additional info:

Comment 1 Asiri Iroshan 2019-10-16 20:52:59 UTC
This problem became apparent when I installed Gnome-Software today to check it out on my Fedora minimal installation I have been using for the past six months.
Never have I ever had any issues with the 'dnf upgrade'. Never have I ever needed to check whether the fwupd was running or not.

Comment 2 Máté Wierdl 2019-10-18 03:04:43 UTC
After reading similar reports, I did  

sudo mkdir /var/cache/fwupd

and rebooted. The problem disappeared. Probably less global restart would be also enough instead of the reboot.

Comment 3 Asiri Iroshan 2019-10-18 18:47:16 UTC
(In reply to Máté Wierdl from comment #2)
> After reading similar reports, I did  
> 
> sudo mkdir /var/cache/fwupd
> 
> and rebooted. The problem disappeared. Probably less global restart would be
> also enough instead of the reboot.

I did that and it worked. That error never came and Gnome-Software works perfectly fine now. Thank you very much.

Comment 4 Ben Cotton 2020-04-30 20:39:10 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2020-05-26 17:59:58 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.