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 511374 - crash in File Browser:
crash in File Browser:
Status: RESOLVED DUPLICATE of bug 459221
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-22 21:17 UTC by anubis4d
Modified: 2008-01-23 10:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description anubis4d 2008-01-22 21:17:05 UTC
Version: 2.18.3

What were you doing when the application crashed?



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.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Mac4Lin_GTK_Aqua_v0.3
Icon Theme: OSX

Memory status: size: 426369024 vsize: 426369024 resident: 46678016 share: 27033600 rss: 46678016 rss_rlim: 18446744073709551615
CPU usage: start_time: 1201046173 rtime: 703 utime: 519 stime: 184 cutime:0 cstime: 2 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 46912496393760 (LWP 3170)]
(no debugging symbols found)
0x0000003ab0c0d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496393760 (LWP 3170))

  • #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 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 gtk_tree_row_reference_free
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #17 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #20 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #21 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #22 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #23 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #24 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #25 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #28 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #29 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #30 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #31 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #32 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #33 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #34 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #35 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #36 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #37 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #38 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #39 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #40 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #41 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #42 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #43 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #44 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #45 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #46 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #47 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #48 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #49 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #50 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #51 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #52 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #53 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #54 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #55 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #56 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #57 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #58 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #59 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #60 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #61 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #62 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #63 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #64 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #65 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #66 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #67 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #68 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #69 nautilus_main_event_loop_quit
  • #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 _SmcProcessMessage
    from /usr/lib64/libSM.so.6
  • #75 IceProcessMessages
    from /usr/lib64/libICE.so.6
  • #76 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.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 ---------------------
fixme:shell:DllCanUnloadNow stub
fixme:shell:DllCanUnloadNow stub
fixme:shell:DllCanUnloadNow stub
fixme:shell:DllCanUnloadNow stub
** (gnome-session:3054): WARNING **: Invalid borders specified for theme pixmap:
        /home/marquitux/.themes/Mac4Lin_GTK_Aqua_v0.3/gtk-2.0/Buttons/button-default.png,
borders don't fit within the image
(nautilus:3170): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed
** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0)
aborting...
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff017f0000
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-23 10:32:31 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 459221 ***