Date: Mon, 07 Apr 2003 08:52:12 -0700 From: "Kevin Oberman" <oberman@es.net> To: gnome@freebsd.org Subject: Re: Gnome 2.2 failed after port update on CURRENT Message-ID: <20030407155212.E7B325D07@ptavv.es.net> In-Reply-To: Message from "Kevin Oberman" <oberman@es.net> <20030407154803.5E15D5D07@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Multipart_Mon_Apr__7_08:51:20_2003-1 Content-Type: text/plain; charset=US-ASCII Forgot to attach the log. Here it is. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 --Multipart_Mon_Apr__7_08:51:20_2003-1 Content-Type: application/octet-stream Content-Disposition: attachment; filename="startx.log" Content-Transfer-Encoding: 7bit XFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: FreeBSD 5.0 i386 [ELF] Build Date: 06 April 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Mon Apr 7 08:25:06 2003 (==) Using config file: "/etc/X11/XF86Config" (EE) Failed to load module "xie" (module does not exist, 0) (EE) Failed to load module "pex5" (module does not exist, 0) Could not init font path element /usr/X11R6/lib/X11/fonts/bitstream-vera/, removing from list! SESSION_MANAGER=local/puppeteer.es.net:/tmp/.ICE-unix/1049 Error setting value: No database available to save your configuration: Unable to store a value at key '/desktop/gnome/applications/window_manager/default', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /usr/X11R6/etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, ch eck the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Window manager warning: 0 stored in GConf key /apps/metacity/general/num_workspaces is not a reasonable number of workspaces, current maximum is 32 ** (gnome-panel:1070): WARNING **: Unable to load panel stock icon 'go' (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (gnome-panel:1070): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 729 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed (nautilus:1072): Eel-WARNING **: GConf error: No database available to save your configuration: Unable to store a value at key '/apps/nautilus/preferences_version', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /usr/X11R6/etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitr (nautilus:1072): Eel-WARNING **: GConf error: No database available to save your configuration: Unable to store a value at key '/apps/nautilus/sound_state', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /usr/X11R6/etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As al (nautilus:1072): Eel-WARNING **: GConf error: No database available to save your configuration: Unable to store a value at key '/apps/nautilus/preferences/start_with_toolbar', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /usr/X11R6/etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in (nautilus:1072): Eel-WARNING **: GConf error: No database available to save your configuration: Unable to store a value at key '/apps/nautilus/preferences/start_with_status_bar', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /usr/X11R6/etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" Window manager warning: Lost connection to the display ':0.0'; most likely the X server was shut down or you killed/destroyed the window manager. X connection to :0.0 broken (explicit kill or server shutdown). The application 'gnome-panel' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. The application 'nautilus' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. xinit: connection to X server lost. Window manager warning: 0 stored in GConf key /apps/metacity/general/num_workspaces is not a reasonable number of workspaces, current maximum is 32 Window manager error: Unable to open X display :0.0 --Multipart_Mon_Apr__7_08:51:20_2003-1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030407155212.E7B325D07>