System power-key-action reboot not working

jocado · November 26, 2020, 7:53pm

Hi,

On UC20, after having set reboot in system config power-key-action, reboot does when I press the power key. In fact it shuts down gracefully.

# snap get system power-key-action
reboot

Any idea what config file this actually changes, or how it’s implemented. If I can dig into it, I may be able to work out why, and potentially file a bug.

Cheers,
Just

ogra · November 26, 2020, 8:25pm

IIRC it uses logind and writes a config to /etc/systemd/logind.conf.d/

github.com

snapcore/snapd/blob/master/overlord/configstate/configcore/powerbtn.go

// -*- Mode: Go; indent-tabs-mode: t -*-

/*
 * Copyright (C) 2017 Canonical Ltd
 *
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License version 3 as
 * published by the Free Software Foundation.
 *
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 *
 * You should have received a copy of the GNU General Public License
 * along with this program.  If not, see <http://www.gnu.org/licenses/>.
 *
 */

package configcore

This file has been truncated. show original

jocado · November 30, 2020, 11:23am

Thanks for the URL

After looking in the source I realised that some system settings are also prefixed with system. , and I didn’t notice that to start with. I’ve correct that and the config is created. So it’s:

snap get system system.power-key-action

Feels a little awkward, but once you know it it’s fine.

Something else I discovered, as I was setting this as a default via the gadget initially, is will allow you to set arbitrary settings that don’t exist. Whereas if you try that via snap set you get an unsupported system option error.

Not sure if I should raise a bug for that or not.

Cheers,
Just

ogra · November 30, 2020, 12:02pm

it might be a bug, but note that if this bug would be fixed, the first boot seeding would fail once you set a wrong option, so your system would not be able to finish booting and you might have have a very hard time to find out why exactly the boot failed then … it is probably the lesser of two evils to allow setting random unused options…

jocado · November 30, 2020, 12:13pm

Presumably it could refuse to set them without making it fatal too if there desire was there

Anyhow, thanks for help

Cheers, Just

ijohnson · December 3, 2020, 8:56pm

I would say file a bug for this in the snapd project on LP, as @ogra said we may not want to fix it, but perhaps we could add a warning to snap warnings or something less fatal than blocking seeding entirely.

jocado · December 4, 2020, 1:26pm

Created, let’s see: https://bugs.launchpad.net/snapd/+bug/1906830

Cheers,
Just