Date: Fri, 9 May 2003 13:10:42 -0500 From: Glenn Johnson <gjohnson@srrc.ars.usda.gov> To: Joe Marcus Clarke <marcus@marcuscom.com> Cc: FreeBSD GNOME Users <gnome@freebsd.org> Subject: Re: gdm-2.4.1.4 not launching Message-ID: <20030509181042.GA82882@node1.cluster.srrc.usda.gov> In-Reply-To: <1052502107.313.24.camel@gyros> References: <20030509160612.GA19809@node1.cluster.srrc.usda.gov> <1052500047.313.14.camel@gyros> <20030509172845.GA76544@node1.cluster.srrc.usda.gov> <1052502107.313.24.camel@gyros>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 09, 2003 at 01:41:47PM -0400, Joe Marcus Clarke wrote: > On Fri, 2003-05-09 at 13:28, Glenn Johnson wrote: > > > On Fri, May 09, 2003 at 01:07:28PM -0400, Joe Marcus Clarke wrote: > > > > > Please stick this patch in /usr/ports/x11/gdm2/files, and rebuild > > > gdm2. Then, make sure gdm debugging is _OFF_, and try running > > > gdm. There should be some XXX messages printed to the console. > > > Please send them to me. > > > > Well, there is nothing to send. Nothing printed out. > > There was only one code change made between 2.4.1.3 and 2.4.1.4, and > those debug messages wrap it. However, g_warning might not be > sufficient for gdm. Try this one. You'll need to turn on full gdm I turned on debugging in gdm.conf but I still do not see any XXX messages. Here is the relevant info from syslog: May 9 12:59:22 node1 gdm[13297]: gdm_main: Here we go... May 9 12:59:22 node1 gdm[13297]: gdm_start_first_unborn_local: Starting :0 May 9 12:59:22 node1 gdm[13297]: gdm_display_manage: Managing :0 May 9 12:59:22 node1 gdm[13297]: Resetting counts for loop of death detection May 9 12:59:22 node1 gdm[13297]: gdm_display_manage: Forked slave: 13317 May 9 12:59:22 node1 gdm[13317]: gdm_slave_start: Starting slave process for :0 May 9 12:59:22 node1 gdm[13317]: gdm_slave_start: Loop Thingie May 9 12:59:22 node1 gdm[13317]: Sending VT_NUM == -1 for slave 13317 May 9 12:59:22 node1 gdm[13317]: Sending VT_NUM 13317 -1 May 9 12:59:22 node1 gdm[13297]: Handling message: 'VT_NUM 13317 -1' May 9 12:59:22 node1 gdm[13297]: Got VT_NUM == -1 May 9 12:59:22 node1 gdm[13297]: (child 13317) gdm_slave_usr2_handler: :0 got USR2 signal May 9 12:59:24 node1 gdm[13317]: gdm_server_start: :0 May 9 12:59:24 node1 gdm[13317]: gdm_auth_secure_display: Setting up access for :0 May 9 12:59:24 node1 gdm[13317]: gdm_auth_secure_display: Setting up socket access May 9 12:59:24 node1 gdm[13317]: gdm_auth_secure_display: Setting up network access May 9 12:59:24 node1 gdm[13317]: gdm_auth_secure_display: Setting up access for :0 - 5 entries May 9 12:59:24 node1 gdm[13317]: Sending COOKIE == <secret> for slave 13317 May 9 12:59:24 node1 gdm[13317]: Sending COOKIE 13317 6931f1cec30e450ff56fd371bbde4aa3 May 9 12:59:24 node1 gdm[13297]: Handling message: 'COOKIE 13317 6...' May 9 12:59:24 node1 gdm[13297]: Got COOKIE == <secret> May 9 12:59:24 node1 gdm[13297]: (child 13317) gdm_slave_usr2_handler: :0 got USR2 signal May 9 12:59:25 node1 gdm[13317]: gdm_server_spawn: Forked server on pid 13419 May 9 12:59:25 node1 gdm[13317]: gdm_server_start: Before mainloop waiting for server May 9 12:59:25 node1 gdm[13419]: gdm_server_spawn: '/usr/X11R6/bin/X :0 vt9 -auth /usr/X11R6/share/gnome/gdm/:0.Xauth' May 9 12:59:35 node1 gdm[13297]: (child 13317) gdm_server_alarm_handler: Got SIGALRM, server abort May 9 12:59:35 node1 gdm[13317]: gdm_server_start: After mainloop waiting for server May 9 12:59:35 node1 gdm[13317]: gdm_server_start: Temporary server failure (:0) -- Glenn Johnson USDA, ARS, SRRC Phone: (504) 286-4252 New Orleans, LA 70124 e-mail: gjohnson@srrc.ars.usda.gov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030509181042.GA82882>