GNOME Bugzilla – Bug 521733
crash in Tasks: I was just readng the em...
Last modified: 2008-03-15 20:54:12 UTC
Version: 2.10 What were you doing when the application crashed? I was just readng the emails and currently clicked another email to view when tha application crashed. Here is what I found the Crash details: 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.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 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: 165523456 vsize: 165523456 resident: 59416576 share: 41865216 rss: 59416576 rss_rlim: 4294967295 CPU usage: start_time: 1205217353 rtime: 70245 utime: 68895 stime: 1350 cutime:15659 cstime: 1194 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208686880 (LWP 19517)] [New Thread -1344271472 (LWP 25386)] [New Thread -1290761328 (LWP 25385)] [New Thread -1323291760 (LWP 19621)] [New Thread -1273394288 (LWP 19544)] [New Thread -1238819952 (LWP 19540)] (no debugging symbols found) 0x00132402 in __kernel_vsyscall ()
+ Trace 192056
Thread 1 (Thread -1208686880 (LWP 19517))
----------- .xsession-errors (92928 sec old) --------------------- 12:38:58,950 DEBUG [main]: Mesh request sent >: Set RF channel: Channel = 18 (2440 MHz) 12:38:58,951 DEBUG [main]: Mesh request sent >: A5 03 17 21 12 0E 12:38:58,961 DEBUG [Mesh serial port reader thread]: Mesh message received <: RSP success 12:38:58,961 DEBUG [Mesh serial port reader thread]: Mesh message received <: A5 03 00 21 17 20 12:39:01,111 DEBUG [JTestBench Task Thread]: PSEM request sent >: PSEM Read request [STDTable0, Full read] 12:39:01,114 DEBUG [JTestBench Task Thread]: PSEM message sent >: 30 00 00 12:39:01,130 DEBUG [JTestBench Task Thread]: Encryption information: 12:39:01,131 DEBUG [JTestBench Task Thread]: Encryption Key = [44 44 44 44 44 44 44 44 11 11 11 11 11 11 11 11] 12:39:01,131 DEBUG [JTestBench Task Thread]: Message = [80 03 30 00 00 00 D5 CA] 12:39:01,131 DEBUG [JTestBench Task Thread]: Encrypted Message = [E2 58 A9 32 BD B0 96 EF] 12:39:01,132 DEBUG [JTestBench Task Thread]: C12.22 message sent >: E0 20 A2 05 A8 77 BE 97 36 A6 01 13 80 01 0B 81 04 91 64 6B 96 A8 01 01 BE 08 E2 58 A9 32 BD B0 96 EF 12:39:01,136 DEBUG [JTestBench Task Thread]: Mesh request sent >: Transmit: Destination address = 00147700000F8BB6 12:39:01,136 DEBUG [JTestBench Task Thread]: Mesh request sent >: A5 2E 11 22 01 00 14 77 00 00 0F 8B B6 22 E0 20 A2 05 A8 77 BE 97 36 A6 01 13 80 01 0B 81 04 91 64 6B 96 A8 01 01 BE 08 E2 58 A9 32 BD ...Too much output, ignoring rest... --------------------------------------------------
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 455077 ***