GNOME Bugzilla – Bug 514433
crash in Evolution Mail and Calendar: Trying to start the app
Last modified: 2008-02-15 10:14:02 UTC
What were you doing when the application crashed? Trying to start the app Distribution: Solaris Express Community Edition snv_76 X86 Gnome Release: 2.20.0 2007-10-08 (Sun Microsystems, Inc.) BugBuddy Version: 2.20.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus Memory status: size: 221605888 vsize: 221605888 resident: 56623104 share: 0 rss: 56623104 rss_rlim: 0 CPU usage: start_time: 0 rtime: 150 utime: 1307894 stime: 197450 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) sol-thread active. Retry #1: Retry #2: Retry #3: Retry #4: [New LWP 1 ] [New Thread 1 (LWP 1)]
+ Trace 188110
Thread 1 (LWP 1)
Thread 8 (Thread 11 ): #-1 0xfe2af4fb in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 7 (Thread 3 (LWP 3)): #-1 0xfe2b2ee7 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 6 (Thread 2 (LWP 2)): #-1 0xfe2b2ee7 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 5 (LWP 2 ): #-1 0xfe2b2ee7 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 4 (LWP 3 ): #-1 0xfe2b2ee7 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 3 (LWP 11 ): #-1 0xfe2af4fb in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 2 (Thread 1 (LWP 1)): #-1 0xfe2b3497 in _waitid () from /usr/lib/libc.so.1 No symbol table info available. Thread 1 (LWP 1 ): #-1 0xfe2b3497 in _waitid () from /usr/lib/libc.so.1 No symbol table info available. #-1 0xfe2b3497 in _waitid () from /usr/lib/libc.so.1
This seems a crash in the Solaris version of Gnome-VFS. Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 514532 ***