After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 520377 - crash in Open Folder: i dont know what happene...
crash in Open Folder: i dont know what happene...
Status: RESOLVED DUPLICATE of bug 356672
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-04 21:13 UTC by krips123
Modified: 2008-03-04 23:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description krips123 2008-03-04 21:13:01 UTC
Version: 2.18.3

What were you doing when the application crashed?
i dont know what happened. i just closed a folder window.., suddenly this windows popped up and says that it crashs.. 


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Fedora

Memory status: size: 160833536 vsize: 160833536 resident: 64757760 share: 31076352 rss: 64757760 rss_rlim: 4294967295
CPU usage: start_time: 1204643070 rtime: 8020 utime: 6594 stime: 1426 cutime:1377 cstime: 175 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209157920 (LWP 2918)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209157920 (LWP 2918))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 ??
  • #11 gtk_tree_model_unref_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_tree_model_unref_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #22 ??
    from /lib/libgobject-2.0.so.0
  • #23 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #24 ??
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #26 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #30 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #38 ??
    from /lib/libgobject-2.0.so.0
  • #39 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #40 ??
    from /lib/libgobject-2.0.so.0
  • #41 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #42 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #43 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 ??
  • #46 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #47 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #50 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #52 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #53 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #54 ??
    from /lib/libgobject-2.0.so.0
  • #55 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #56 ??
    from /lib/libgobject-2.0.so.0
  • #57 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #58 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #59 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #60 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #61 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #62 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #63 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #64 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #65 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #66 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #67 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #68 ??
    from /lib/libgobject-2.0.so.0
  • #69 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #70 ??
    from /lib/libgobject-2.0.so.0
  • #71 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #72 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #73 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #74 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #75 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #76 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #77 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #78 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #79 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #80 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #81 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #82 ??
    from /lib/libgobject-2.0.so.0
  • #83 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #84 ??
    from /lib/libgobject-2.0.so.0
  • #85 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #86 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #87 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #88 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #89 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #90 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #91 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #92 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #93 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #94 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #95 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #96 ??
    from /lib/libgobject-2.0.so.0
  • #97 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #98 ??
    from /lib/libgobject-2.0.so.0
  • #99 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #100 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #101 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #102 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #103 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #104 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #105 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #106 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #107 gtk_container_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #108 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #109 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #110 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #111 ??
    from /lib/libgobject-2.0.so.0
  • #112 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #113 ??
    from /lib/libgobject-2.0.so.0
  • #114 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #115 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #116 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #117 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #118 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #119 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #120 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #121 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #122 ??
  • #123 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #124 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #125 ??
    from /lib/libgobject-2.0.so.0
  • #126 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #127 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #128 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #129 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #130 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #131 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #132 ??
    from /lib/libglib-2.0.so.0
  • #133 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #134 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #135 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libbonoboui-2.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgnome-2.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libdbus-1.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-03-04 23:07:05 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 356672 ***