the phone-home register

fwupd

What fwupd sends out of your computer by default, when, to whom, and the switch that stops it, version by version, with how we know.

The answer

Read in its unit files, Ubuntu's packaging and the firmware service's documents, not wire-checked: where fwupd is installed (Ubuntu 26.04's desktop and server metapackages recommend it), its package enables fwupd-refresh.timer, which runs every hour, with a random delay of up to an hour and not inside containers, and downloads the Linux Vendor Firmware Service's metadata from cdn.fwupd.org only when a refresh is due (how often, we did not read); systemctl disable --now fwupd-refresh.timer stops it, and you then hear of firmware updates, security ones included, only when you refresh by hand.

Builds and versions

the distro's package fwupd 2.1.1-1ubuntu3.1On by default?yes · read in its unit files, its packaging and the firmware service's documentsMeasured here?no · read in codeDate checked (UTC)2026-10-10
Version
2.1.1-1ubuntu3.1 · the Ubuntu 26.04 package
Where the evidence came from
Ubuntu 26.04 desktop, x86-64 (a machine of ours, not a stock install)
On by default?
yes · read in its unit files, its packaging and the firmware service's documents
Measured here?
no · read in code
Date checked (UTC)
2026-10-10
Why we say so
the refresh unit, its timer, the build file that installs it and the default remote read at tag 2.1.1; Ubuntu's packaging at 2.1.1-1ubuntu3.1 and debhelper's handling of units; the firmware service's privacy page read 2026-10-10

Each call out

metadata refresh · 2.1.1-1ubuntu3.1

Version · build
2.1.1-1ubuntu3.1 · the Ubuntu 26.04 package · Ubuntu 26.04 desktop, x86-64 (a machine of ours, not a stock install) · the distro's package fwupd 2.1.1-1ubuntu3.1
Sends by default
yes · read in its unit files, its packaging and the firmware service's documents
Kind
checks
Trigger
on its own
When
Its timer runs fwupdmgr refresh every hour, with a random delay of up to an hour, except inside containers; the refresh downloads the metadata of the Linux Vendor Firmware Service (LVFS) from cdn.fwupd.org. How often a run finds the metadata old enough to download again was not read. Not wire-checked.
Where
update service · cdn.fwupd.org
What it sends
a download of the firmware service's metadata (request)
The vendor's stated purpose
“Refresh fwupd metadata and update motd” — the unit's own Description line at 2.1.1 (quoted whole), read 2026-10-10
Grade and method
read · the refresh unit, its timer, the build file that installs it and the default remote read at tag 2.1.1; Ubuntu's packaging at 2.1.1-1ubuntu3.1 and debhelper's handling of units; the firmware service's privacy page read 2026-10-10 · read 2026-10-10
Receipts
the refresh unit · the firmware service's privacy page · the package · the refresh timer: hourly, with a random delay, not in containers · the build installs the timer · the default remote's metadata address · the default remote is installed switched on · Ubuntu's packaging leaves debhelper's unit handling at its default · debhelper (13.31ubuntu1, Ubuntu 26.04) enables every installed unit that has an install section · Ubuntu 26.04's desktop metapackage recommends fwupd · and so does its server metapackage

The switch

disable fwupd-refresh.timer

Accepted values
disabled
What it is
a systemd timer
Where it must be set
systemctl disable --now fwupd-refresh.timer · turn them off
Also turns off
automatic discovery of firmware updates
What turning it off costs
you no longer hear about firmware updates, security fixes included, until you refresh by hand
Proof
documented behaviour of systemd; not tested by us
For the call
metadata refresh · 2.1.1-1ubuntu3.1

Listens beyond the machine, and other cloud features

Listens beyond the machine by default

  • n/a · a system service: not a server you reach (2.1.1-1ubuntu3.1 the Ubuntu 26.04 package)

Other cloud features

None found.

What it leaves on disk

Nothing we know of.

Brings in, and installed for you by

None on the register.

Credit

None recorded.

Vendor documents it? · public discussion

Vendor documents it?

Public discussion

History

No dated changes yet.

Not yet checked

Nothing named.