GNOME Bugzilla – Bug 448073
crash in Tasks: on close, just after clo...
Last modified: 2007-07-02 15:47:23 UTC
Version: 2.10 What were you doing when the application crashed? on close, just after close evolution , I got ug buddy Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 714719232 vsize: 714719232 resident: 71921664 share: 39858176 rss: 71921664 rss_rlim: 18446744073709551615 CPU usage: start_time: 1181954645 rtime: 1357 utime: 1223 stime: 134 cutime:199 cstime: 45 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 46912496430688 (LWP 6007)] [New Thread 1094719824 (LWP 6574)] [New Thread 1136679248 (LWP 6068)] [New Thread 1147435344 (LWP 6067)] (no debugging symbols found) 0x0000003b19a0d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 141343
Thread 2 (Thread 1094719824 (LWP 6574))
----------- .xsession-errors (84 sec old) --------------------- Major opcode: 159 Minor opcode: 6 Resource id: 0x1405ad0 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 159 Minor opcode: 6 Resource id: 0x84 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x14069bc X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 159 Minor opcode: 6 Resource id: 0x14069bc --------------------------------------------------
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
This was bug buddy in action. I just put my email , after crash bug buddy create my login and done this report , I just tell you this because , you could receive more bugs like this , not from me but from other Fedora users. I will try reproduce the bug. Thanks
Sergio: Yes, I know about bug-buddy... ;-) Can you provide a better stacktrace, as described above?
Created attachment 91033 [details] evolution-data-server-1.10-bugreport (In reply to comment #3) > Sergio: Yes, I know about bug-buddy... ;-) > Can you provide a better stacktrace, as described above? ok a bug report with symbols
thanks for the new trace! this is the same issue as bug 452169, i'm marking it as a duplicate because the trace at bug 452169 contains more information. *** This bug has been marked as a duplicate of 452169 ***