GNOME Bugzilla – Bug 447409
crash in Tasks: start it ...
Last modified: 2007-06-14 12:58:37 UTC
What were you doing when the application crashed? start it ... Distribution: redhat-4 Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 102039552 vsize: 102039552 resident: 46743552 share: 38002688 rss: 46743552 rss_rlim: 4294967295 CPU usage: start_time: 1181801707 rtime: 70 utime: 61 stime: 9 cutime:2 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 -1208236320 (LWP 2893)] (no debugging symbols found) 0x0064a402 in __kernel_vsyscall ()
+ Trace 140850
Thread 1 (Thread -1208236320 (LWP 2893))
----------- .xsession-errors (10 sec old) --------------------- ScimInputContextPlugin() QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMinimumSize: The smallest allowed size is (0,0) kwin: Fatal IO error: client killed compiz: No stencil buffer. Clipping of transformed windows is not going to be correct when screen is transformed. Loading "installonlyn" plugin X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2a0000c CalDAV Eplugin starting up ... (evolution:2893): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution:2893): e-utils-WARNING **: Plugin 'Bogofilter junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.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 425129 ***