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 446966 - crash in Open Folder: closing a window
crash in Open Folder: closing a window
Status: RESOLVED DUPLICATE of bug 444717
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-13 02:38 UTC by mrp
Modified: 2007-06-23 11:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mrp 2007-06-13 02:38:47 UTC
Version: 2.18.1

What were you doing when the application crashed?
closing a window


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Yattacier3
Icon Theme: Gion

Memory status: size: 505077760 vsize: 505077760 resident: 45072384 share: 27496448 rss: 45072384 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181698908 rtime: 623 utime: 544 stime: 79 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496365264 (LWP 3213)]
[New Thread 1094719824 (LWP 5422)]
(no debugging symbols found)
0x0000003880a0d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496365264 (LWP 3213))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /lib64/libglib-2.0.so.0
  • #6 g_log
    from /lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /lib64/libglib-2.0.so.0
  • #8 ??
  • #9 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #11 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 gtk_tree_row_reference_free
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #15 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #16 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #19 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #21 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #22 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #23 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #24 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #26 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #27 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #28 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #29 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #30 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #31 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #32 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #33 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #34 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #35 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #36 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #37 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #38 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #39 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #40 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #41 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #42 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #43 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #44 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #45 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #46 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #47 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #48 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #49 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #50 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #51 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #52 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #53 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #54 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #55 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #56 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #57 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #58 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #59 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #60 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #61 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #62 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #63 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #64 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #65 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #66 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #67 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #68 ??
  • #69 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #70 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #71 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #72 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #73 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #74 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #75 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #76 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #77 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #78 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #79 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #80 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #81 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
Sending reload event...
Sending reload event...
Sending reload event...
Sending reload event...
Sending reload event...
Sending reload event...
--- Hash table keys for warning below:
--> file:///home/robles
(nautilus:5384): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
I/O warning : failed to load external entity "/home/robles/.config/audacious/playlist.xspf"
** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0)
aborting...
--------------------------------------------------
Comment 1 André Klapper 2007-06-23 11:37:20 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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