power button configuration broken

[Timo Aaltonen]

I'm not able to suspend the machine anymore by pressing the power button, instead a popup saying the machine will be shut down in 60s appears. The settings for configuring the behaviour is no longer visible in control center. And selecting suspend from the menu now asks for my password.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-settings-daemon 3.38.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
Uname: Linux 5.8.0-28-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 24 16:35:55 2020
InstallationDate: Installed on 2019-10-14 (406 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fi_FI.UTF-8
 SHELL=/bin/zsh
RebootRequiredPkgs:
 gnome-shell
 linux-image-5.8.0-29-generic
 linux-base
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to groovy on 2020-09-29 (56 days ago)

[Launchpad Janitor (janitor)]

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

[Sebastien Bacher (seb128)]

Thank you for your bug report. What hardware configuration are you using?

What's the output of
$ gdbus call --system --dest org.freedesktop.hostname1 --object-path /org/freedesktop/hostname1 --method org.freedesktop.DBus.Properties.Get org.freedesktop.hostname1 Chassis

the logic is to hide the button config if the chassis is vm, tablet or handset

[Timo Aaltonen (tjaalton)]

It's a desktop.

[Sebastien Bacher (seb128)]

what's the output of the gdbus call? 'desktop'?

[Timo Aaltonen (tjaalton)]

yes

[Sebastien Bacher (seb128)]

$ gdbus call --system --dest org.freedesktop.login1 --object-path /org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanSuspend

(and same with Hibernate)

[Timo Aaltonen (tjaalton)]

('challenge',)

for suspend, 'na' for hibernate

but I figured out what was wrong! Udisks2 was hogging cpu because there was a fsck.vfat process lingering for a disk that got removed two weeks ago.. Killing fsck then made udisks normal again and then it all works fine again. Huh...

[Sebastien Bacher (seb128)]

alright, how did you manage to get fsck active for a non existing disk? did you hotswap out the disk while the machine was on? it seems a udisk issue somehow that it's possible to get it stucked

[Timo Aaltonen (tjaalton)]

No it was mounted but fsck.vfat got stuck for some reason, but the sd-card works fine now. Not really sure of what happened in which order..

[Sebastien Bacher (seb128)]

Thanks for the details, I'm going to close it even if it seems like a situation that could be handled better it's not a normal usecase scenario, also logind returning 'challenge' for suspend is weird and would indicate the issue isn't with GNOME components