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 416167 - crash in Computer: just attempted to bring ...
crash in Computer: just attempted to bring ...
Status: RESOLVED DUPLICATE of bug 390534
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-08 19:38 UTC by Gavin Flower
Modified: 2007-03-09 10:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Gavin Flower 2007-03-08 19:38:11 UTC 
Version: 2.16.2

What were you doing when the application crashed?
just attempted to bring up a nautilus directory view of my home directory.  The instance appeared, but no contents displayed


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2911.6.5.fc6 #1 SMP Sun Mar 4 16:05:34 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 508157952 vsize: 508157952 resident: 38412288 share: 15769600 rss: 38412288 rss_rlim: 0
CPU usage: start_time: 1173163168 rtime: 3145 utime: 2651 stime: 494 cutime:7 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496437168 (LWP 3835)]
0x00000034bd40d96f in __libc_waitpid (pid=1472, stat_loc=0x7fffb1339cbc, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

+ Trace 116965

Thread 1 (Thread 46912496437168 (LWP 3835))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #2 <signal handler called>
  • #3 IA__gtk_ui_manager_remove_ui
    at gtkuimanager.c line 1753
  • #4 nautilus_ui_unmerge_ui
    at nautilus-ui-utilities.c line 38
  • #5 real_update_menus
    at fm-directory-view.c line 4637
  • #6 fm_directory_view_update_menus
    at fm-directory-view.c line 9360
  • #7 update_menus_timeout_callback
    at fm-directory-view.c line 2928
  • #8 g_timeout_dispatch
    at gmain.c line 3422
  • #9 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #10 g_main_context_iterate
    at gmain.c line 2677
  • #11 IA__g_main_loop_run
    at gmain.c line 2881
  • #12 IA__gtk_main
    at gtkmain.c line 1148
  • #13 main
    at nautilus-main.c line 389
  • #14 __libc_start_main
    at libc-start.c line 231
  • #15 _start 
0x00000034bd40d96f	41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);


----------- .xsession-errors (133798 sec old) ---------------------
(gnome-system-log:4465): Gtk-CRITICAL **: gtk_tree_selection_real_modify_range: assertion `start_node != NULL' failed
(gnome-system-log:4465): Gtk-CRITICAL **: gtk_tree_selection_real_modify_range: assertion `start_node != NULL' failed
(gnome-system-log:4465): Gtk-CRITICAL **: gtk_tree_selection_real_modify_range: assertion `start_node != NULL' failed
(gnome-system-log:4465): Gtk-CRITICAL **: gtk_tree_selection_real_modify_range: assertion `start_node != NULL' failed
(gnome-system-log:4465): Gtk-CRITICAL **: gtk_tree_selection_real_modify_range: assertion `start_node != NULL' failed
(gnome-system-log:4465): Gtk-CRITICAL **: gtk_tree_selection_real_modify_range: assertion `start_node != NULL' failed
(gnome-system-log:4465): Gtk-CRITICAL **: gtk_tree_selection_real_modify_range: assertion `start_node != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Susana 2007-03-09 10:02:17 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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