+++ This bug was initially created as a clone of Bug #1399539 +++ Started happening for me with Fedora 27, I believe since the upgrade to kernel 4.14. Jan 24 19:36:13 gnome-shell[1779]: JS ERROR: Error getting systemd inhibitor: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Method call timed out LoginManagerSystemd<.inhibit/<@resource:///org/gnome/shell/misc/loginManager.js:176:48 Jan 24 19:35:58 polkitd[789]: Error evaluating authorization rules Jan 24 19:35:58 polkitd[789]: /etc/polkit-1/rules.d/49-polkit-pkla-compat.rules:21: Error: Error spawning helper: Timed out after 10 seconds (g-io-error-quark, 24) rpm -qa |grep -E "kernel|systemd|pplokit" kernel-modules-4.14.11-300.fc27.x86_64 abrt-addon-kerneloops-2.10.5-1.fc27.x86_64 kernel-4.14.13-300.fc27.x86_64 python-systemd-doc-234-3.fc27.x86_64 kernel-headers-4.14.13-300.fc27.x86_64 systemd-234-9.fc27.x86_64 systemd-container-234-9.fc27.x86_64 systemd-udev-234-9.fc27.x86_64 texlive-l3kernel-svn41246-36.fc27.5.noarch libreport-plugin-systemd-journal-2.9.3-1.fc27.x86_64 kernel-core-4.14.8-300.fc27.x86_64 rpm-plugin-systemd-inhibit-4.14.0-2.fc27.x86_64 kernel-4.14.8-300.fc27.x86_64 systemd-bootchart-233-1.fc27.x86_64 python3-systemd-234-3.fc27.x86_64 kernel-modules-4.14.8-300.fc27.x86_64 kernel-core-4.14.13-300.fc27.x86_64 kernel-core-4.14.11-300.fc27.x86_64 libreport-plugin-kerneloops-2.9.3-1.fc27.x86_64 systemd-pam-234-9.fc27.x86_64 kernel-modules-4.14.13-300.fc27.x86_64 kernel-4.14.11-300.fc27.x86_64 systemd-libs-234-9.fc27.x86_64 df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 3.7G 0 3.7G 0% /dev tmpfs 3.7G 68M 3.6G 2% /dev/shm tmpfs 3.7G 2.1M 3.7G 1% /run tmpfs 3.7G 0 3.7G 0% /sys/fs/cgroup /dev/sdc2 226G 19G 206G 9% / tmpfs 3.7G 312K 3.7G 1% /tmp /dev/sdc1 477M 200M 248M 45% /boot /dev/sda1 932G 147G 784G 16% /home tmpfs 748M 20K 748M 1% /run/user/42 tmpfs 748M 5.8M 742M 1% /run/user/1000 /dev/fuse 250G 0 250G 0% /keybase btrfs filesystem df / Data, single: total=32.00GiB, used=17.70GiB System, single: total=32.00MiB, used=16.00KiB Metadata, single: total=2.00GiB, used=454.20MiB GlobalReserve, single: total=47.17MiB, used=0.00B btrfs filesystem df /home Data, RAID1: total=155.00GiB, used=145.74GiB System, RAID1: total=32.00MiB, used=48.00KiB Metadata, RAID1: total=2.00GiB, used=309.78MiB GlobalReserve, single: total=179.66MiB, used=0.00B libvirtd is running but I'm not running any VMs. Neither I use Docker. System hangs after being left unattended. Mouse and keyboard do not work. I had to enable the Magic SysRq key to be able to force reboot the system as nicely as possible. Please let me know if you need any additional information.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.