GNOME Bugzilla – Bug 480116
crash in e_util_unicode_get_utf8()?
Last modified: 2008-02-26 23:41:18 UTC
What were you doing when the application crashed? Distribution: Mandriva Linux release 2007.1 (Official) for x86_64 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 15:18:36 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Ia Ora Blue Icon Theme: gnome Memory status: size: 233058304 vsize: 233058304 resident: 9076736 share: 5664768 rss: 9076736 rss_rlim: 18446744073709551615 CPU usage: start_time: 1190613848 rtime: 44 utime: 33 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib64/evolution-data-server-1.10' (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 47631865754192 (LWP 6400)] [New Thread 1099184448 (LWP 6408)] [New Thread 1074006336 (LWP 6401)] (no debugging symbols found) 0x00002b5228033eae in waitpid () from /lib64/libc.so.6
+ Trace 165287
Thread 1 (Thread 47631865754192 (LWP 6400))
----------- .xsession-errors --------------------- Major opcode: 56 Minor opcode: 0 Resource id: 0x0 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 56 Minor opcode: 0 Resource id: 0x0 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 56 Minor opcode: 0 Resource id: 0x0 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x5c --------------------------------------------------
*** Bug 480113 has been marked as a duplicate of this bug. ***
*** Bug 453029 has been marked as a duplicate of this bug. ***
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, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Closing as the requested information hasn't been provided. Feel free to reopen if you have additional information :)