GNOME Bugzilla – Bug 522981
crash in Evolution Mail and Calendar: Clicked OK after looking...
Last modified: 2008-05-26 05:02:48 UTC
What were you doing when the application crashed? Clicked OK after looking at a personal contact. 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: 224493568 vsize: 224493568 resident: 34734080 share: 282624 rss: 34734080 rss_rlim: 0 CPU usage: start_time: 0 rtime: 4834 utime: 25037847 stime: 23309947 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 192693
Thread 1 (LWP 1)
Thread 20 (Thread 11 (LWP 11)): #-1 0xfe2a4cd5 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 19 (Thread 10 (LWP 10)): #-1 0xfe2a4cd5 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 18 (Thread 9 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 17 (Thread 8 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 16 (Thread 7 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 15 (Thread 6 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 14 (Thread 5 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 13 (Thread 4 (LWP 4)): #-1 0xfe2a4705 in __fcntl_syscall () from /usr/lib/libc.so.1 No symbol table info available. Thread 12 (Thread 2 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 11 (LWP 2 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 10 (LWP 4 ): #-1 0xfe2a4705 in __fcntl_syscall () from /usr/lib/libc.so.1 No symbol table info available. Thread 9 (LWP 5 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 8 (LWP 6 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 7 (LWP 7 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 6 (LWP 8 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 5 (LWP 9 ): #-1 0xfe2a0c99 in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 4 (LWP 10 ): #-1 0xfe2a4cd5 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 3 (LWP 11 ): #-1 0xfe2a4cd5 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 2 (Thread 1 (LWP 1)): #-1 0xfe2a56d5 in __waitid () from /usr/lib/libc.so.1 No symbol table info available. Thread 1 (LWP 1 ): #-1 0xfe2a56d5 in __waitid () from /usr/lib/libc.so.1 No symbol table info available. #-1 0xfe2a56d5 in __waitid () from /usr/lib/libc.so.1
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. Could you please install some debugging packages [1], start the application as normal, and 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] debugging packages for evolution, evolution-data-server, evolution-exchange, gtkhtml, gtk, glib, libsoup, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
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 415623 ***