View Full Version : Minor annoyance in dbus
Saiha5
January 26th, 2009, 08:09
I am very happy with gnome so far however one minor annoyance ...
After logging in, The gnome splash screen just gets stuck for a minute or so and does not show any desktop items. clicks on other desktop panels etc are responsive but nothing on the desktop itself works ...that's only for about a minute.
I checked logs in /var/log/messages. It says thus ...
Jan 24 20:00:29 rivendell gnome-keyring-daemon[801]: Scheduling hal init retry
Jan 24 20:00:59 rivendell gnome-keyring-daemon[801]: error connecting to D-BUS s
ystem bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such
file or directory
This log keeps repeating over and over. Any idea what is causing this ? ...how to prevent this ?
SirDice
January 26th, 2009, 09:23
Looks like dbus isn't running..
Did you add dbus_enable="YES" to /etc/rc.conf?
Saiha5
January 26th, 2009, 10:26
ok the log regarding socket is gone ... but now something else.
Jan 26 14:49:20 rivendell gnome-keyring-daemon[852]: Scheduling hal init retry
Jan 26 14:49:20 rivendell gnome-keyring-daemon[852]: Couldn't unlock login keyring with provided password
Jan 26 14:49:20 rivendell gnome-keyring-daemon[852]: Failed to unlock login on startup
Jan 26 14:49:22 rivendell seahorse-agent[880]: DNS-SD initialization failed: Daemon not running
Jan 26 14:49:24 rivendell console-kit-daemon[855]: GLib-CRITICAL: g_hash_table_lookup: assertion `hash_table != NULL' failed
Jan 26 14:49:24 rivendell console-kit-daemon[855]: GLib-CRITICAL: g_hash_table_destroy: assertion `hash_table != NULL' failed
Jan 26 14:49:50 rivendell gnome-keyring-daemon[852]: failed to initialize a HAL context: (null)
And it still keeps getting stuck for some time with the HAL init log repeating.
so ? .... any idea what is gnome keyring daemon ?
SirDice
January 26th, 2009, 11:41
And it still keeps getting stuck for some time with the HAL init log repeating.
I seem to get that too.. Everything works though..
ale
January 26th, 2009, 11:49
Just guessing...
Is it the same after adding the following lines (if not present) in /etc/rc.conf?avahi_daemon_enable="YES"
avahi_dnsconfd_enable="YES"
What is the output of locate keyring | grep $HOME
Saiha5
January 26th, 2009, 16:13
OK...now I get a warning in Avahi daemon init as such :
Jan 26 20:35:07 rivendell avahi-daemon[664]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
remaining errors remain same.
out put of $ locate keyring | grep $HOME is
locate: database too small: /var/db/locate.database
ale
January 26th, 2009, 16:22
OK...now I get a warning in Avahi daemon init as such :I think that you should install dns/nss_mdns to get rid of the message.
But as it seems avahi is not helping you can skip it.
out put of $ locate keyring | grep $HOME is
locate: database too small: /var/db/locate.databaseThis is because the locate database has not been built.
Run /etc/periodic/weekly/310.locate and try again or run find ~ -name \*keyring\*
Saiha5
January 26th, 2009, 18:12
OK ...now locate shows some output but the errors remain same.
Jan 26 22:36:26 rivendell gnome-keyring-daemon[770]: Couldn't unlock login keyring with provided password
Jan 26 22:36:26 rivendell gnome-keyring-daemon[770]: Failed to unlock login on startup
These messages ...does it mean the user with which I am logging in does not have correct rights ?
ale
January 26th, 2009, 18:16
OK ...now locate shows some outputOoh! :)
And what is the output (as requested above) ?
SirDice
January 26th, 2009, 19:10
I seem to get that too.. Everything works though..
Ah.. I rechecked my system.. Hald wasn't running :r
Weird, hald has been in my /etc/rc.conf for at least a couple of years..
Anyway.. That message (every 30 sec):
Jan 26 19:06:43 williscorto gnome-keyring-daemon[38112]: failed to initialize a HAL context: (null)
Jan 26 19:06:43 williscorto gnome-keyring-daemon[38112]: Scheduling hal init retry
It disappeared after I started hald manually.
IIRC gnome-keyring needs /proc. Add this to /etc/fstab:
proc /proc procfs rw 0 0
Saiha5
January 27th, 2009, 17:35
Ok ...hald log is gone :)...added hald to rc.conf
gnome-keyring block stays. :)
output of locate :
/usr/home/paddy/.icons/gnome-wise/32x32/apps/gnome-keyring-manager.png
/usr/home/paddy/.icons/gnome-wise/32x32/apps/keyring-manager.png
/usr/home/paddy/.icons/gnome-wise/32x32/apps/stock_keyring.png
/usr/home/paddy/.icons/gnome-wise/scalable/apps/gnome-keyring-manager.svg
/usr/home/paddy/.icons/gnome-wise/scalable/apps/keyring-manager.svg
/usr/home/paddy/.icons/gnome-wise/scalable/apps/stock_keyring.svg
these are icons from the gnome theme I installed.
Saiha5
January 27th, 2009, 17:38
the find command shows some more data however as such ...
/home/paddy/.gnome2/keyrings
/home/paddy/.gnome2/keyrings/login.keyring
ale
January 27th, 2009, 17:52
Ok ...hald log is gone :)...added hald to rc.confSo you had hald stopped too?
SirDice
January 27th, 2009, 19:30
gnome-keyring block stays. :)
Did you add /proc to fstab?
Saiha5
January 28th, 2009, 17:06
yes.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.