Nautilus crash!

[John McCutchan <ttb tentacle dhs org>]

Hello,

With the latest garnome (0.18.2) Nautilus is crashing on me on startup.

Here is what is happening, When I start X nautilus loads fine,
but if I try and open up another copy of nautilus the one already running
crashes. I got this message:


(process:27209): Gdk-ERROR (recursed) **: The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
(Details: serial 83841 error_code 13 request_code 59 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Multiple segmentation faults occurred; can't display error dialog

So I ran nautilus with the --sync option and I got this message:


Gdk-ERROR **: The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadPixmap (invalid Pixmap parameter)'.
(Details: serial 20790 error_code 4 request_code 55 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...

When this happens, a core file is left but it is not from nautilus,
its from bonobo-activation-server. Here is the stack trace:

#0  0x40135e31 in g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR,
    format=0x80573a0 "file %s: line %d (%s): assertion failed: (%s)",
    args1=0xbffff5dc) at gmessages.c:503
#1  0x40135ee9 in g_log (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR,
    format=0x80573a0 "file %s: line %d (%s): assertion failed: (%s)")
    at gmessages.c:526
#2  0x08051d28 in remove_active_server (servant=0x80629e8,
    iid=0x8095789 ":0.0,OAFIID:Nautilus_Throbber_Factory", object=0x8085540)
    at object-directory-corba.c:678
#3  0x08051e47 in impl_Bonobo_ObjectDirectory_unregister (_servant=0x80629e8,
    iid=0x8095789 ":0.0,OAFIID:Nautilus_Throbber_Factory", obj=0x8085540,
    ev=0xbffff864) at object-directory-corba.c:737
#4  0x40018aca in _ORBIT_skel_small_Bonobo_ObjectDirectory_unregister (
    _o_servant=0x80629e8, _o_retval=0x0, _o_args=0xbffff730,
    _o_ctx=0xbffff790, _o_ev=0xbffff864,
    _impl_unregister=0x8051e30 <impl_Bonobo_ObjectDirectory_unregister>)
    at Bonobo_ObjectDirectory-skels.c:122
#5  0x40050a32 in ORBit_POAObject_invoke (pobj=0x8062900, ret=0x0,
    args=0xbffff730, ctx=0xbffff790, data=0xbffff7f4, ev=0xbffff864)
    at poa.c:893
#6  0x40053abd in ORBit_OAObject_invoke (adaptor_obj=0x8062900, ret=0x0,
    args=0xbffff730, ctx=0xbffff790, data=0xbffff7f4, ev=0xbffff864)
    at orbit-adaptor.c:132
#7  0x40043acb in ORBit_small_invoke_adaptor (adaptor_obj=0x8062900,
    recv_buffer=0x80829f0, m_data=0x40023180, data=0xbffff7f4, ev=0xbffff864)
    at orbit-small.c:797
#8  0x40050f7e in ORBit_POAObject_handle_request (pobj=0x8062900,
    opname=0x8083c7c "unregister", ret=0x0, args=0x0, ctx=0x0,
    recv_buffer=0x80829f0, ev=0xbffff864) at poa.c:1099
#9  0x400511b9 in ORBit_POA_handle_request (poa=0x8060d78,
    recv_buffer=0x80829f0, objkey=<incomplete type>) at poa.c:1186
#10 0x400539f6 in ORBit_handle_request (orb=0x8060ce0, recv_buffer=0x80829f0)
    at orbit-adaptor.c:94
#11 0x4003eefe in giop_connection_handle_input (lcnx=0x8087510)
    at giop-recv-buffer.c:1202
#12 0x4006d659 in linc_connection_io_handler (gioc=0x0, condition=G_IO_IN,
    data=0x8087510) at linc-connection.c:862
#13 0x4006f198 in linc_source_dispatch (source=0x8087028,
    callback=0x4006d5f0 <linc_connection_io_handler>, user_data=0x8087510)
    at linc-source.c:54
#14 0x4012eb29 in g_main_dispatch (context=0x8062140) at gmain.c:1617
#15 0x4012f947 in g_main_context_dispatch (context=0x8062140) at gmain.c:2161
#16 0x4012fd23 in g_main_context_iterate (context=0x8062140, block=1,
    dispatch=1, self=0x8095060) at gmain.c:2242
#17 0x401303ff in g_main_loop_run (loop=0x80621c8) at gmain.c:2462
#18 0x080539b2 in main (argc=3, argv=0xbffffbf4)
    at activation-server-main.c:296


There is another stack trace from nautilus in the bug I filed:

http://bugzilla.gnome.org/show_bug.cgi?id=97007

Do you guys need any more information? Is this a bug in
bonobo-activation-server or a bug in nautilus causing bonobo-activation-server
to segfault?

John