GNOME Bugzilla – Bug 436873
crash in Open Folder: nothing! Wasn
Last modified: 2008-05-31 11:22:44 UTC
Version: 2.18.1 What were you doing when the application crashed? nothing! Wasn't even at the computer... Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3116.fc7 #1 SMP Thu Apr 26 10:17:55 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 455589888 vsize: 455589888 resident: 16830464 share: 11034624 rss: 16830464 rss_rlim: 18446744073709551615 CPU usage: start_time: 1178629148 rtime: 57 utime: 43 stime: 14 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496442272 (LWP 5278)] (no debugging symbols found) 0x000000329a20d83f in waitpid () from /lib64/libpthread.so.0
+ Trace 133064
Thread 1 (Thread 46912496442272 (LWP 5278))
----------- .xsession-errors --------------------- 14:34:36 : Population view with packages 14:34:36 : Population Completed Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c00021 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c00021 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c00021 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. closing gnome-mount 0.6 ** Message: Unknown errno: Too many levels of symbolic links ** Message: Unknown errno: Too many levels of symbolic links Initializing nautilus-flac-converter extension --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 449639 has been marked as a duplicate of this bug. ***
Additional comment to duplicate bug 449639 comment 2: Forget kde--I don't think it crashed till I went back into gnome. I clicked on the "wall paper tray" to change the wall paper--it crashed several times. Then when I tried to put different wall paper on the different desktops it crashed a couple more times. I deleted the "wall paper tray" from the panel and it hasn't crashed again.
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 the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 449984 has been marked as a duplicate of this bug. ***
*** Bug 449985 has been marked as a duplicate of this bug. ***
*** Bug 454084 has been marked as a duplicate of this bug. ***
*** Bug 464273 has been marked as a duplicate of this bug. ***
*** Bug 466124 has been marked as a duplicate of this bug. ***
*** Bug 480507 has been marked as a duplicate of this bug. ***
*** Bug 480506 has been marked as a duplicate of this bug. ***
could be the same issue as bug 439977
*** Bug 485796 has been marked as a duplicate of this bug. ***
*** Bug 495220 has been marked as a duplicate of this bug. ***
*** Bug 495495 has been marked as a duplicate of this bug. ***
*** Bug 495493 has been marked as a duplicate of this bug. ***
*** Bug 500536 has been marked as a duplicate of this bug. ***
*** Bug 501173 has been marked as a duplicate of this bug. ***
*** Bug 501175 has been marked as a duplicate of this bug. ***
*** Bug 501176 has been marked as a duplicate of this bug. ***
*** Bug 501177 has been marked as a duplicate of this bug. ***
*** Bug 501178 has been marked as a duplicate of this bug. ***
*** Bug 501179 has been marked as a duplicate of this bug. ***
*** Bug 502416 has been marked as a duplicate of this bug. ***
*** Bug 502417 has been marked as a duplicate of this bug. ***
*** Bug 502418 has been marked as a duplicate of this bug. ***
*** Bug 502419 has been marked as a duplicate of this bug. ***
This crash seems to have no duplicates from >= 2.20, closing as OBSOLETE. Please feel free to reopen the report if you can reproduce it with Nautilus >= 2.20, thanks!