GNOME Bugzilla – Bug 513334
crash in Open Folder: renaming a folder
Last modified: 2008-01-31 15:10:55 UTC
Version: 2.18.3 What were you doing when the application crashed? renaming a folder Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 143335424 vsize: 143335424 resident: 56270848 share: 27312128 rss: 56270848 rss_rlim: 4294967295 CPU usage: start_time: 1200886763 rtime: 7231 utime: 6560 stime: 671 cutime:17 cstime: 9 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 -1208310048 (LWP 2888)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 187517
Thread 1 (Thread -1208310048 (LWP 2888))
----------- .xsession-errors --------------------- (gnome-panel:474): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (gnome-panel:474): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (gnome-panel:474): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (gnome-panel:474): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (gnome-panel:474): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (gnome-panel:474): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (gnome-panel:474): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed (gnome-panel:474): Gdk-CRITICAL **: gdk_window_move_resize: assertion `GDK_IS_WINDOW (window)' failed --------------------------------------------------
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 465786 ***