GNOME Bugzilla – Bug 525816
crash in Home Folder: browse thumbnails scroll...
Last modified: 2008-04-03 00:37:10 UTC
What were you doing when the application crashed? browse thumbnails scroll up down mouse in window Distribution: Solaris Express Community Edition snv_84 X86 Gnome Release: 2.20.2 2008-02-13 (Sun Microsystems, Inc.) BugBuddy Version: 2.20.1 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus Memory status: size: 206077952 vsize: 206077952 resident: 89554944 share: 393216 rss: 89554944 rss_rlim: 0 CPU usage: start_time: 0 rtime: 12015 utime: 106381316 stime: 13774901 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 194043
Thread 1 (LWP 1)
Thread 8 (Thread 333 (LWP 333)): #-1 0xfef04717 in __read () from /lib/libc.so.1 No symbol table info available. Thread 7 (Thread 168 ): #-1 0xfef00c6b in __lwp_park () from /lib/libc.so.1 No symbol table info available. Thread 6 (Thread 165 ): #-1 0xfef00c6b in __lwp_park () from /lib/libc.so.1 No symbol table info available. Thread 5 (LWP 168 ): #-1 0xfef00c6b in __lwp_park () from /lib/libc.so.1 No symbol table info available. Thread 4 (LWP 333 ): #-1 0xfef04717 in __read () from /lib/libc.so.1 No symbol table info available. Thread 3 (LWP 165 ): #-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 ----------- .xsession-errors (16835 sec old) --------------------- /etc/X11/gdm/Xsession: Beginning session setup... /etc/X11/gdm/Xsession: Setup done, will execute: /usr/dt/config/Xsession.jds --------------------------------------------------
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 483884 ***