GNOME Bugzilla – Bug 455530
crash in Tasks: Crashes on opening in KD...
Last modified: 2007-08-01 13:18:08 UTC
Version: 2.10 What were you doing when the application crashed? Crashes on opening in KDE or Gnome session Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000001 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 145432576 vsize: 145432576 resident: 37183488 share: 30838784 rss: 37183488 rss_rlim: 4294967295 CPU usage: start_time: 1184070071 rtime: 36 utime: 32 stime: 4 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209157920 (LWP 30762)] [New Thread -1261847664 (LWP 30809)] [New Thread -1251357808 (LWP 30808)] [New Thread -1240458352 (LWP 30800)] (no debugging symbols found) 0x00795402 in __kernel_vsyscall ()
+ Trace 146992
Thread 1 (Thread -1209157920 (LWP 30762))
----------- .xsession-errors --------------------- Resource id: 0x2200003 (evolution:30762): libsoup-CRITICAL **: soup_message_set_request: assertion `SOUP_IS_MESSAGE (msg)' failed (evolution:30762): libsoup-CRITICAL **: soup_message_set_flags: assertion `SOUP_IS_MESSAGE (msg)' failed (evolution:30762): libsoup-CRITICAL **: soup_session_send_message: assertion `SOUP_IS_MESSAGE (msg)' failed X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x14002cf X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 153 Minor opcode: 6 Resource id: 0x52 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 453932 ***