Bug 1548049 - fwupd is continuously running in the background while this is not neccessary
Summary: fwupd is continuously running in the background while this is not neccessary
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fwupd
Version: 27
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-22 15:27 UTC by degeneloy
Modified: 2018-02-22 21:33 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-02-22 21:33:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description degeneloy 2018-02-22 15:27:50 UTC
Description of problem:
Fwupd is continuously using RAM as a background daemon, while this is not really necessary to run the daemon unless there are updates to be installed.

Version-Release number of selected component (if applicable):
client version:	0.9.7
daemon version:	0.9.7
compile-time dependency versions
	appstream-glib:	0.7.2
	gusb:	0.2.11

Expected results:
It would probably be preferred to use systemd timers to run the fwupdmgr utilities once in a while, to check for updates and install them. 

Additional information:
These utilities automatically start the daemon, so it would be necessary to shutdown the daemon afterwards.

Comment 1 Richard Hughes 2018-02-22 15:58:06 UTC
How would we do hardware hotplug?

Comment 2 degeneloy 2018-02-22 16:38:38 UTC
Can a generic udev rule start the daemon at a hotplug event? Or would it need to be running before the hotplug events occurs because it listens to dbus hotplug events?

Comment 3 Richard Hughes 2018-02-22 21:33:09 UTC
I listens to all kind of hardware, using libusb, gudev and others. This isn't something I really want to discuss on a downstream bugtracker, sorry. If you have an idea please file an upstream issue and we can discuss there.


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