Closed kenvandine closed 12 months ago
It seems like this isn't covered by the desktop
interface. The only interface that partially allows access to org.gnome.SessionManager
is screen-inhibit-control
, which gives access to Inhibit
and Uninhibit
.
We'd still be able to reboot using org.freedesktop.login1.Manager
though (but this way the user won't see a confirmation dialog). Access to that is already provided by fwupd
i have a similar issue:
it appears that i am unable to apply a firmware update.
although i am guessing such a program like firmware updater would require elevated permissions?
i tried opening it with sudo in the hopes that might bypass any permission issues however when trying to launch it with sudo i was greeted with:
mkdir: cannot create directory ‘/run/user/0’: Permission denied unable to connect to D-Bus: Failed to execute child process “dbus-launch” (No such file or directory)
Reboot is failing for me due to this denial:
2023-03-29T09:36:21.844452-04:00 lifebook dbus-daemon[1835]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/SessionManager" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name="org.gnome.SessionManager" pid=4948 label="snap.firmware-updater.firmware-updater-app" peer_pid=1991 peer_label="unconfined"