GNOME Bugzilla – Bug 447523
crash in Evolution: Start Evolution
Last modified: 2007-06-15 17:25:28 UTC
What were you doing when the application crashed? Start Evolution 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 Gray Icon Theme: gnome Memory status: size: 426065920 vsize: 426065920 resident: 27959296 share: 16834560 rss: 27959296 rss_rlim: 18446744073709551615 CPU usage: start_time: 1181825606 rtime: 82 utime: 74 stime: 8 cutime:0 cstime: 0 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 47519776804256 (LWP 5748)] (no debugging symbols found) 0x00002b380ac5dc2e in waitpid () from /lib64/libpthread.so.0
+ Trace 140921
Thread 1 (Thread 47519776804256 (LWP 5748))
----------- .xsession-errors --------------------- Gtk-CRITICAL **: gtk_list_store_get_path: assertion `iter->stamp == GTK_LIST_STORE (tree_model)->stamp' failed at /usr/lib/libDrakX/ugtk2.pm line 1243. X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1e002b9 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 155 Minor opcode: 6 Resource id: 0x1e002b9 QMenuData::removeItem: Index 0 out of range CalDAV Eplugin starting up ... X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 155 Minor opcode: 6 Resource id: 0x3b --------------------------------------------------
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 425129 ***