Bug 1399539

I can confirm this issue as well. However, my issues occur both on and off the RH network.

Jan 13 12:29:00  polkitd[1057]: /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)
Jan 13 12:29:00  polkitd[1057]: Error evaluating authorization rules

The system will hang for several minutes at login (gdm); or, if logged in, the terminal hangs for several minutes at any root or sudo operation. I have also set selinux to permissive mode, and it does not seem to ameliorate the issue (although I have not fully tested this). The problem will go away after a full restart of the system, but invariably returns after time. It is especially aggravated after a laptop dock (inserting laptop into the dock).

When the issue is in effect, there are quite a few timeout issues with gnome shell, as well. In addition to the gnome freezes, any operation regarding suspending, hibernating, or shutdown are also unavailable:

Jan 13 18:14:56  gnome-shell[1956]: JS ERROR: Error getting systemd inhibitor: Gio.IOErrorEnum: Timeout was reached
                                                     LoginManagerSystemd<.inhibit/<@resource:///org/gnome/shell/misc/loginManager.js:170
Jan 13 18:14:56  gnome-shell[1956]: JS ERROR: Error getting systemd inhibitor: Gio.IOErrorEnum: Timeout was reached
                                                     LoginManagerSystemd<.inhibit/<@resource:///org/gnome/shell/misc/loginManager.js:170
Jan 13 18:14:56  gnome-shell[1956]: JS ERROR: Error getting systemd inhibitor: Gio.IOErrorEnum: Timeout was reached
                                                     LoginManagerSystemd<.inhibit/<@resource:///org/gnome/shell/misc/loginManager.js:170


4.9.3-200.fc25.x86_64 (as well as later 4.8 kernels)

polkit-libs-0.113-5.fc24.x86_64
polkit-pkla-compat-0.1-7.fc24.x86_64
polkit-0.113-5.fc24.x86_64

rpm-plugin-systemd-inhibit-4.13.0-6.fc25.x86_64
systemd-bootchart-231-2.fc25.x86_64
python-systemd-doc-232-1.fc25.x86_64
systemd-pam-231-12.fc25.x86_64
systemd-container-231-12.fc25.x86_64
systemd-231-12.fc25.x86_64
systemd-libs-231-12.fc25.x86_64
systemd-udev-231-12.fc25.x86_64
python3-systemd-232-1.fc25.x86_64
oci-systemd-hook-0.1.4-4.git15c2f48.fc25.x86_64

This seems to be particularly apparent when I have docker running (docker-1.12.6-4.gitf499e8b.fc25.x86_64) and 'oc cluster up' with the openshift origin binary running (oc v1.5.0-alpha). I'll need to isolate if either of these causes an issue.

To me it usually happens with heavy libvirt activity.

Still happening on:
[ykaul@ykaul lago]$ rpm -qa |grep -E "kernel|systemd|pplokit"
systemd-pam-231-12.fc25.x86_64
python3-systemd-232-1.fc25.x86_64
kernel-core-4.9.9-200.fc25.x86_64
systemd-udev-231-12.fc25.x86_64
libreport-plugin-kerneloops-2.8.0-1.fc25.x86_64
systemd-libs-231-12.fc25.x86_64
kernel-core-4.9.7-201.fc25.x86_64
python2-systemd-232-1.fc25.x86_64
kernel-modules-4.9.8-201.fc25.x86_64
systemd-devel-231-12.fc25.x86_64
kernel-headers-4.9.9-200.fc25.x86_64
abrt-addon-kerneloops-2.9.0-1.fc25.x86_64
systemd-bootchart-231-2.fc25.x86_64
systemd-231-12.fc25.x86_64
kernel-4.9.7-201.fc25.x86_64
kernel-4.9.8-201.fc25.x86_64
systemd-container-231-12.fc25.x86_64
kernel-tools-libs-4.9.9-200.fc25.x86_64
kernel-core-4.9.8-201.fc25.x86_64
kernel-modules-4.9.9-200.fc25.x86_64
oci-systemd-hook-0.1.4-4.git15c2f48.fc25.x86_64
python-systemd-doc-232-1.fc25.x86_64
kernel-modules-4.9.7-201.fc25.x86_64
kernel-4.9.9-200.fc25.x86_64
rpm-plugin-systemd-inhibit-4.13.0-6.fc25.x86_64
kernel-tools-4.9.9-200.fc25.x86_64

I was seeing the same messages.  It would take 5 minutes to start up a VM (libvirt) and 1 minute just to log into my laptop.  After seeing Chris Ryan's response, I uninstalled docker, deleted /var/lib/docker, and re-installed docker.  My laptop has been trouble free since.

FWIW, I started noticing the performance issues when I ran low on disk space on my root partition.  I'm not sure if this has any pertinence to the issue though.

Thanks for the advice, Michael. I checked my root partition (50G), and it was 73% used, mostly docker-image related. Once I deleted the images and /var/lib/docker, the usage went down to 25%, a considerable amount. I also reinstalled docker for good measure after deleting /var/lib/docker. 

Will run some tests and get back with some more information. Thank you!

(In reply to Chris Ryan from comment #6)
> Thanks for the advice, Michael. I checked my root partition (50G), and it
> was 73% used, mostly docker-image related. Once I deleted the images and
> /var/lib/docker, the usage went down to 25%, a considerable amount. I also
> reinstalled docker for good measure after deleting /var/lib/docker. 
> 
> Will run some tests and get back with some more information. Thank you!

I don't think I've had my root partition full - probably around the above number as well. I've removed Docker anyway and /var/lib/docker + other stuff. I'll monitor it as well.

(In reply to Yaniv Kaul from comment #7)
> (In reply to Chris Ryan from comment #6)
> > Thanks for the advice, Michael. I checked my root partition (50G), and it
> > was 73% used, mostly docker-image related. Once I deleted the images and
> > /var/lib/docker, the usage went down to 25%, a considerable amount. I also
> > reinstalled docker for good measure after deleting /var/lib/docker. 
> > 
> > Will run some tests and get back with some more information. Thank you!
> 
> I don't think I've had my root partition full - probably around the above
> number as well. I've removed Docker anyway and /var/lib/docker + other
> stuff. I'll monitor it as well.

I've had enough space, and I've bumped into the issue still.
I have two clues:
1. It only happens when I'm connected to RH network - via LAN or VPN. It doesn't happen otherwise. 
2. I suspect it happens on network changes - and I do run dnsmasq (well, libvirt does) when I run VMs on my laptop. I'm using 192.168.20x.y networks there (IPv4 and IPv6 networks)

I don't have good enough evidence for the 2nd item just yet.

Noticed a (new?) issue today - don't think it's related:
2 17:49:38 ykaul.tlv.redhat.com tracker-extract[2765]: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.

So I am continuing to see the hangs with libvirt.  It would take minutes to start a VM and I would have to reboot to get it back where I am not utterly frustrated with my system. I found this bug where people were reporting similar symptoms: https://bugzilla.redhat.com/show_bug.cgi?id=1171923 that pointed to sssd.  While my system was exhibiting the hangs, I restarted sssd and it went away.  I am going to try to install the recommended version of sssd and will report back here if I no longer see hangs.

I am no longer seeing hangs

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.

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.

Cloned into bug 1539197 against Fedora 27 as this one can't be reopened.