GNOME Bugzilla – Bug 481533
crash in Home Folder: Restarted Nautilus after...
Last modified: 2008-09-12 13:48:16 UTC
What were you doing when the application crashed? Restarted Nautilus after installing the nautilus-sendto extension Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 84410368 vsize: 84410368 resident: 22114304 share: 13258752 rss: 22114304 rss_rlim: 4294967295 CPU usage: start_time: 1191049177 rtime: 2096 utime: 1852 stime: 244 cutime:344 cstime: 88 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 0xb6b376c0 (LWP 8243)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 166363
Thread 1 (Thread 0xb6b376c0 (LWP 8243))
----------- .xsession-errors (524 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6200058 (A222 Proje) Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6200058 (A222 Proje) Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
at the moment it looks like this is fixed by rebuilding nautilus-sendto against current GNOME.
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
*** Bug 498602 has been marked as a duplicate of this bug. ***
*** Bug 510652 has been marked as a duplicate of this bug. ***
*** Bug 513899 has been marked as a duplicate of this bug. ***
*** Bug 536411 has been marked as a duplicate of this bug. ***
*** Bug 542784 has been marked as a duplicate of this bug. ***
*** Bug 543760 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 480179 ***
*** Bug 551948 has been marked as a duplicate of this bug. ***