3

deleted everything in /tmp directory.....

view full story
linux-howto

http://forums.opensuse.org – I wanted to clean up my tmp directory. So I went to the /tmp directory and did sudo rm -r * in /tmp. But now I get error messages when I open an application. For instance, when I try to open nautilus I get: Code: (nautilus:22457): Eel-WARNING **: GConf error:   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 GConf configuration system for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) (nautilus:22457): Eel-WARNING **: GConf error:   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 GConf configuration system for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) GConf warning: failure listing pairs in `/apps/nautilus/preferences': 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 GConf configuration system for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) (nautilus:22457): Eel-WARNING **: GConf error:   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 GConf configuration system for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) and a bunch of other errors. Similar things happen when I try to open yast: Code: An error occurred while loading or saving configuration information for GNOME SuperUser. Some of your configuration settings may not work properly. 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://www.gnome.org/projects/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) 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://www.gnome.org/projects/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) 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://www.gnome.org/projects/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) 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://www.gnome.org/projects/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) 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://www.gnome.org/projects/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) What am I supposed to do now? (Distributions)