GNOME Bugzilla – Bug 509932
crash in Open Folder: Typing at address bar a ...
Last modified: 2008-08-14 17:00:51 UTC
Version: 2.20.0 What were you doing when the application crashed? Typing at address bar a location to my home dir Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Fri Nov 30 16:25:38 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Debian-GTK Icon Theme: nuoveXT.2.2 Memory status: size: 159387648 vsize: 159387648 resident: 25108480 share: 15278080 rss: 25108480 rss_rlim: 4294967295 CPU usage: start_time: 1200497097 rtime: 1145 utime: 999 stime: 146 cutime:669 cstime: 70 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6c656c0 (LWP 3243)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 185582
Thread 1 (Thread 0xb6c656c0 (LWP 3243))
----------- .xsession-errors (6 sec old) --------------------- ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded: ignored. ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** (nautilus:3243): WARNING **: destroyed file still being monitored ** ERROR **: file nautilus-directory-background.c: line 616 (nautilus_connect_background_to_file_metadata): assertion failed: (NAUTILUS_IS_FILE (old_file)) aborting... --------------------------------------------------
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
Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Fri Nov 30 16:25:38 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Debian-GTK Icon Theme: nuoveXT.2.2 Memory status: size: 81633280 vsize: 81633280 resident: 26533888 share: 16371712 rss: 26533888 rss_rlim: 4294967295 CPU usage: start_time: 1202081924 rtime: 1687 utime: 918 stime: 769 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6c1a6c0 (LWP 25783)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 187987
Thread 1 (Thread 0xb6c1a6c0 (LWP 25783))
This should be fixed in 2.22
*** This bug has been marked as a duplicate of 425157 ***