Public bug reported:

On Ubuntu 26.04 LTS, performing a firmware update with fwupd triggers a
reboot requirement and prompts the user for confirmation:

An update requires a reboot to complete. Restart now? [y/N]:

After the user approves the reboot, the automatic restart fails with the
following error:

GDBus.Error:org.freedesktop.login1.BlockedByInhibitorLock: Operation
denied due to active block inhibitor

Despite this error, manually rebooting the system works without any
issues, and the firmware update is successfully applied after the manual
restart.

Expected behavior

After firmware installation completes, fwupd should be able to initiate
a system reboot successfully without being blocked by an active
inhibitor lock.

Actual behavior

fwupd stages the firmware capsule successfully but fails to reboot the
system automatically due to:

GDBus.Error:org.freedesktop.login1.BlockedByInhibitorLock: Operation denied due 
to active block inhibitor
A manual reboot is required to complete the firmware update process.

loginctl list-sessions:

      SESSION  UID  USER SEAT  LEADER CLASS   TTY  IDLE SINCE
            2  1000 ami  seato 2978   user    tty2 no   -
            3  1000 ami  -     3229   manager -    no   -

      2 sessions listed.

systemd-inhibit --list:
I've captured systemd-inhibit --list at different stages:(refer attached image)

Before Firmware Update:
12 inhibitors listed
2 in block mode: gnome-session-s (shutdown) and gsd-media-keys

After Firmware Update:
11 inhibitors listed
Still 2 in block mode, but now gsd-power and gsd-media-keys

** Affects: gnome-settings-daemon (Ubuntu)
     Importance: Undecided
         Status: New

** Patch added: "systemd-inhibit --list at Before and After Firmware Update"
   
https://bugs.launchpad.net/bugs/2165881/+attachment/5996497/+files/systemd-inhibit-list_image.png

** Description changed:

- On Ubuntu 26.04 LTS, performing a firmware update with fwupd triggers a 
reboot requirement and prompts the user for confirmation:
-  
+ On Ubuntu 26.04 LTS, performing a firmware update with fwupd triggers a
+ reboot requirement and prompts the user for confirmation:
+ 
  An update requires a reboot to complete. Restart now? [y/N]:
-  
- After the user approves the reboot, the automatic restart fails with the 
following error:
-  
- GDBus.Error:org.freedesktop.login1.BlockedByInhibitorLock: Operation denied 
due to active block inhibitor
-  
- Despite this error, manually rebooting the system works without any issues, 
and the firmware update is successfully applied after the manual restart.
+ 
+ After the user approves the reboot, the automatic restart fails with the
+ following error:
+ 
+ GDBus.Error:org.freedesktop.login1.BlockedByInhibitorLock: Operation
+ denied due to active block inhibitor
+ 
+ Despite this error, manually rebooting the system works without any
+ issues, and the firmware update is successfully applied after the manual
+ restart.
  
  Expected behavior
  
  After firmware installation completes, fwupd should be able to initiate
  a system reboot successfully without being blocked by an active
  inhibitor lock.
  
  Actual behavior
  
  fwupd stages the firmware capsule successfully but fails to reboot the
  system automatically due to:
  
  GDBus.Error:org.freedesktop.login1.BlockedByInhibitorLock: Operation denied 
due to active block inhibitor
  A manual reboot is required to complete the firmware update process.
  
  loginctl list-sessions:
  
-       SESSION  UID  USER SEAT  LEADER CLASS   TTY  IDLE SINCE
-             2  1000 ami  seato 2978   user    tty2 no   -    
-             3  1000 ami  -     3229   manager -    no   -    
-                                                        
-       2 sessions listed.                                     
+       SESSION  UID  USER SEAT  LEADER CLASS   TTY  IDLE SINCE
+             2  1000 ami  seato 2978   user    tty2 no   -
+             3  1000 ami  -     3229   manager -    no   -
+ 
+       2 sessions listed.
  
  systemd-inhibit --list:
- I've captured systemd-inhibit --list at different stages:
+ I've captured systemd-inhibit --list at different stages:(refer attached 
image)
  
  Before Firmware Update:
  12 inhibitors listed
  2 in block mode: gnome-session-s (shutdown) and gsd-media-keys
  
  After Firmware Update:
  11 inhibitors listed
  Still 2 in block mode, but now gsd-power and gsd-media-keys

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/2165881

Title:
  Automatic Reboot Blocked by Inhibitor Lock After Firmware Update
  (Ubuntu 26.04 LTS)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2165881/+subscriptions


-- 
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to