Date: Thu, 11 Dec 2003 14:31:21 -0600 From: Jeremy Messenger <mezz7@cox.net> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: freebsd-gnome@freebsd.org Subject: Re: How do I debug the logout session? Message-ID: <oprz09yjid8ckrg5@smtp.central.cox.net> In-Reply-To: <1071172308.749.43.camel@gyros> References: <oprz07uaqw8ckrg5@smtp.central.cox.net> <1071172308.749.43.camel@gyros>
next in thread | previous in thread | raw e-mail | index | archive | help
------------Lz3bZyepUvVUx1X6lYCEHb Content-Type: text/plain; format=flowed; charset=iso-8859-1 Content-Transfer-Encoding: 8bit On Thu, 11 Dec 2003 14:51:48 -0500, Joe Marcus Clarke <marcus@marcuscom.com> wrote: > On Thu, 2003-12-11 at 14:45, Jeremy Messenger wrote: >> I have everything up to date, it's Gnome 2.5.2 and it can't logout. I am >> wondering how can I debug that kind of bug? > > gnome-session is responsible for logging in and out. You might want to > attach gdb to that from a vty and see what happens. Also, check the > ~/.xsession-errors and console for anything useful. There's no ~/.xsession-errors and I don't understand or know what you mean by vty? Attaching the errors.txt is what I get from kill X by manual, but I don't think it will help that much. I tried to add that '--sync' in the .xinitrc like 'exec gnome-session --sync' and no luck. Cheers, Mezz > Joe > >> >> Cheers, >> Mezz -- bsdforums.org 's moderator, mezz. ------------Lz3bZyepUvVUx1X6lYCEHb Content-Disposition: attachment; filename=errors.txt Content-Type: text/plain; name=errors.txt Content-Transfer-Encoding: 8bit (nautilus:883): libgnomevfs-WARNING **: module '/usr/X11R6/lib/gnome-vfs-2.0/mod ules/libmapping.so' returned a NULL handle (gnome-session:847): GLib-GObject-WARNING **: g_object_set_valist: construct pro perty "type" for object `GtkDialog' can't be set after construction Gdk-ERROR **: The program 'gnome-session' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 720 error_code 8 request_code 42 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... X connection to :0.0 broken (explicit kill or server shutdown). 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. 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. The application 'gnome_segv' 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. waiting for X server to shut down ------------Lz3bZyepUvVUx1X6lYCEHb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?oprz09yjid8ckrg5>