From owner-freebsd-gnome@FreeBSD.ORG Mon Oct 9 14:40:57 2006 Return-Path: X-Original-To: freebsd-gnome@freebsd.org 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 AAF0F16A403 for ; Mon, 9 Oct 2006 14:40:57 +0000 (UTC) (envelope-from jlw@team-fatal.com) Received: from dewshu02.webservice-hannover.de (p15181084.pureserver.info [217.160.216.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F00643D6E for ; Mon, 9 Oct 2006 14:40:48 +0000 (GMT) (envelope-from jlw@team-fatal.com) Received: from [192.168.0.2] (p548301B7.dip0.t-ipconnect.de [84.131.1.183]) by dewshu02.webservice-hannover.de (Postfix) with ESMTP id 3516C810FA0 for ; Mon, 9 Oct 2006 16:40:47 +0200 (CEST) Message-ID: <452A5F6E.5070405@team-fatal.com> Date: Mon, 09 Oct 2006 16:40:46 +0200 From: Jacek Lukas Wotka User-Agent: Thunderbird 1.5.0.7 (X11/20061004) MIME-Version: 1.0 To: freebsd-gnome@freebsd.org References: <45274E11.6090004@team-fatal.com> <1160334873.21790.25.camel@shumai.marcuscom.com> In-Reply-To: <1160334873.21790.25.camel@shumai.marcuscom.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: gdm 2.16.1 graphical greeter / configuration-screen crash (CURRENT) X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2006 14:40:57 -0000 Joe Marcus Clarke wrote: > On Sat, 2006-10-07 at 08:49 +0200, Jacek Lukas Wotka wrote: >> hi >> >> i get gdm/xserver crashes when trying to enter the configuration-screen >> in gdm. old configs with enabled graphical greeter produce >> xserverrestarts with standard greeter enabled. >> >> FreeBSD 7.0-CURRENT #1: Mon Oct 2 15:41:46 CEST 2006 >> >> any ideas or any other information needed for that? > > Others have reported this problem as well. I recommend building gdm > with debugging symbols, then setting the following two sysctls: > > kern.coredump > kern.sugid_coredump > > And get a full backtrace from the crash. > > Joe > ok, can you explain this in detail? (especially the "get a full backtrace", not the previous stuff)