GNOME Bugzilla – Bug 483026
crash in Tasks: I just opened Evolution
Last modified: 2007-10-05 09:48:00 UTC
What were you doing when the application crashed? I just opened Evolution Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 132608000 vsize: 132608000 resident: 22986752 share: 16220160 rss: 22986752 rss_rlim: 4294967295 CPU usage: start_time: 1189126335 rtime: 135 utime: 115 stime: 20 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 -1209211168 (LWP 4306)] [New Thread -1291011184 (LWP 4346)] [New Thread -1228731504 (LWP 4318)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167461
Thread 1 (Thread -1209211168 (LWP 4306))
----------- .xsession-errors (4134 sec old) --------------------- beryl: Couldn't bind redirected window 0x240002b to texture beryl: pixmap 0x1000128 can't be bound to texture beryl: Couldn't bind redirected window 0x240002b to texture beryl: pixmap 0x1000128 can't be bound to texture beryl: Couldn't bind redirected window 0x240002b to texture beryl: pixmap 0x1000128 can't be bound to texture beryl: Couldn't bind redirected window 0x240002b to texture beryl: pixmap 0x1000128 can't be bound to texture beryl: Couldn't bind redirected window 0x240002b to texture beryl: pixmap 0x1000128 can't be bound to texture beryl: Couldn't bind redirected window 0x240002b to texture beryl: pixmap 0x1000128 can't be bound to texture beryl: Couldn't bind redirected window 0x240002b to texture ...Too much output, ignoring rest... --------------------------------------------------
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 431459 ***