Public bug reported:
Binary package hint: gnome-control-center
I'm not sure this is the right package: maybe gnome-session is really
at fault here.
I have an old AMD K7 machine with a probably-dead CMOS battery, so it
often boots up with the hw clock set to the year 2000. I just put
Ubuntu Gutsy (i386) onto it.
After logging in through gdm (or booting from the Gutsy live CD), Ubuntu's
default desktop session pops up a dialog that reads:
"The computer clock appears to be wrong" ... Ignore / Adjust the Clock.
All is well if I select Ignore.
However, selecting adjust fails: You get a dialog that says:
"The configuration could not be loaded
You are not allowed to access the system configuration.
[close]"
After closing the dialog, it just sits there doing nothing, with the
orange background and a mouse cursor, but _nothing_ else. All I can do
is switch to a text console to debug it: gnome-settings-daemon is still
running. Neither x-window-manager nor metacity are running. Maybe
gnome-session is waiting for gnome-settings to exit...
In case it matters, hw is Athlon (original) 650MHz, 256MB RAM, ATI AIW
Radeon 7200 (32MB RAM) plugged into a CRT that supports DDC properly, so
that's all good. IDE hard drive, XFS root filesystem (yes, I had to
install grub manually). An ne2kpci ethernet card is installed, but
NetworkManager doesn't even try to bring it up because it can't detect
whether there is a link. (This is a separate bug that I'll report...)
So the machine has eth0 UP BROADCAST RUNNING MULTICAST, but with no IP.
netstat doesn't show any socket activity, so I don't think anything's
just waiting for a net timeout.
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
"clock appears to be wrong" dialog prevents gnome session from starting
https://bugs.launchpad.net/bugs/175960
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
