This trace looks the same as a the menu monitoring bug that has been fixed for nv_86, did you add some new menu item or install some new software when the crash occured ?
cheers Matt Nick Briggs wrote: > System is SunBlade 1000, 2xFFB2+ in xinerama mode. > > gnome-panel crashes frequently. There is no debug schema, so bug-buddy isn't > helpful. > > Typical stack is: > > t at 1 (l at 1) signal SEGV (no mapping at the fault address) in (unknown) at > 0x0 > 0x00000000: <bad address 0x0> > (dbx) where > current thread: t at 1 > [1] 0x0(0x2e09d0, 0x2fb628, 0x1040, 0xff3626a4, 0x21a958, 0x0), at 0x0 > [2] cached_dir_invoke_monitors(0x27d370, 0x3, 0x2f9bb8, 0x0, 0x305af8, > 0x0), at 0xf7897b48 > [3] invoke_notifies(0x2fc628, 0x3, 0x2e9c30, 0x0, 0x148a0, 0xf78b7300), at > 0xf78a2ac4 > [4] emit_events_in_idle(0x33fef0, 0xf78b7ac0, 0xf78b7300, 0x7c0, 0x14814, > 0x400), at 0xf78a2b50 > [5] g_main_dispatch(0xc1ac8, 0x0, 0x0, 0x0, 0xff063eb4, 0xc1ad0), at > 0xfefc0010 > [6] g_main_context_dispatch(0x1, 0x1, 0xff065ea4, 0x2, 0xff065ea8, > 0xc1ac8), at 0xfefc16b8 > [7] g_main_context_iterate(0x1, 0x1, 0x1, 0xc1ac8, 0x17, 0x17), at > 0xfefc1bd8 > [8] g_main_loop_run(0x212630, 0x0, 0x0, 0xa0b38, 0x212638, 0x1), at > 0xfefc24dc > [9] gtk_main(0x0, 0x0, 0x0, 0xbe5c, 0xfbaf1538, 0x212630), at 0xfb8a6b34 > [10] main(0x5, 0xa9058, 0x80000, 0x803e0, 0x803f8, 0x8040c), at 0x37e70 > > Happens many times per day. Other gnome parts also SEGV (though not as > frequently), which is most annoying when it's the window manager, and you > lose everything you're doing. > > > This message posted from opensolaris.org > _______________________________________________ > desktop-discuss mailing list > desktop-discuss at opensolaris.org >
