Policy kit daemon fails to start due to Timeout
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 4 of 4
  1. #1
    Join Date
    Mar 2012
    München, Deutschland

    Question Policy kit daemon fails to start due to Timeout

    I had very strange error after I upgraded my Fedora 27 (rawhide). After upgrading, and rebooting, login stalls forever. This seems to happen when polkitd could not be started by systemd.

    It appeared similar to this:
    polkit.service operation timed out. Terminating.
    systemd[1]: Failed to start Authorization Manager.
    Job for polkit.service failed. See 'systemctl status polkit.service' and 'journalctl -xn' for details.
    So, what I did (since nothing good happened while entering init=/bin/bash in kernel command line in GRUB2 menu), I de-installed polkit package. Because of dependencies, it de-installed most of gnome and some "other" packages.

    After rebooting, I was able to get to normal run level 3 (and I have all 6 terminals), but network would not work. It'll show ONLY IPV6 on ETH (ens33 I/F), no sign of Wireless at all. And even giving IPV4 address manually to ETH/ens33, it would not ping wireless router (address which of I know).

    ifconfig command shows something like this:

    ens33  Link encap:Ethernet  HWaddr e8:03:9a:97:61:b1  
              inet6 addr: fe80::ea03:9aff:fe97:61b1/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets: 0 errors:0 dropped:1 overruns:0 frame:0
              TX packets: 0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:  TX bytes:
    lo        Link encap:Local Loopback  
              inet addr:  Mask:
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:1289 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1289 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:114509 (114.5 KB)  TX bytes:114509 (114.5 KB)
    I tried many things, but not able to connect with the host (since my Fedora rawhide is, after all, VM).

    Any suggestions?

    Thank you,

  2. #2
    Join Date
    Sep 2009

    Re: Policy kit daemon fails to start due to Timeout

    This early in the rawhide cycle, I leave the display manager disabled, and boot to multi-user instead of target.
    # systemctl set-default multi-user
    # systemctl disable lightdm
    # reboot
    When you get the terminal after booting, login as your normal user and run startx. When there fatal errors, like a broken polkit, you usually come back to a terminal. In the current situation, I'm logging in as root and running dnf upgrade until I see a new polkit being installed. There's not much point in trying to run x, or wayland, until that is fixed.