Startup process hungs and does timeout ... and after it works
- From: Ángel Galindo Muñoz <agalindo@xxxxxx>
- Date: Wed, 07 Feb 2007 12:58:11 +0100
When authenticating (gdm) it hungs (about 3 minutes and half) and
finally gnome starts but without themes and showing a message like this
(it's translated from Catalan, sorry):
"An error has happened when starting up the GNOME Settings Daemon.
Some things, like the themes, the sound or background configuration
could not work properly.
The las error message was:
Did not receive a reply. Possible causes include: the remote application
send a reply, the message bus security policy blocked the reply, the
out expired, or the network connection was broken.
Gnome still will try to start upt he configuration daemon next start-up's.
Once I have entered I can change the theme, for example.
But what is really SURPRISING is that if I try to enter Gnome having
disabled networking (/etc/init.d/networking stop) then I can access
without any problem and it works fine. Then I can enable networkig and
my system works fine.
This looks like some issue with "dbus", maybe, ... does anybody know
have any idea?
It it helps and gives clues to find the problem, it's a successful
Ubuntu 6.10 installation on a computer where it works fine. To re-use
the installation on other identical equipments I have divided the data
on the original filesystem ("/"), extracting /var, /tmp, /opt and /home
to their on filesystem. When restoring I find the explained problem.
Mount options of the new filesystem are the same that where on the
original "/" : "defaults". Maybe it has been the dump/restore which
couldn't copy some special files like sockets, ...? I want to tell
again the fact that once I've logged on every thing works.
Can anybody help me, please? Thanks in advance!
- - - - - - - - - -
Ángel Galindo Muñoz
gnome-list mailing list
- Prev by Date: Re: Window List panel - irritating behavior (clicks ignored)
- Next by Date: Password after session is locked
- Previous by thread: Window List panel - irritating behavior (clicks ignored)
- Next by thread: Password after session is locked