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 479501 - crash in Computer: I clicked on the "upper ...
crash in Computer: I clicked on the "upper ...
Status: RESOLVED DUPLICATE of bug 424980
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-23 11:58 UTC by antoine.roux
Modified: 2007-10-19 22:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description antoine.roux 2007-09-23 11:58:30 UTC 
Version: 2.18.3

What were you doing when the application crashed?
I clicked on the "upper directory" button. In the same time, I was doing the configuration of Vmware Player


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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 96174080 vsize: 96174080 resident: 28884992 share: 19070976 rss: 28884992 rss_rlim: 4294967295
CPU usage: start_time: 1190534750 rtime: 753 utime: 670 stime: 83 cutime:1 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208883488 (LWP 2907)]
(no debugging symbols found)
0x00f09402 in __kernel_vsyscall ()

+ Trace 164827

Thread 1 (Thread -1208883488 (LWP 2907))

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


----------- .xsession-errors (15 sec old) ---------------------
Module vmnet not loaded
vmware
Bridged networking on /dev/vmnet0 is not running
Host network detection is not running
Host-only networking on /dev/vmnet1 is not running
DHCP server on /dev/vmnet1 is not running
Bridged networking on /dev/vmnet2 is not running
Host-only networking on /dev/vmnet8 is not running
DHCP server on /dev/vmnet8 is not running
NAT networking on /dev/vmnet8 is not running
Module vmmon not loaded
Module vmnet not loaded
** ERROR **: file fm-tree-model.c: line 1527 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0)
aborting...
--------------------------------------------------
Comment 1 Christian Kirbach 2007-10-19 22:16:11 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 424980 ***