GNOME Bugzilla – Bug 520425
crash in Open Folder:
Last modified: 2009-03-31 17:42:14 UTC
Version: 2.21.91 What were you doing when the application crashed? Distribution: Solaris Express Community Edition snv_83a X86 Gnome Release: 2.21.91 2008-02-27 (Sun Microsystems, Inc.) BugBuddy Version: 2.21.90 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 144838656 vsize: 144838656 resident: 64856064 share: 851968 rss: 64856064 rss_rlim: 0 CPU usage: start_time: 0 rtime: 276 utime: 2377386 stime: 384851 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) sol-thread active. Retry #1: Retry #2: Retry #3: Retry #4: [New LWP 1 ] [New Thread 1 (LWP 1)]
+ Trace 191329
Thread 1 (LWP 1)
Thread 4 (Thread 1384 ): #-1 0xfef00c6b in __lwp_park () from /lib/libc.so.1 No symbol table info available. Thread 3 (LWP 1384 ): #-1 0xfef00c6b in __lwp_park () from /lib/libc.so.1 No symbol table info available. Thread 2 (Thread 1 (LWP 1)): #-1 0xfef04c07 in __waitid () from /lib/libc.so.1 No symbol table info available. Thread 1 (LWP 1 ): #-1 0xfef04c07 in __waitid () from /lib/libc.so.1 No symbol table info available. #-1 0xfef04c07 in __waitid () from /lib/libc.so.1
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 454799 ***
Wrongly marked as a dup, sorry for the spam.
Still, it's not a useful trace. :-( 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
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!