Ubuntu
gnome-software package

Device firmware update does not detect AC power

Bug #1811169 reported by Carroarmato0
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
fwupd (Ubuntu)
Invalid
Undecided
Unassigned
gnome-software (Ubuntu)
Confirmed
High
Unassigned

Bug Description

On a freshly installed Ubuntu 18.10 on a Lenovo T580, the Gnome Software center after awhile proposes to install a couple of firmware related updates.

At first the AC wasn't connected, and upon trying to install either of the updates, a popup appears saying that the update cannot continue without the AC being plugged in.

This is so far expected behavior.

But even after connecting the laptop to the AC power supply, the message persists, making it not possible to continue with the firmware updates.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-software 3.30.2-0ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 10 00:59:20 2019
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2019-01-09 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba N/A
 gnome-software-plugin-snap 3.30.2-0ubuntu8
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Carroarmato0 (carroarmato0) wrote :
Revision history for this message
Carroarmato0 (carroarmato0) wrote :

After a reboot, clicking on the Update buttons don't complain about connecting to the AC power.

The options briefly disappear, and then reappear, seemingly as if the options weren't accepted.

But after another reboot, the bios noticed that there were pending updates and went on to apply both of them after 2 reboots.

After the whole procedure the updates don't appear anymore in the Software center, making me believe that it was executed successfully.

I seems that the issue could be closed, unless you would consider this an interaction bug.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Sounds like there are some real problems there
- connecting to power should automatically close/dismiss the warning and let you install the update
- the UI interaction seems at minimal confusing, it shouldn't have applied firmware updates without communicating about it properly

Could you attach the journalctl log from the boot where you had the issue? (or maybe look for gnome-software/fwupd warning/errors in there)

Changed in gnome-software (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

I've reported it upstream on https://gitlab.gnome.org/GNOME/gnome-software/issues/567

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

To me this sounds like it's probably Gnome Software not fwupd.

Changed in fwupd (Ubuntu):
status: New → Invalid
Revision history for this message
Carroarmato0 (carroarmato0) wrote :

Sorry for the delay in following up.

Based on the logs I've checked, fwupd has been behaving correctly, no where in the various boot logs have I seen it crash or output anything that would look like an issue.

However, I've been seeing many issues from Gnome Software.

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

Added fwupd for reference

Revision history for this message
Carroarmato0 (carroarmato0) wrote :

Maybe a small detail which may have an impact: the laptop has SecureBoot enabled by default.
During the installation, the Ubuntu installer made me go about setting a password.

After installing Virtualbox I noticed that I had to do some extra steps into signing the compiled kernel module.

I have followed the procedures correctly, but afterwards decided to turn off Secure Boot just to not wanting to deal with the upgrade hassle in the future.

I don't remember between which boots I disabled SecureBoot and when I started the firmware update successfully.

I do remember the annoyance of the firmware upgrade processes beeping every couple of seconds during the long procedure, in an open workspace environment. Because it's usually a bad idea to terminate a firmware flash right in the middle I had to run away with my "ticking timebomb". But I divert, this has nothing to do with actually setting up the firmware upgrade through Gnome-Software/fwupd.

Sebastien Bacher (seb128)
Changed in gnome-software (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-software (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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