Unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value

[Norbert]

Steps to reproduce:
1. Have Ubuntu 18.04 LTS installed with GNOME desktop
2. Click Power Off button or physical ACPI Power Button and see window with default 60 seconds timeout "The system will power off automatically in 60 seconds"
3. Try to set lower or higher timeout value anywhere (in `dconf`, `gsettings`, etc.)

Expected results:
User is able to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value.

Actual results:
User is unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value.

Note: problem was first described on AskUbuntu ( https://askubuntu.com/q/1057271/66509 ).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.2-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 18 22:42:50 2018
DisplayManager: gdm3
GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-04-28 (81 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

There is an existing bug report roughly about this in:
https://bugzilla.gnome.org/show_bug.cgi?id=790128

[Rael Gugelmin Cunha (rael-gc)]

Bug was closed (not implemented) in Gnome Gitlab: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/369

[Rael Gugelmin Cunha (rael-gc)]

@vanvugt: Not sure if I'm missing something, but the bug was not fixed in Gnome, just closed.

[Daniel van Vugt (vanvugt)]

We know. That's just a Launchpad bug where it doesn't know the difference.

[Rael Gugelmin Cunha (rael-gc)]

Sorry if I'm being naughty, but on this case the proper status should not be "Won't fix"?

[Daniel van Vugt (vanvugt)]

You are absolutely right. See bug 701186 :)

[Daniel van Vugt (vanvugt)]

"Won't Fix" because that's upstream's position on this right now.