Fedora 30 doesn't display battery status, function keys don't work properly

vladoski · June 4, 2019, 7:43am

Hello guys,
today my Fedora 30 gives me some headache:

Gnome doesn’t display the battery status (acpi works)
Gnome power manager tool takes a few minutes to open
Fn keys don’t work the first 2 minutes after starting Fedora.
What could be the problem?
Thanks for help!

jhannafin · June 4, 2019, 4:13pm

This happened to me once I installed the newest kernel (5.1.5). When I check journalctl -p warning -b I see this, which seems like the likely culprit.

Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2418]: upower.service: Failed to set up mount namespacing: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2418]: upower.service: Failed at step NAMESPACE spawning /usr/libexec/upowerd: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: upower.service: Failed with result 'exit-code'.
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: Failed to start Daemon for power management.
Jun 04 11:59:32 raijin.simulcast.ove.com gnome-shell[2146]: g_dir_open_with_errno: assertion 'path != NULL' failed
Jun 04 11:59:32 raijin.simulcast.ove.com gnome-shell[2146]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2425]: geoclue.service: Failed to set up mount namespacing: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2425]: geoclue.service: Failed at step NAMESPACE spawning /usr/libexec/geoclue: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: geoclue.service: Failed with result 'exit-code'.
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: Failed to start Location Lookup Service.
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2473]: upower.service: Failed to set up mount namespacing: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2473]: upower.service: Failed at step NAMESPACE spawning /usr/libexec/upowerd: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: upower.service: Failed with result 'exit-code'.
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: Failed to start Daemon for power management.
Jun 04 11:59:32 raijin.simulcast.ove.com gsd-xsettings[2440]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Destination does not exist
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2520]: upower.service: Failed to set up mount namespacing: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2520]: upower.service: Failed at step NAMESPACE spawning /usr/libexec/upowerd: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: upower.service: Failed with result 'exit-code'.
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: Failed to start Daemon for power management.
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2533]: fprintd.service: Failed to set up mount namespacing: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2533]: fprintd.service: Failed at step NAMESPACE spawning /usr/libexec/fprintd: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: fprintd.service: Failed with result 'exit-code'.
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: Failed to start Fingerprint Authentication Daemon.
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2542]: upower.service: Failed to set up mount namespacing: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[2542]: upower.service: Failed at step NAMESPACE spawning /usr/libexec/upowerd: Permission denied
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: upower.service: Failed with result 'exit-code'.
Jun 04 11:59:32 raijin.simulcast.ove.com systemd[1]: Failed to start Daemon for power management.
Jun 04 11:59:33 raijin.simulcast.ove.com systemd[2545]: upower.service: Failed to set up mount namespacing: Permission denied
Jun 04 11:59:33 raijin.simulcast.ove.com systemd[2545]: upower.service: Failed at step NAMESPACE spawning /usr/libexec/upowerd: Permission denied
Jun 04 11:59:33 raijin.simulcast.ove.com systemd[1]: upower.service: Failed with result 'exit-code'.
Jun 04 11:59:33 raijin.simulcast.ove.com systemd[1]: Failed to start Daemon for power management.
Jun 04 11:59:33 raijin.simulcast.ove.com systemd[1]: upower.service: Start request repeated too quickly.
Jun 04 11:59:33 raijin.simulcast.ove.com systemd[1]: upower.service: Failed with result 'exit-code'.
Jun 04 11:59:33 raijin.simulcast.ove.com systemd[1]: Failed to start Daemon for power management.

All that said, I’m a bit at a loss of what to do from here to fix it. Maybe someone else has some insight?

jhannafin · June 4, 2019, 4:39pm

There was another related topic that fixed this for me. Downgrading snapd one version solved all these problems, including the battery status.

https://discussion.fedoraproject.org/t/slow-sudo-execution-since-snapd-update/74687?u=jhannafin

vladoski · June 4, 2019, 7:13pm

Yep that was the problem. I’ve removed snapd.
https://bugzilla.redhat.com/show_bug.cgi?id=1708991

github.com/snapcore/snapd

data/selinux: permit init_t to remount snappy_snap_t

snapcore:master ← bboozzoo:bboozzoo/selinux-init-remount-snap

opened 07:18AM - 04 Jun 19 UTC

bboozzoo

+43 -0

Systemd services that get a new mount namespace on startup fail due to SELinux …blocking system from remounting /var/lib/snapd/snap into the new mount ns. Since we cannot declare fs_type() and generate contexts through genfscon outside of core policy, add an explicit permission for init_t. Corresponding denial: ``` type=AVC msg=audit(1559625610.991:67): avc: denied { remount } for pid=578 comm="(resolved)" scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:snappy_snap_t:s0 tclass=filesystem permissive=0 ``` Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1708991 cc @Conan-Kudo

soheshts · June 17, 2019, 5:50pm

Thanks, upgrading snapd to 2.39.1-1.fc30
fixed the issues in my case.