Arch Linux

you should report this upstream. the option is hardcoded into the code.

http://git.gnome.org/browse/gdm/commit/?id=5407f9fc02494234f5909e3f551e4916e5350850
http://git.gnome.org/browse/gdm/commit/?id=2e6e88a4a47d81eb653da8c98e7166260ff49b1f

So is it a bug with my gdm config? (maybe outdated version?)

what config? don't you see it was added in the code to start with debug? Ask upstream to drop the debug because is slowing down gdm

OK I reported that to the gnome3 bugtrack. Here's the link: https://bugzilla.gnome.org/show_bug.cgi?id=669135

Thanks.

The gnome developers point out that the ConsoleKit and Avahi cannot be started from gdm and waits 20 seconds until it give up and continue loading.
I added avahi daemon to the Daemons in rc.conf but don't know how to fix the ConsoleKit. Any ideas, attaching the latest reboot messages.
Feb 1 20:31:57 localhost dbus[527]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'

Feb 1 20:31:57 localhost dbus[527]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Feb 1 20:31:57 localhost acpid: client connected from 855[0:0]
Feb 1 20:31:57 localhost acpid: 1 client rule loaded
Feb 1 20:31:58 localhost dbus[527]: [system] Activating service name='org.freedesktop.Accounts' (using servicehelper)
Feb 1 20:31:58 localhost dbus[527]: [system] Successfully activated service 'org.freedesktop.Accounts'
Feb 1 20:31:59 localhost avahi-daemon[631]: Registering new address record for fe80::16da:e9ff:fe13:96a9 on eth0.*.
Feb 1 20:32:02 localhost dhcpcd[694]: eth0: leased 192.168.1.65 for 86400 seconds
Feb 1 20:32:02 localhost avahi-daemon[631]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.65.
Feb 1 20:32:02 localhost avahi-daemon[631]: New relevant interface eth0.IPv4 for mDNS.
Feb 1 20:32:02 localhost avahi-daemon[631]: Registering new address record for 192.168.1.65 on eth0.IPv4.
Feb 1 20:32:02 localhost NetworkManager[658]: <info> (eth0): DHCPv4 state changed preinit -> bound
Feb 1 20:32:02 localhost NetworkManager[658]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Feb 1 20:32:02 localhost NetworkManager[658]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
Feb 1 20:32:02 localhost NetworkManager[658]: <info> address 192.168.1.65
Feb 1 20:32:02 localhost NetworkManager[658]: <info> prefix 24 (255.255.255.0)
Feb 1 20:32:02 localhost NetworkManager[658]: <info> gateway 192.168.1.254
Feb 1 20:32:02 localhost NetworkManager[658]: <info> hostname 'tiamat'
Feb 1 20:32:02 localhost NetworkManager[658]: <info> nameserver '192.168.1.254'
Feb 1 20:32:02 localhost NetworkManager[658]: <info> domain name 'home'
Feb 1 20:32:02 localhost NetworkManager[658]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Feb 1 20:32:02 localhost NetworkManager[658]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
Feb 1 20:32:02 localhost NetworkManager[658]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Feb 1 20:32:03 localhost NetworkManager[658]: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Feb 1 20:32:03 localhost NetworkManager[658]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS.
Feb 1 20:32:03 localhost NetworkManager[658]: <info> Activation (eth0) successful, device activated.
Feb 1 20:32:03 localhost NetworkManager[658]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Feb 1 20:32:03 localhost dbus[527]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Feb 1 20:32:03 localhost dbus[527]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 1 20:32:22 localhost rtkit-daemon[765]: Warning: PolicyKit call failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Feb 1 20:32:22 localhost dbus[527]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
Feb 1 20:32:22 localhost accounts-daemon[875]: started daemon version 0.6.15

what are your DAEMONS?
are you using stock initscripts?
paste /etc/pam.d/login

Hello Ionut, my daemons are like:
DAEMONS=(syslog-ng dbus network crond avahi-daemon networkmanager acpid mpd sshd)
The login file you requested:
#%PAM-1.0
auth required pam_securetty.so
auth requisite pam_nologin.so
auth required pam_unix.so nullok
auth required pam_tally.so onerr=succeed file=/var/log/faillog
# use this to lockout accounts for 10 minutes after 3 failed attempts
#auth required pam_tally.so deny=2 unlock_time=600 onerr=succeed file=/var/log/faillog
account required pam_access.so
account required pam_time.so
account required pam_unix.so
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
#password required pam_unix.so sha512 shadow use_authtok
session required pam_unix.so
session required pam_env.so
session required pam_motd.so
session required pam_limits.so
session optional pam_mail.so dir=/var/spool/mail standard
session optional pam_lastlog.so
session optional pam_loginuid.so
-session optional pam_ck_connector.so nox11
-session optional pam_systemd.so

drop network from DAEMONS.

Yeah you were right on that since I was using the networkmanager. But still this is irelevant to the ConsoleKit. Tested and still takes 20secs for timeout.

are you using default initscripts?

Yes

i think it fails to start because /run/ConsoleKit is not created fast enough, even if we have /usr/lib/tmpfiles.d/consolekit.conf in consolekit 0.4.5-2.

try to add mkdir /run/ConsoleKit in rc.local to see if is working.

Could be because of my hardware. 8core + and ssd. I will try and report back. If this is the case should it be reported to somewhere else or here?

did it work?

Nope :( still 20secs
$ cat /var/log/messages.log | grep ConsoleKit
Feb 2 22:10:15 localhost dbus[534]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Feb 2 22:10:40 localhost dbus[534]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out

Could it be a problem with the ConcoleKit package? Where should I report it if that's the case? Is it part of gdm?

Searching around seems to be reports in other distros as well:
https://bugzilla.redhat.com/show_bug.cgi?id=708866

Maybe this post is relative although it is for FreeBSD
http://forums.freebsd.org/archive/index.php/t-4634.html

I played around the various settings in /etc/hosts
That might be the fix.
I made my system not booting at first, to be more exact I made it load but stuck on the debug information from Consolekit..
So I had to ssh to it and remove the debug option and anything related from rc.local

Then I reboot and it was normal! no 20 seconds delay.
I didn't bother looking the logs but seems to be fixed.
I am not sure if it was the hosts file but worth giving it a try.

how does your /etc/hosts look now?

Hello ionut,

Here's the hosts file
cat /etc/hosts
#
# /etc/hosts: static lookup table for host names
#

#<ip-address> <hostname.domain.org> <hostname>
::1 localhost localhost.my.domain
127.0.0.1 localhost localhost.my.domain tiamat tiamat.my.domain

# End of file

and how my rc.local looks like:cat /etc/rc.local
#!/bin/bash
#
# /etc/rc.local: Local multi-user startup script.
#

#/usr/sbin/console-kit-daemon --debug --no-daemon

echo 2 > /sys/module/hid_apple/parameters/fnmode
echo "458856 99" | /usr/sbin/keyfuzz -s -d /dev/input/by-id/usb-Apple__Inc_Apple_Keyboard-event-kbd

what about HOSTNAME from rc.conf ?

Hostname is tiamat

correct way of setting /etc/hosts is

#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost tiamat
::1 localhost.localdomain localhost tiamat

That's how it was before but if its like that the tiamat.localdomain won't resolve.
On the links I posted above they mention it should contain a FQD within hosts file.

I did a reinstallation of dbus as someone mentioned it, something to with machine-id

Other than that I don't know what else could it fix it.

mine doesn't have tiamat.localdomain.

machine-id has sense on systemd.

I don't think I have systemd on my system. (I never explicitly installed it so only if it came as dependency for another package).
I can't check it out now since I am at work - later on afternoon.

I can confirm it's not installed.

everything is fine now no? can i close this?

Yes you can close it.
Thanks for all the suggestions.