fwupd running in WSL 2 in Ubuntu-22.04 fails to start

Bug #2036190 reported by Aki Ketolainen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-software (Ubuntu)
New
Undecided
Unassigned

Bug Description

The fwupd systemd service file contains "ConditionVirtualization=!container". This blocks fwupd from starting in WSL 2 Ubuntu-22.04 instance. Modifying the fwupd systemd service file to contain:

# /etc/systemd/system/fwupd.service.d/override.conf
[Unit]
ConditionVirtualization=

fixes this issue.

WSL 2 is a light-weight utility VM, not a container.

I noticed this issue when starting gnome-software. gnome-software output this error to the terminal:

09:48:20:0857 Gs plugin fwupd took 25.0 seconds to do setup
09:48:21:0461 PK failed to set proxy: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the uid
09:48:21:0462 GsPluginPackageKit failed to set proxies: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror_2dquark.Code3: setting the proxy failed: failed to get the uid
09:48:46:0298 Gs can't reliably fixup error code 20 in domain g-dbus-error-quark
09:48:46:0299 Gs not handling error failed for action refresh: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms)
09:48:46:0299 Gs can't reliably fixup error code 20 in domain g-dbus-error-quark
09:48:46:0299 Gs not handling error failed for action get-updates-historical: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: fwupd 1.7.9-1~22.04.3
Uname: Linux 5.10.16.3-microsoft-standard-WSL2 x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Xpra
Date: Fri Sep 15 13:01:49 2023
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: fwupd
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Aki Ketolainen (akik) wrote :
Revision history for this message
Mario Limonciello (superm1) wrote :

Let me ask - what are you actually going to be able to update from WSL2 that would justify changing this?

Revision history for this message
Aki Ketolainen (akik) wrote :

Mario Limonciello: When I start gnome-software, and fwupd is not running, there is a long timeout (maybe that 25 seconds shown in the error output) before gnome-software is opened.

I don't expect fwupd to do anything in WSL 2, but for some strange reason, it has some dependency to gnome-software.

Revision history for this message
Mario Limonciello (superm1) wrote :

I think that this should be changed in gnome software not to try to start fwupd then when in WSL2.

affects: fwupd (Ubuntu) → gnome-software (Ubuntu)
Revision history for this message
Aki Ketolainen (akik) wrote :

Mario Limonciello: I don't think gnome-software is trying to start fwupd, but it's trying to access it.

Revision history for this message
Aki Ketolainen (akik) wrote :

#linux.09-15.log:22:50 < ioria> libfwupd2 is a dep of gnome-software

Revision history for this message
Aki Ketolainen (akik) wrote :

Mario Limonciello: I think I was wrong and it looks like fwupd is using socket activation and gnome-software starts it.

Revision history for this message
Aki Ketolainen (akik) wrote :

(That is if "ConditionVirtualization=!container" is not blocking fwupd from starting)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.