Fedora Linux Support Community & Resources Center
Prev Previous Post   Next Post Next
Old 4th April 2017, 07:42 AM
nobody Offline
Registered User
Join Date: Mar 2012
Location: München, Deutschland
Posts: 849
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
          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,
I am nobody, and nobody is perfect, therefore I am perfect!
Reply With Quote

daemon, fails, kit, policy, start, timeout

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Hal Daemon Fails to Start shduff Using Fedora 8 25th November 2013 09:48 PM
Hal daemon fails to start mukiwa Using Fedora 3 9th December 2006 07:49 PM
Timeout error occurred trying to start MySQL Daemon Mat Servers & Networking 1 15th December 2004 01:48 PM
Timeout error occurred trying to start MySQL Daemon Mat Using Fedora 0 22nd November 2004 12:33 AM

Current GMT-time: 14:01 (Monday, 21-08-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat