linux ubuntu 9.10 broken

[alin19]

i have a stupid outlet that restarted my laptop several time when he was starting, now my ubuntu has a lot of problems, when he starts i get some errors:

the default gnome power manager has not been installed, contact system administrator;


there was an error while it was saving or loading configuration fr evolution-alarm-notify, some of your configuration settings may not work properly;

and when i press details :

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details — 1: Could not send message to GConf daemon: Message did not receive a reply (timeout by message bus))

now i'm posting from that ubuntu,but a lot of things are looking different and some does not work, the tot bar with clock, shutdown,accesories is missing, desktop is black ,

:(

can i fix this? or i have to reinstall? i have try to start another kernel but same problem,

[blazemore]

The easiest thing is to make a new user.

[gordontytler]

I am not familiar with linux.

I had the same problem after upgrading to Ubuntu 9.10. It was fixed by creating a new user. I found out the hard way that the correct way to do this is as root with command adduser --ingroup original-user new-user

I subsequently discovered that the original user can be fixed by deleting these directories in /home/original-user
.dbus
.gconf
.gconfd
.gnome2
.gnome2_private

[SandmanCL]

I am not familiar with linux.

I had the same problem after upgrading to Ubuntu 9.10. It was fixed by creating a new user. I found out the hard way that the correct way to do this is as root with command adduser --ingroup original-user new-user

I subsequently discovered that the original user can be fixed by deleting these directories in /home/original-user
.dbus
.gconf
.gconfd
.gnome2
.gnome2_private

Thanks :) Very informative first posting !

[zoroko]

I am not familiar with linux.

I had the same problem after upgrading to Ubuntu 9.10. It was fixed by creating a new user. I found out the hard way that the correct way to do this is as root with command adduser --ingroup original-user new-user

I subsequently discovered that the original user can be fixed by deleting these directories in /home/original-user
.dbus
.gconf
.gconfd
.gnome2
.gnome2_private

Worked on my girlfriends laptop. thanks! I didn't realize it was such an easy fix. I wonder how it all got screwed up anyway from the update. I've done updates on my laptop as well and havn't encountered the problem.. weird.

[susanw]

Just had this same problem, even creating a new user seemed to fail but deleting those files worked a treat. Thank you very much.


Can anyone explain how this works?