GNOME Bugzilla – Bug 537879
crash in Evolution: Reading a mail with seve...
Last modified: 2008-06-12 04:34:05 UTC
What were you doing when the application crashed? Reading a mail with several attachments, the last three GIF files. Click 'view inline' on each GIF file, last to first, without waiting for each one to appear. The button on the middle one appeared to jam 'down', which may have been the point of crash. Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.20.3 2008-02-20 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.24-gentoo-r4 #2 PREEMPT Sat Apr 12 13:27:19 BST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Smooth-Tangerine-Dream Icon Theme: nuvola Memory status: size: 581783552 vsize: 581783552 resident: 351674368 share: 31477760 rss: 351674368 rss_rlim: 4294967295 CPU usage: start_time: 1212416498 rtime: 744429 utime: 619938 stime: 124491 cutime:8 cstime: 65 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Really redefine built-in command "frame"? (y or n) [answered Y; input not from terminal] Really redefine built-in command "thread"? (y or n) [answered Y; input not from terminal] Really redefine built-in command "start"? (y or n) [answered Y; input not from terminal] Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb68f06c0 (LWP 7432)] [New Thread 0xa9bffb90 (LWP 31231)] [New Thread 0xab229b90 (LWP 31218)] [New Thread 0xae0a3b90 (LWP 10077)] [New Thread 0xabe21b90 (LWP 7484)] [New Thread 0xabf30b90 (LWP 7477)] [New Thread 0xac7ecb90 (LWP 7448)] [New Thread 0xad0a1b90 (LWP 7444)] [New Thread 0xad8a2b90 (LWP 7442)] [New Thread 0xae904b90 (LWP 7440)] _______________________________________________________________________________ eax:FFFFFE00 ebx:00007DB8 ecx:BF92A87C edx:00000000 eflags:00200293 esi:BF92A87C edi:00000000 esp:BF92A794 ebp:BF92A898 eip:FFFFE410 cs:0073 ds:007B es:007B fs:0000 gs:0033 ss:007B o d I t S z A p C [007B:BF92A794]---------------------------------------------------------[stack] BF92A7C4 : 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ BF92A7B4 : 7C A8 92 BF 00 00 00 00 - 00 00 00 00 00 00 00 00 |............... BF92A7A4 : F4 4F 48 B7 00 00 00 00 - 25 7E 42 B7 B8 7D 00 00 .OH.....%~B..}.. BF92A794 : 98 A8 92 BF 00 00 00 00 - 7C A8 92 BF AB BF 3B B7 ........|.....;. [007B:BF92A87C]---------------------------------------------------------[ data] BF92A87C : 40 D3 3C B7 B8 7D 00 00 - FF FF FF FF FF FF FF FF @.<..}.......... BF92A88C : F4 4F 48 B7 00 00 00 00 - 18 A9 92 BF E8 A8 92 BF .OH............. [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: nop 0xffffe415: nop ------------------------------------------------------------------------------ 0xffffe410 in __kernel_vsyscall ()
+ Trace 200191
----------- .xsession-errors (39958 sec old) --------------------- (evolution:7432): Bonobo-CRITICAL **: impl_set_prop: assertion `value != NULL' failed (evolution:7432): Gtk-CRITICAL **: gtk_icon_info_free: assertion `icon_info != NULL' failed (evolution:7432): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion `icon_info != NULL' failed (evolution:7432): Bonobo-CRITICAL **: impl_set_prop: assertion `value != NULL' failed (evolution:7432): Gtk-CRITICAL **: gtk_icon_info_free: assertion `icon_info != NULL' failed (evolution:7432): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion `icon_info != NULL' failed (evolution:7432): Bonobo-CRITICAL **: impl_set_prop: assertion `value != NULL' failed ...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 511337 ***