GNOME Bugzilla – Bug 494298
crash in Open Folder: shift clicked on 2 direc...
Last modified: 2007-11-08 01:28:16 UTC
Version: 2.18.3 What were you doing when the application crashed? shift clicked on 2 directory and 1 file to open them 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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 85446656 vsize: 85446656 resident: 25006080 share: 18010112 rss: 25006080 rss_rlim: 4294967295 CPU usage: start_time: 1194371479 rtime: 966 utime: 897 stime: 69 cutime:0 cstime: 0 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 -1208989984 (LWP 2898)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175841
Thread 1 (Thread -1208989984 (LWP 2898))
----------- .xsession-errors (12 sec old) --------------------- --- Hash table keys for warning below: --> file:///home/udayan (nautilus:5503): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) --- Hash table keys for warning below: --> file:///home/udayan (nautilus:5499): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ** (nautilus:2898): WARNING **: destroyed file has call_when_ready pending (nautilus:2898): Gtk-CRITICAL **: gtk_window_get_screen: assertion `GTK_IS_WINDOW (window)' failed ** (nautilus:2898): CRITICAL **: my_gdk_spawn_make_environment_for_screen: assertion `GDK_IS_SCREEN (screen)' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces