R: Re: R: Re: ports/148272: polkit-gnome-authen core dumps when starting gnome

[Joe Marcus Clarke]

On 7/8/10 11:47 AM, Kevin Oberman wrote:
>> Date: Thu, 08 Jul 2010 11:22:52 -0400
>> From: Byron Campbell <wa4geg at netscape.net>
>> Sender: owner-freebsd-gnome at freebsd.org
>>
>> On 07/07/2010 07:46 PM, Joe Marcus Clarke wrote:
>>> On 7/7/10 7:14 PM, Barbara wrote:
>>>>
>>>>
>>>>> On 7/5/10 7:59 PM, Barbara wrote:
>>>>>>
>>>>>>> On 7/5/10 5:36 PM, Barbara wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On 7/4/10 5:00 PM, Barbara wrote:
>>>>>>>>>>
>>>>>>>>>> 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).
>>>>>>>>>
>>>>>>>>
>>>>>>>> As I've said in another post, I have that file.
>>>>>>>> Anyway I think I've found a "solution" for that:
>>>>>>>> $ gconftool-2 --type=bool --set /apps/gnome_settings_daemon/gtk-
>>>>>>>> modules/gnomebreakpad false
>>>>>>>> This is obviously a single-user setting, so that should be done for
>>>> every
>>>>>> user
>>>>>>>> logging in with GDM.
>>>>>>>> Unfortunately, this doesn't solve the other problem when running startx.
>>>>>>>
>>>>>>> Do you use any Linux GTK+ apps?
>>>>>>
>>>>>> No, AFAIK. On startup?
>>>>>>
>>>>>>> This warning could be coming from one of those that can't find a Linux
>>>> ABI
>>>>>>> version of breakpad.  In any event, I don't think it's fatal.
>>>>>>
>>>>>> I thought it was caused by polkit-gnome-auth... as reported in the
>>>> backtrace,
>>>>>> wasn't it?
>>>>>> Anyway, no, it's not fatal. I've found it's dumping cores accidentally.
>>>>>>
>>>>>>
>>>>>>> I have been trying to reproduce all of these problems locally, and thus
>>>>>>> far I have not seen any of them.  I have two test machines both are
>>>>>>> i386.  One machine is running RELENG_8, and the other is -CURRENT.  I
>>>>>>> have tested an existing account upgraded from GNOME 2.0 as well as a new
>>>>>>> account.  Neither show any slowness, crashes, or strange errors in
>>>>>>> .xsession-errors.  I have only tested with GDM thus far.
>>>>>>>
>>>>>>> I have just finished updating my amd64 machine, so I will test with that
>>>>>>> machine as well.  If I cannot reproduce any of these problems, I will
>>>>>>> have to point people to GNOME's Bugzilla.
>>>>>>>
>>>>>>
>>>>>> I have not updated my laptop since (about) the last month.
>>>>>> It's RELENG_8_0, i386, ports.
>>>>>> I'll made some test on it before and after updating the installed ports to
>>>> see
>>>>>> what happens.
>>>>>> Maybe I'm doing something wrong or I'm not doing something needed (e.g.
>>>> some
>>>>>> configurations).
>>>>>>
>>>>>>
>>>>>
>>>>> If you can reliably reproduce the polkit-gnome crash, remove the
>>>>> /usr/local/lib/gtk-2.0/modules/libgnomebreakpad.so module, and get a
>>>>> backtrace of the new core file.
>>>>>
>>>>
>>>> I've tried removing the module after rebuilding polkit, polkit-gnome and bug-
>>>> buddy WITH_DEBUG, but I'm not getting any core file.
>>>> This is what I get in ~/.xsession-errors:
>>>> Gtk-Message: Failed to load module "gnomebreakpad": Shared object
>>>> "libgnomebreakpad.so" not found, required by "gnome-settings-daemon"
>>>> Gtk-Message: Failed to load module "gnomebreakpad": Shared object
>>>> "libgnomebreakpad.so" not found, required by "metacity"
>>>> Window manager warning: Failed to read saved session file /home/bar/.
>>>> config/metacity/sessions/10d6257d9fd17a13d7127854042857675300000790890017.ms:
>>>> Failed to open file '/home/bar/.
>>>> config/metacity/sessions/10d6257d9fd17a13d7127854042857675300000790890017.ms':
>>>> No such file or directory
>>>> Gtk-Message: Failed to load module "gnomebreakpad": Shared object
>>>> "libgnomebreakpad.so" not found, required by "gnome-panel"
>>>> Gtk-Message: Failed to load module "gnomebreakpad": Shared object
>>>> "libgnomebreakpad.so" not found, required by "nautilus"
>>>> Gtk-Message: Failed to load module "gnomebreakpad": Shared object
>>>> "libgnomebreakpad.so" not found, required by "canberra-gtk-play"
>>>> Gtk-Message: Failed to load module "gnomebreakpad": Shared object
>>>> "libgnomebreakpad.so" not found, required by "polkit-gnome-authentication-agent-
>>>> 1"
>>>>
>>>> On the first login I also got failure loading some applets as you can see
>>>> here:
>>>> http://www.freeimagehosting.net/uploads/9f051e0414.png
>>>> Maybe some are the same givig troubles to Kevin (e.g. WorkspaceSwitcher
>>>> BTW, why it's always tring to "read saved session file" ? ~/.
>>>> config/metacity/sessions/ is always empty!
>>>>
>>>> About my laptop, the ports were as outdated as I was thinking: Jun 20th.
>>>> And I'm getting the same exact behaviors I'm seeing on my desktop.
>>>>
>>>>
>>>>
>>>
>>> I am unable to reproduce even with startx.  I have the following in my
>>> .xinitrc:
>>>
>>> exec ck-launch-session gnome-session
>>>
>>> GNOME comes up.  It's slow to start since gnome-panel cannot contact
>>> GDM, but I get working applets, and my workspace switcher works.  At
>>> this point, I would advise those seeing a problem to open a bug (or
>>> bugs) with GNOME Bugzilla.
>>>
>>> Joe
>>>
>>
>> Workspace Switcher works for me too when starting gnome w/ startx. Using 
>> "exec ck-launch-session gnome-session" in .xinitrc speeds up things by a 
>> good 10~11 seconds over just "exec gnome-session".
> 
> Actually, the recommended command to start gnome that was suggested (and
> I am using) is:
> exec ck-launch-session dbus-launch --exit-with-session gnome-session
> 
> I know that dbus-launch has been the "proper" way to start it for a
> while. I don't know that it will affect startup, but it should make for
> a cleaner shutdown if I understand what it does.

dbus-launch is actually no longer required since GNOME 2.26, I think.
The ck-launch-session is.  I updated the FAQ yesterday.

Joe

-- 
Joe Marcus Clarke
FreeBSD GNOME Team	::	gnome at FreeBSD.org
FreeNode / #freebsd-gnome
http://www.FreeBSD.org/gnome