GNOME Bugzilla – Bug 481356
crash in Tasks: sorting email
Last modified: 2007-10-06 12:22:40 UTC
What were you doing when the application crashed? sorting email 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.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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 149786624 vsize: 149786624 resident: 32083968 share: 20246528 rss: 32083968 rss_rlim: 4294967295 CPU usage: start_time: 1191082838 rtime: 1597 utime: 1469 stime: 128 cutime:54 cstime: 23 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 -1208858912 (LWP 3656)] [New Thread -1235928176 (LWP 3756)] [New Thread -1274442864 (LWP 3695)] [New Thread -1309357168 (LWP 3684)] (no debugging symbols found) 0x00428402 in __kernel_vsyscall ()
+ Trace 166219
Thread 1 (Thread -1208858912 (LWP 3656))
----------- .xsession-errors --------------------- Transfer ACCEPTED by: PictureNotifierTask QGArray::find: Index 0 out of range Transfer ACCEPTED by: PictureNotifierTask Transfer ACCEPTED by: PictureNotifierTask CLIENT: Task: Task::done() CLIENT: Task: emitting finished CLIENT: Task: Task::done() CLIENT: Task: emitting finished Transfer ACCEPTED by: StatusNotifierTask CLIENT: Task: Task::done() CLIENT: Task: emitting finished CLIENT: Task: Task::done() CLIENT: Task: emitting finished Transfer ACCEPTED by: StatusNotifierTask Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 431342 ***