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 484413 - crash in Open Folder: switching to the next di...
crash in Open Folder: switching to the next di...
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-10-07 14:36 UTC by furlan primus
Modified: 2007-10-07 18:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description furlan primus 2007-10-07 14:36:53 UTC 
Version: 2.18.3

What were you doing when the application crashed?
switching to the next directory above the current one.


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 94289920 vsize: 94289920 resident: 28561408 share: 21434368 rss: 28561408 rss_rlim: 4294967295
CPU usage: start_time: 1191758767 rtime: 2131 utime: 1829 stime: 302 cutime:401 cstime: 134 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 -1208645920 (LWP 2680)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 168546

Thread 1 (Thread -1208645920 (LWP 2680))

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


----------- .xsession-errors (12 sec old) ---------------------
AFD changed from -2 to -1
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  42 (X_SetInputFocus)
  Serial number of failed request:  24711
  Current serial number in output stream:  24713
kbuildsycoca running...
Reusing existing ksycoca
KMid 2.0 Copyright (C) 1997,98,99,2000,01 Antonio Larrosa Jimenez. Malaga (Spain)
KMid comes with ABSOLUTELY NO WARRANTY; for details view file COPYING
This is free software, and you are welcome to redistribute it
under certain conditions
** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0)
aborting...
--------------------------------------------------
Comment 1 Susana 2007-10-07 18:41:53 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 ***