nautilus-throbber波崩溃

keyuan1

在RHE3AS(网络下载版)中,设置关联文件打开文件可导致nautilus-throbber崩溃.fix此bug的技术文档我看不懂.请高手告之.

Index: nautilus/src//nautilus-navigation-window.c
===================================================================
RCS file: /cvs/gnome/nautilus/src/nautilus-navigation-window.c,v
retrieving revision 1.417
diff -p -u -r1.417 nautilus-navigation-window.c
--- nautilus/src//nautilus-navigation-window.c  3 Nov 2003 14:12:38 -0000       1.417
+++ nautilus/src//nautilus-navigation-window.c  17 Nov 2003 09:26:11 -0000
@@ -944,6 +944,8 @@ real_set_content_view_widget (NautilusWi
        
        disconnect_view (window, nautilus_window->content_view);

+       g_return_if_fail(new_view != NULL);
+      
        EEL_CALL_PARENT (NAUTILUS_WINDOW_CLASS,
                         set_content_view_widget,
                         (nautilus_window, new_view));

laokan

是够麻烦的，要看懂这个，可够呛

keyuan1

哪位高手能够解决.

问题见:

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

Steps to reproduce:

1. Login as root.
2. Goto a user (For example 'sragavan') /home/sragavan
3. Create a file a.txt, which has owner as root:root and file attribute as
700 (-rwx --- ---)
4. Login as sragavan. Start nautilus.
5. Double click the file a.txt that the root user created. It crashes.

Its 100% reproducible.

Stack Trace
------------

#0  0xffffe002 in ?? ()
#1  0x4025f58d in libgnomeui_segv_handle (signum=11) at gnome-ui-init.c:738
#2  <signal handler called>
#3  0x08070a15 in create_view_as_menu_item (window=0x8181ef8,
    identifier=0xfffffe00, index=3221217016)
    at nautilus-navigation-window.c:608
#4  0x08070d69 in load_view_as_menu (window=0x8181ef
    at nautilus-navigation-window.c:689
#5  0x080881ee in nautilus_window_set_content_view_widget (window=0x8181ef8,
    frame=0x0) at nautilus-window.c:1293
#6  0x08083893 in handle_view_failure (window=0x8181ef8, view=0x84ba440)
    at nautilus-window-manage-views.c:1007
#7  0x40af0c84 in g_cclosure_marshal_VOID__VOID (closure=0x84ba800,
    return_value=0x0, n_param_values=1, param_values=0x1,
    invocation_hint=0xbfffe018, marshal_data=0x0) at gmarshal.c:77
#8  0x40adebb6 in g_closure_invoke (closure=0x84ba800, return_value=0x0,
    n_param_values=1, param_values=0xbfffe120, invocation_hint=0xbfffe01
    at gclosure.c:437
#9  0x40af0826 in signal_emit_unlocked_R (node=0x81d0d88, detail=0,
    instance=0x84ba440, emission_return=0x0, instance_and_params=0xbfffe120)
    at gsignal.c:2436
#10 0x40aef8e2 in g_signal_emit_valist (instance=0x84ba440, signal_id=216,
    detail=0, var_args=0xbfffe2ac "??\a\b\001") at gsignal.c:2195
---Type <return> to continue, or q <return> to quit---
#11 0x40aefb97 in g_signal_emit (instance=0x84ba440, signal_id=216, detail=0)
    at gsignal.c:2239
#12 0x0807f978 in view_frame_failed (view=0x84ba440)
    at nautilus-view-frame.c:445
#13 0x4001f46b in execute_queued_functions (callback_data=0x8434170)
    at nautilus-idle-queue.c:66
#14 0x40b693d8 in g_idle_dispatch (source=0x8501950, callback=0x1,
    user_data=0x8434170) at gmain.c:3273
#15 0x40b669da in g_main_dispatch (context=0x80d927 at gmain.c:1752
#16 0x40b67a2d in g_main_context_dispatch (context=0x80d927 at gmain.c:2300
#17 0x40b67d57 in g_main_context_iterate (context=0x80d9278, block=1,
    dispatch=1, self=0x80c7eb0) at gmain.c:2381
#18 0x40b68426 in g_main_loop_run (loop=0x81465c at gmain.c:2601
#19 0x4048529b in gtk_main () at gtkmain.c:1158
#20 0x0806f41d in main (argc=1, argv=0xbfffe584) at nautilus-main.c:282
#21 0x420156a4 in __libc_start_main () from /lib/tls/libc.so.6

Hope this is sufficient to fix the crash.




------- Additional Comments From Srinivasa Ragavan 2003-11-17 04:36 -------

I have fixed the defect. Actually new_view == null, was not checked at
all. I have attached the patch also. Basically after disconnecting
from the previous view, and just before connecting to the new view,
check whether new_view is null or not.




------- Additional Comments From Srinivasa Ragavan 2003-11-17 04:37 -------

Created an attachment (id=21523)
Proposed patch