From owner-freebsd-gnome@FreeBSD.ORG Sun Jul 4 23:00:54 2010 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9ED41065673; Sun, 4 Jul 2010 23:00:53 +0000 (UTC) (envelope-from barbara.xxx1975@libero.it) Received: from cp-out2.libero.it (cp-out2.libero.it [212.52.84.102]) by mx1.freebsd.org (Postfix) with ESMTP id 85A3A8FC0C; Sun, 4 Jul 2010 23:00:53 +0000 (UTC) Received: from wmail38 (172.31.0.227) by cp-out2.libero.it (8.5.107) id 4C2E04A500139984; Mon, 5 Jul 2010 01:00:52 +0200 Message-ID: <14101673.1065931278284451980.JavaMail.defaultUser@defaultHost> Date: Mon, 5 Jul 2010 01:00:51 +0200 (CEST) From: Barbara To: MIME-Version: 1.0 Content-Type: text/plain;charset="UTF-8" Content-Transfer-Encoding: 7bit X-SenderIP: 87.21.211.5 Cc: gnome@freebsd.org Subject: R: Re: ports/148272: polkit-gnome-authen core dumps when starting gnome X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Barbara List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jul 2010 23:00:54 -0000 > >On 7/4/10 5:00 PM, Barbara wrote: >> >>> On 7/4/10 6:06 AM, Barbara wrote: >>>> >>>>> Synopsis: polkit-gnome-authen core dumps when starting gnome >>>>> >>>>> State-Changed-From-To: open->feedback >>>>> State-Changed-By: marcus >>>>> State-Changed-When: Sun Jul 4 01:37:18 UTC 2010 >>>>> State-Changed-Why: >>>>> You need to compile polkit and polkit-gnome with debugging symbols, then >>>>> provide a backtrace of this crash following the instructions at >>>>> http://www.freebsd.org/gnome/docs/bugging.html . >>>>> >>>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=148272 >>>> >>>> This is what I get after rebuilding also bug-buddy WITH_DEBUG: >>>> http://freebsd-gnome.pastebin.com/NHQeUcqk >>>> >>>> >>> >>> Guys, can you try removing the date/time applet as described in >>> https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/599140 and >>> see if this problem (as well as the slowness) issue goes away? >>> >> >> I've tested removing the clock applet, but it doesn't solve the problem. >> >> Anyway I think that there are two different issues, at least from what I can >> see on my desktop pc (i386, ports). >> >> One is that polkit-gnome-authen.core is dumped in /var/gdm when logging in >> with GDM, but everything seems working correctly. >> I can't even remember how I've found it. The following line is printed in ~/. >> xsession-errors: >> Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: >> cannot open shared object file: No such file or directory > >You should have a /usr/local/lib/gtk-2.0/modules/libgnomebreakpad.so >file (installed by bug-buddy). > Yes indeed. But this is what appears in ~/.xsession-errors. I don't know why. >> >> The other is the problem about slow start of panel and/or nautilus when >> running startx. >> Here you can find what is printed on the console: >> http://freebsd-gnome.pastebin.com/BnGRPB5L >> >> I have no idea if they are related and if it's correct mixing them, but if I >> use GDM, the desktop starts normally, if I use startx no core is dumped. > >Koop's suggestion to use ck-launch-session for startx sessions is a good >one. You need to do that. I tried with ck-launch-session...: the desktop appears immediately, the panel take a lot of time. It seems different from what Kevin says: "the panel comes up MUCH more quickly" here http://lists.freebsd.org/pipermail/freebsd-gnome/2010-July/024583.html Unless he means about 20 secs. It appears when the following message is printed, just like there a timeout while waiting for a response occurs: ** (gnome-panel:8811): WARNING **: Could not ask session manager if shut down is available: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Again, using GDM, as I normally do, I have no such issue. > As for the core dump, I have been unable to >reproduce locally. My research led me to the clock applet suggestion. >The backtrace was not terribly useful. Building bug-buddy without WITH_DEBUG=yes was even less useful. Can I do something more about that? Please, ask me. > >Can you try testing a virgin account with GDM as well as with startx >(and ck-launch-session) to see what problems still exist? > I've tried it yet, with both GDM and startx, with or without clock applet. Same effects in all cases.