Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora 17/18 > Using Fedora
FedoraForum Search

Forgot Password? Join Us!

Using Fedora General support for current versions. Ask questions about Fedora and it's software that do not belong in any other forum.

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
  #1  
Old 27th June 2012, 08:13 PM
andrew harland Offline
Registered User
 
Join Date: Apr 2010
Posts: 8
linuxchrome
Failure to login on first attemp

I've recently started having a problem logging in FC16 x64: -

On first attempt, end up in loop (can see 'Loading initial ramdisk' for a second time) and then nothing just a blank screen, sometimes Ctrl+Atl+Backspace can break the loop but it's not consistent.

If I wait roughly a minute or so, I see the second 'Loading initial ramdisk', login prompt appears and I can log in no problems.

This has only started happening recently, I'm currently on kernel 3.4.2-1.fc16.x86_64.

I have tried to find a solution, there are a couple of posts (couldn't add URL's, post was denied) but neither of these seem to fit.

I'm no Linux expert, as such I haven't messed around with any settings/policies, simply use yum update; and don't know where to start.

I have got this from the messages log but it may as well be written in DoubleDutch

Jun 26 20:31:21 localhost NetworkManager[1189]: <info> (p32p1): IP6 addrconf timed out or failed.
Jun 26 20:31:21 localhost NetworkManager[1189]: <info> Activation (p32p1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jun 26 20:31:21 localhost NetworkManager[1189]: <info> Activation (p32p1) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jun 26 20:31:21 localhost NetworkManager[1189]: <info> Activation (p32p1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jun 26 20:31:23 localhost dbus[1235]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out
Jun 26 20:31:23 localhost dbus-daemon[1235]: dbus[1235]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out
Jun 26 20:31:23 localhost dbus[1235]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Jun 26 20:31:23 localhost dbus-daemon[1235]: dbus[1235]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Jun 26 20:31:23 localhost dbus-daemon[1235]: process 1235: arguments to dbus_message_set_reply_serial() were incorrect, assertion "reply_serial != 0" failed in file dbus-message.c line 1009.
Jun 26 20:31:23 localhost dbus-daemon[1235]: This is normally a bug in some application using the D-Bus library.
Jun 26 20:31:23 localhost dbus-daemon[1235]: D-Bus not built with -rdynamic so unable to print a backtrace
Jun 26 20:31:23 localhost avahi-daemon[1212]: Disconnected from D-Bus, exiting.
Jun 26 20:31:23 localhost avahi-daemon[1212]: Got SIGTERM, quitting.
Jun 26 20:31:23 localhost NetworkManager[1189]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Jun 26 20:31:23 localhost avahi-daemon[1212]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Jun 26 20:31:23 localhost NetworkManager[1189]: <warn> disconnected by the system bus.
Jun 26 20:31:23 localhost avahi-daemon[1212]: Leaving mDNS multicast group on interface p32p1.IPv4 with address 192.168.0.5.
Jun 26 20:31:23 localhost systemd[1]: systemd-logind.service: main process exited, code=exited, status=1
Jun 26 20:31:23 localhost rtkit-daemon[1839]: Demoting known real-time threads.
Jun 26 20:31:23 localhost dbus-daemon[1235]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Jun 26 20:31:23 localhost rtkit-daemon[1839]: Successfully demoted thread 2056 of process 2049 (/usr/bin/pulseaudio).
Jun 26 20:31:23 localhost rtkit-daemon[1839]: Successfully demoted thread 2055 of process 2049 (/usr/bin/pulseaudio).
Jun 26 20:31:23 localhost rtkit-daemon[1839]: Successfully demoted thread 2054 of process 2049 (/usr/bin/pulseaudio).
Jun 26 20:31:23 localhost rtkit-daemon[1839]: Successfully demoted thread 2049 of process 2049 (/usr/bin/pulseaudio).
Jun 26 20:31:23 localhost rtkit-daemon[1839]: Successfully demoted thread 1846 of process 1838 (/usr/bin/pulseaudio).
Jun 26 20:31:23 localhost rtkit-daemon[1839]: Successfully demoted thread 1845 of process 1838 (/usr/bin/pulseaudio).
Jun 26 20:31:23 localhost rtkit-daemon[1839]: Successfully demoted thread 1844 of process 1838 (/usr/bin/pulseaudio).
Jun 26 20:31:23 localhost rtkit-daemon[1839]: Successfully demoted thread 1843 of process 1838 (/usr/bin/pulseaudio).
Jun 26 20:31:23 localhost rtkit-daemon[1839]: Successfully demoted thread 1838 of process 1838 (/usr/bin/pulseaudio).
Jun 26 20:31:23 localhost rtkit-daemon[1839]: Demoted 9 threads.
Jun 26 20:31:23 localhost systemd[1]: Unit systemd-logind.service entered failed state.
Jun 26 20:31:23 localhost systemd[1]: dbus.service: main process exited, code=killed, status=6
Jun 26 20:31:23 localhost avahi-daemon[1212]: avahi-daemon 0.6.30 exiting.
Jun 26 20:31:23 localhost systemd[1]: accounts-daemon.service: main process exited, code=exited, status=1
Jun 26 20:31:23 localhost systemd[1]: Unit accounts-daemon.service entered failed state.
Jun 26 20:31:23 localhost systemd[1]: Unit dbus.service entered failed state.
Jun 26 20:31:23 localhost gnome-session[1873]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012
Jun 26 20:31:24 localhost pulseaudio[2049]: module-console-kit.c: Unable to subscribe to ConsoleKit signals: org.freedesktop.DBus.Error.Disconnected: Connection is closed
Jun 26 20:31:24 localhost pulseaudio[2049]: module.c: Failed to load module "module-console-kit" (argument: ""): initialization failed.
Jun 26 20:31:24 localhost pulseaudio[2049]: main.c: Module load failed.
Jun 26 20:31:24 localhost pulseaudio[2049]: main.c: Failed to initialize daemon.
Jun 26 20:31:24 localhost dbus-daemon[2104]: dbus[2104]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Jun 26 20:31:24 localhost dbus[2104]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Jun 26 20:31:24 localhost avahi-daemon[2108]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70).
Jun 26 20:31:24 localhost avahi-daemon[2108]: Successfully dropped root privileges.
Jun 26 20:31:24 localhost avahi-daemon[2108]: avahi-daemon 0.6.30 starting up.
Jun 26 20:31:24 localhost dbus[2104]: [system] Successfully activated service 'org.freedesktop.Avahi'

Any help appreciated.
Reply With Quote
 

Tags
attempt, failure, login

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
mysql-cluster-5.1.42 attemp SlowJet Fedora 13 Development Branch 0 2nd January 2010 09:14 AM
GDM Failure after login ctyler2621 Using Fedora 1 28th May 2008 11:22 PM
login failure. FC3. yuvalaviel Using Fedora 8 11th January 2005 03:43 PM


Current GMT-time: 16:09 (Saturday, 18-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

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