GNOME Bugzilla – Bug 359957
crash in Evolution: tried to go to the trash...
Last modified: 2006-10-10 12:23:29 UTC
What were you doing when the application crashed? tried to go to the trash to see all the spam i deleted surprised to see nothing in it clicking or any other folder after that, or closing evolution leads to a crash Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 133156864 vsize: 0 resident: 133156864 share: 0 rss: 28610560 rss_rlim: 0 CPU usage: start_time: 1160068984 rtime: 0 utime: 547 stime: 0 cutime:509 cstime: 0 timeout: 38 it_real_value: 0 frequency: 457 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232726352 (LWP 5965)] [New Thread -1286485088 (LWP 6131)] [New Thread -1294877792 (LWP 6128)] [New Thread -1317823584 (LWP 6126)] [New Thread -1277699168 (LWP 6009)] [New Thread -1269306464 (LWP 5998)] [New Thread -1260913760 (LWP 5997)] [New Thread -1252521056 (LWP 5996)] _______________________________________________________________________________ eax:FFFFFE00 ebx:00001855 ecx:BFAEE864 edx:00000000 eflags:00000246 esi:0000000B edi:08221038 esp:BFAEE794 ebp:BFAEE898 eip:FFFFE410 cs:0073 ds:007B es:007B fs:0000 gs:0033 ss:007B o d I t s Z a P c [007B:BFAEE794]---------------------------------------------------------[stack] BFAEE7C4 : 10 A0 35 08 FB 23 62 B7 - A4 C8 62 B7 D0 26 64 B7 ..5..#b...b..&d. BFAEE7B4 : 64 E8 AE BF 00 00 00 00 - 2C 41 63 B7 7C E8 AE BF d.......,Ac.|... BFAEE7A4 : 14 F7 ED B7 00 00 00 00 - B6 B1 EA B7 55 18 00 00 ............U... BFAEE794 : 98 E8 AE BF 00 00 00 00 - 64 E8 AE BF 9B 16 1A B7 ........d....... [007B:08221038]---------------------------------------------------------[ data] 08221038 : F0 A2 21 08 02 00 00 00 - 00 00 00 00 E0 0F 21 00 ..!...........!. 08221048 : 00 0E 00 00 00 00 00 00 - 00 C0 56 08 14 00 00 00 ..........V..... [0073:FFFFE410]---------------------------------------------------------[ code] 0xffffe410 <__kernel_vsyscall+16>: pop %ebp 0xffffe411 <__kernel_vsyscall+17>: pop %edx 0xffffe412 <__kernel_vsyscall+18>: pop %ecx 0xffffe413 <__kernel_vsyscall+19>: ret 0xffffe414 <__kernel_vsyscall+20>: nop 0xffffe415 <__kernel_vsyscall+21>: nop ------------------------------------------------------------------------------ 0xffffe410 in __kernel_vsyscall ()
+ Trace 74743
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
I have the same issue. Here is the full backtrace: Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1500547392 (LWP 10150)] [New Thread -1595450448 (LWP 10222)] [New Thread -1585964112 (LWP 10219)] [New Thread -1577571408 (LWP 10188)] [New Thread -1569178704 (LWP 10187)] [New Thread -1560786000 (LWP 10186)] [New Thread -1550488656 (LWP 10185)] [New Thread -1542095952 (LWP 10183)] [New Thread -1533703248 (LWP 10182)] [New Thread -1524917328 (LWP 10181)] [New Thread -1516524624 (LWP 10179)] [New Thread -1506309200 (LWP 10178)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 74748
Thread 5 (Thread -1569178704 (LWP 10187))
I don't if it's related but if I visit the trash when it is empty, it displays a popup that contains : "Erreur durant la génération de la liste des message" (error while generating message list) Erreur lors de l'execution de l'expression de recherche : Unknown type in parse tree: 140427752 : (and (match-all (and (not (system-flag "deleted")) (not (system-flag "junk")))) ) (error while executing search expression : ... )
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. I believe this to actually be the same issue as bug 360237. *** This bug has been marked as a duplicate of 360237 ***