From owner-freebsd-gnome@FreeBSD.ORG Mon Dec 11 19:07:42 2006 Return-Path: X-Original-To: gnome@hub.freebsd.org Delivered-To: freebsd-gnome@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 187E316A415 for ; Mon, 11 Dec 2006 19:07:42 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6548A43F63 for ; Mon, 11 Dec 2006 18:59:40 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kBBJ0ZPD004252 for ; Mon, 11 Dec 2006 19:00:35 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kBBJ0ZuA004251; Mon, 11 Dec 2006 19:00:35 GMT (envelope-from gnats) Date: Mon, 11 Dec 2006 19:00:35 GMT Message-Id: <200612111900.kBBJ0ZuA004251@freefall.freebsd.org> To: gnome@FreeBSD.org From: Micah Cc: Subject: Re: ports/105589: Firefox 2.0 segfaults when saving more than one file per session X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Micah List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Dec 2006 19:07:42 -0000 The following reply was made to PR ports/105589; it has been noted by GNATS. From: Micah To: Joe Marcus Clarke Cc: gnome@freebsd.org, bug-followup@freebsd.org Subject: Re: ports/105589: Firefox 2.0 segfaults when saving more than one file per session Date: Mon, 11 Dec 2006 10:35:34 -0800 Joe Marcus Clarke wrote: > No, it doesn't really help isolate why the problem is happening. It's > just good to know we have a workaround. You should try and find out > what KDE is doing that affects GTK+ or GNOME applications. THAT would > help track down the crash. I've got an email into the KDE maintainer(s) to see if they can shed some light on it. I did notice one thing though. I get the following error on the settings-deamon's terminal right about where Firefox would normally crash. I rebuilt D-Bus (and the QT/Glib bindings for it) with debugging symbols, but that doesn't seem enough to get it to display the backtrace. (gnome-settings-daemon:43599): GLib-GObject-WARNING **: gsignal.c:2271: signal name `new-toplevel_window' is invalid for instance `0x80c6250' process 43620: arguments to dbus_connection_add_filter() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 4954. This is normally a bug in some application using the D-Bus library. D-Bus not compiled with backtrace support so unable to print a backtrace - Micah