From owner-freebsd-gnome Fri Aug 9 16: 7: 7 2002 Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5E1C37B400 for ; Fri, 9 Aug 2002 16:07:05 -0700 (PDT) Received: from lilbuddy.antsclimbtree.com (dsl-64-130-38-189.telocity.com [64.130.38.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0797143E65 for ; Fri, 9 Aug 2002 16:07:05 -0700 (PDT) (envelope-from mark@antsclimbtree.com) Received: from amore.antsclimbtree.com (amore.antsclimbtree.com [192.168.1.2]) (authenticated bits=0) by lilbuddy.antsclimbtree.com (8.12.3/8.12.3) with ESMTP id g79Ms4vB002127; Fri, 9 Aug 2002 15:54:04 -0700 (PDT) (envelope-from mark@antsclimbtree.com) Date: Fri, 9 Aug 2002 15:54:03 -0700 Subject: Re: Bug/problem with gdm-2.2.5.5 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Cc: gnome@FreeBSD.org To: Joe Marcus Clarke From: Mark Edwards In-Reply-To: <1028933297.55175.30.camel@shumai.marcuscom.com> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.482) Sender: owner-freebsd-gnome@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday, August 9, 2002, at 03:48 PM, Joe Marcus Clarke wrote: > On Fri, 2002-08-09 at 18:43, Mark Edwards wrote: >> I think I've tracked down a fairly annoying bug with the gdm port. >> >> I install the port on top of the full gnome install, having already >> created >> a gdm user/group with id's of 92 (I need to do this because ID 91 gets >> taken by the mail/mailman port). > > This is no longer needed. I committed a patch to use 92 across the > board. When did you do this? I just cvsup'd my ports tree two days ago, and gdm refused to install unless I first made a user/group gdm with 92 myself. >> >> Upon first boot, it is possible to run gdmconfig from the gdm login panel. >> However, after a change is made to the configuration, running gdmconfig >> results in a freeze which requires killing the gdmconfig process from >> another machine. >> >> What seems to be happening is gdmconfig is changing this line from >> gdm.conf: >> >> Willing=/usr/X11R6/etc/gdm/Xwilling >> >> to: >> >> Willing= >> >> If that config line is blank, gdmconfig will crash. If I replace the line >> with the original, gdmconfig boots again, but changing the configuration >> results in the line getting messed-up again. >> >> This didn't used to happen with an earlier version of the port. Is this >> just a bug in gdm? Is this a bug in the port? > > My Willing line is blank, and I don't see any problems. How do you > start gdm? From my /etc/ttys: ttyv8 "/usr/X11R6/bin/gdm -nodaemon" xterm on I've also been able to crash gdmconfig by changing GtkRC=/usr/X11R6/share/gnome/../themes/Default/gtk/gtkrc to GtkRC=/usr/X11R6/share/gnome/../themes/Metal/gtk/gtkrc Changing it back to "Default" stopped the crashing. I don't know what could be different on my end, but this stuff is 100% repeatable. -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message