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 465177 - crash in Open Folder: Clicking into /home/user
crash in Open Folder: Clicking into /home/user
Status: RESOLVED DUPLICATE of bug 433983
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-09 20:30 UTC by boylej
Modified: 2007-08-10 14:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description boylej 2007-08-09 20:30:30 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Clicking into /home/user


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

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 322498560 vsize: 322498560 resident: 233320448 share: 36765696 rss: 233320448 rss_rlim: 4294967295
CPU usage: start_time: 1186671660 rtime: 21110 utime: 19274 stime: 1836 cutime:1146 cstime: 174 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 -1208588576 (LWP 3624)]
[New Thread -1252484208 (LWP 17551)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 154052

Thread 1 (Thread -1208588576 (LWP 3624))

  • #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 gtk_tree_row_reference_free
    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 gtk_tree_view_set_cursor_on_cell
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_tree_view_set_cursor
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
  • #23 ??
    from /lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #25 ??
    from /lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (12 sec old) ---------------------
(nautilus:3624): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `VALID_ITER (iter, tree_model_sort)' failed
(nautilus:3624): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed
kbuildsycoca running...
Reusing existing ksycoca
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x38c9d28
** (nautilus:3624): WARNING **: destroyed file has call_when_ready pending
** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0)
aborting...
--------------------------------------------------
Comment 1 Susana 2007-08-10 14:37:24 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 433983 ***