Bug 179697 - nautilus segfaulted.
Summary: nautilus segfaulted.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-02 04:49 UTC by Dave Jones
Modified: 2015-01-04 22:24 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-09-06 07:59:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dave Jones 2006-02-02 04:49:00 UTC
I found some core dumps in my home dir belonging to nautilus.

Core was generated by `nautilus --no-default-window --sm-client-id default3'.
Program terminated with signal 11, Segmentation fault.

(gdb) bt
#0  0x0000003cdde3e7d4 in ORBit_OAObject_invoke () from /usr/lib64/libORBit-2.so.0
#1  0x0000003cdde3e857 in ORBit_handle_request () from /usr/lib64/libORBit-2.so.0
#2  0x0000003cdde2bcaa in giop_connection_handle_input () from
/usr/lib64/libORBit-2.so.0
#3  0x0000003cdde43c90 in link_connection_state_changed () from
/usr/lib64/libORBit-2.so.0
#4  0x0000003cdc224e91 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#5  0x0000003cdc227cad in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#6  0x0000003cdc227ffe in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#7  0x0000003cdde42ed3 in link_set_io_thread () from /usr/lib64/libORBit-2.so.0
#8  0x0000003cdc23eeaf in g_thread_create_full () from /usr/lib64/libglib-2.0.so.0
#9  0x0000003c3dd0615a in start_thread () from /lib64/libpthread.so.0
#10 0x0000003c3b9c92bd in clone () from /lib64/libc.so.6
#11 0x0000000000000000 in ?? ()

Comment 1 Alexander Larsson 2006-09-04 15:59:18 UTC
Ugh, bonobo stuff...
Do you have accessibility enabled in gnome?


Comment 2 Alexander Larsson 2006-09-04 16:00:29 UTC
Also, how old are these cores?


Comment 3 Dave Jones 2006-09-05 17:07:40 UTC
no accessability, and I don't have the cores around any more, so no idea.
Haven't seen it segv in a while though, so if you want to close this, I'll file
a new bug if it ever reappears.



Note You need to log in before you can comment on or make changes to this bug.