** Description changed:

  Ptyxis on 26.04 introduced new feature from upstream
  https://gitlab.gnome.org/chergert/ptyxis/-/merge_requests/123#note_2569421
  
  The ptyxis will create a systemd inhibitor to block shutdown process
  from all users including privileged users.
- 
  
  Step to reproduce:
  
  1. Launch a ptyxis terminal
  2. run a random foreground command such as "less or top"
  3. observe result of command "systemd-inhibitor --list" as below to confirm a 
inhibitor been created
  user   1000 user 4811 gnome-session-s    shutdown          user   session 
inhibited    block
  
  4. trigger a critical thermal zone by following command in a root console
  "echo 200000 > /sys/class/thermal/thermal_zone0/emul_temp"
  Please note that the critical temperature may be varied per OEM bios setup
  
- 
  Expected result:
  The system should perform emergency shutdown immediately due to critical 
temperature
  
  Actual result:
  System stays up and running, and following kernel message appears
  kernel: thermal thermal_zone0: acpitz: critical temperature reached
  kernel: reboot: HARDWARE PROTECTION shutdown (Temperature too high)
  
- 
  Summary:
- The system inhibitor created by Ptyxis should not block emergency shutdown or 
from a privileged user. 
+ The system inhibitor created by Ptyxis should not block emergency shutdown or 
from a privileged user.
  Although there is a configuration to turn of the ptyxis behavior not to 
create a system inhibitor, however this is not current default setting.
  
+ Potential fix:
+ [1] The default setting on Fedora is now set to false not to create systemd 
inhibitor as a shorten mitigation
+ 
https://discussion.fedoraproject.org/t/cant-shutdown-with-systemctl-command-anymore/189839
  
- Potential fix:
- [1] The default setting on Fedora is now set to false not to create systemd 
inhibitor
- 
https://discussion.fedoraproject.org/t/cant-shutdown-with-systemctl-command-anymore/189839
+ [2] kernel shutdown command should add parameters to by pass inhibitor
+ blocks as permanent solution.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 26.04
  Package: ptyxis 50.1-1ubuntu2
  ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14
  Uname: Linux 7.0.0-38-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.34.1-0ubuntu0.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Oct 20 11:45:40 2026
  InstallationDate: Installed on 2026-07-06 (106 days ago)
  InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 
(20260423.1)
  SourcePackage: ptyxis
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Ptyxis on 26.04 introduced new feature from upstream
  https://gitlab.gnome.org/chergert/ptyxis/-/merge_requests/123#note_2569421
  
  The ptyxis will create a systemd inhibitor to block shutdown process
  from all users including privileged users.
  
  Step to reproduce:
  
  1. Launch a ptyxis terminal
  2. run a random foreground command such as "less or top"
  3. observe result of command "systemd-inhibitor --list" as below to confirm a 
inhibitor been created
  user   1000 user 4811 gnome-session-s    shutdown          user   session 
inhibited    block
  
  4. trigger a critical thermal zone by following command in a root console
  "echo 200000 > /sys/class/thermal/thermal_zone0/emul_temp"
  Please note that the critical temperature may be varied per OEM bios setup
  
  Expected result:
  The system should perform emergency shutdown immediately due to critical 
temperature
  
  Actual result:
  System stays up and running, and following kernel message appears
  kernel: thermal thermal_zone0: acpitz: critical temperature reached
  kernel: reboot: HARDWARE PROTECTION shutdown (Temperature too high)
  
  Summary:
  The system inhibitor created by Ptyxis should not block emergency shutdown or 
from a privileged user.
  Although there is a configuration to turn of the ptyxis behavior not to 
create a system inhibitor, however this is not current default setting.
  
  Potential fix:
  [1] The default setting on Fedora is now set to false not to create systemd 
inhibitor as a shorten mitigation
  
https://discussion.fedoraproject.org/t/cant-shutdown-with-systemctl-command-anymore/189839
  
  [2] kernel shutdown command should add parameters to by pass inhibitor
- blocks as permanent solution.
+ blocks as permanent solution. such as "systemctl poweroff -i"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 26.04
  Package: ptyxis 50.1-1ubuntu2
  ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14
  Uname: Linux 7.0.0-38-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.34.1-0ubuntu0.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Oct 20 11:45:40 2026
  InstallationDate: Installed on 2026-07-06 (106 days ago)
  InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 
(20260423.1)
  SourcePackage: ptyxis
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2171467

Title:
  Ptyxis creates systemd inhibitor blocks system emergency shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ptyxis/+bug/2171467/+subscriptions


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

Reply via email to