Re: problems restarting gnome



If you ctl-alt-backspace, you are killing the Xserver ... so Gnome doesn't have a chance to shutdown gracefully. Thus, there are some daemon processes left running, but unattached to anything. Then when Gnome attempts to restart, it can't run "new" daemon processes because the old ones are hogging all the appropriate sockets and resources.

Does this happen if you exit Gnome the "normal" way?

don draikes com wrote:

Hello,

I just compiled garnome 2.8.0.3 onto a fedora core 2 system yesterday.

I compiled the desktop, geektoys, bootstrap, hacker-tools and office
groups.

The first time I start gnome from a user's home directory, it starts
fine, and I can get gnopernicus to work.
Once I use <ctrl+alt+backspace> to exit gnome, I cannot restart it.

I get an error (see the log file following).

Any suggestions would be greatly appreciated.

---- start of log file ----
Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.7
Build Operating System: Linux 2.4.21-14.ELsmp i686 [ELF] Current Operating System: Linux oasis.draikes.com 2.6.8-1.521spk #1 Tue Aug 17 05:32:04 UTC 2004 i686
Build Date: 28 September 2004
Build Host: tweety.build.redhat.com

	Before reporting problems, check http://wiki.X.Org
	to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.8-1.521spk (root wb2flw octothorp org) (gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Tue Aug 17 05:32:04 UTC 2004 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/Xorg.0.log", Time: Thu Oct 28 19:55:51 2004
(==) Using config file: "/etc/X11/xorg.conf"

Bonobo accessibility support initialized
GTK Accessibility Module initialized
SESSION_MANAGER=local/oasis.draikes.com:/tmp/.ICE-unix/5418
GetModeLine - scrn: 0 clock: 94500
GetModeLine - hdsp: 1024 hbeg: 1072 hend: 1168 httl: 1376
             vdsp: 768 vbeg: 769 vend: 772 vttl: 808 flags: 5
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized

**********************
* SCREEN READER CORE *
**********************

Bonobo accessibility support initialized
GTK Accessibility Module initialized

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: You are using at least one voice witout markers

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to register the callback

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter

(srcore:5513): gnopernicus-WARNING **: Unable to find parameter
The application 'gnome-session' 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.
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).
application finalize called
xinit:  connection to X server lost.
gnopernicus-Message: speech initialization succeded

** ERROR **: Accessibility app error: exception during registry activation from id: IDL:Bonobo/GeneralError:1.0

aborting...
The application 'gnopernicus' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.

** (process:5512): ERROR (recursed) **: Accessibility app error: exception during registry activation from id: IDL:Bonobo/GeneralError:1.0

aborting...

** ERROR **: Accessibility app error: exception during registry activation from id: IDL:Bonobo/GeneralError:1.0

aborting...
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.

** ERROR **: AT-SPI error: during registry activation: Child process did not give an error message, unknown failure occurred

aborting...
Multiple segmentation faults occurred; can't display error dialog

** (process:5508): ERROR (recursed) **: Accessibility app error: exception during registry activation from id: IDL:Bonobo/GeneralError:1.0

aborting...
Multiple segmentation faults occurred; can't display error dialog

---- end of log file ----



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]