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 457059 - crash in Computer: I clicked on the mebu it...
crash in Computer: I clicked on the mebu it...
Status: RESOLVED DUPLICATE of bug 349551
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-15 08:07 UTC by Gavin Flower
Modified: 2007-07-15 19:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Gavin Flower 2007-07-15 08:07:42 UTC 
Version: 2.16.2

What were you doing when the application crashed?
I clicked on the mebu item to delete contents of the wastebasket, it had done that (wastebasket director viewer was now blank), then it crashed...


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.20-1.2962.fc6 #1 SMP Tue Jun 19 18:50:05 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 599642112 vsize: 599642112 resident: 59691008 share: 38580224 rss: 59691008 rss_rlim: 0
CPU usage: start_time: 1184314830 rtime: 3544 utime: 2816 stime: 728 cutime:1 cstime: 10 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 46912496437184 (LWP 25568)]
[New Thread 1115699520 (LWP 28407)]
0x000000347c40d9ff in __libc_waitpid (pid=7959, stat_loc=0x7fff9c476c9c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

+ Trace 148135

Thread 1 (Thread 46912496437184 (LWP 25568))

  • #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 1154
  • #13 main
    at nautilus-main.c line 389
  • #14 __libc_start_main
    at libc-start.c line 231
  • #15 _start 
0x000000347c40d9ff	41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);


----------- .xsession-errors ---------------------
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
** (nautilus:25568): CRITICAL **: nautilus_window_info_get_window_type: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed
** (nautilus:25568): CRITICAL **: nautilus_window_info_get_ui_manager: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
** (bug-buddy:7960): WARNING **: Couldn't load icon for Open Folder
Xlib:  extension "SHAPE" missing on display ":0.0".
warning: the debug information found in "/usr/lib/debug//lib64/libdbus-1.so.3.2.0.debug" does not match "/lib64/libdbus-1.so.3" (CRC mismatch).
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-07-15 19:36:43 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 349551 ***