GNOME Bugzilla – Bug 504194
crash in Tasks:
Last modified: 2007-12-18 10:46:32 UTC
Version: 2.10 What were you doing when the application crashed? 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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 128888832 vsize: 128888832 resident: 41218048 share: 30289920 rss: 41218048 rss_rlim: 4294967295 CPU usage: start_time: 1197963161 rtime: 313 utime: 279 stime: 34 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 -1209129248 (LWP 2071)] [New Thread -1246016624 (LWP 2191)] [New Thread -1235526768 (LWP 2169)] [New Thread -1225036912 (LWP 2164)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182203
Thread 4 (Thread -1225036912 (LWP 2164))
----------- .xsession-errors --------------------- Minor opcode: 6 Resource id: 0x14002e6 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1400268 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x4d (process:2216): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function (process:2216): Gtk-CRITICAL **: gtk_clipboard_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed Adobe FlashPlayer: gtk_clipboard_get(GDK_SELECTION_PRIMARY); failed. Trying to call gtk_init(0,0); --------------------------------------------------
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 339602 ***