A few things happened to make crashes more common in recent GNOME builds:
1) The GNOME community enabled coreing on ASSERTs in default builds, so
some subtle bugs became less subtle.
2) Coring on ASSERT causes some post install scripts to fail on some
hardware due to a file access race condition. Here are two bugs related
to that and the corresponding workarounds:
6631419 - gtk-update-icon-cache dies on first boot after install/upgrade
Workaround: (as root)
for d in /usr/share/icons/*; do
[ -d $d ] &&
gtk-update-icon-cache --force $d;
done
6578750 - fontconfig crash in FcPatternPosition. This should be fixed
in snv_85:
Run "/usr/bin/fc-cache -sv" from the console, or a failsafe session as
yourself and as root.
Jim Walker wrote:
> Alan Coopersmith wrote:
>
>> Nick Briggs wrote:
>>
>>> Can't help on getting the older release, but it's not just under vmware that
>>> gnome is crashing -- happens 5-20 times a day to me running on b84 on
>>> a SunBlade 1000 (w/ dual ffb, xinerama mode)
>>>
>> Strange - I can't remember the last time GNOME crashed on my SunBlade 2500
>> (now running nv_84 - I usually live upgrade to the current nevada build
>> every month or two).
>>
>>
>
> I have an Ultra 45 with XVR-2500 card. After I upgraded to snv_84 last
> week I get 5-20 gnome crashes a day, like Nick. With the bug buddy
> appearing but never getting any useful data to send in. I never saw
> a gnome crash before. I plan on moving to the next build asap.
>
> Cheers,
> Jim
>
> _______________________________________________
> desktop-discuss mailing list
> [EMAIL PROTECTED]
>
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
