GNOME Bugzilla – Bug 543079
crash in Evolution: Open a mail with multipl...
Last modified: 2008-07-16 04:57:00 UTC
What were you doing when the application crashed? Open a mail with multiple attachments. Click the 'expand inline' button on two of them fast enough that the first one doesn't have time to expand before the second button is clicked. Reliable KABOOM. All fall down go die. 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.25-gentoo-r5 #5 PREEMPT Mon Jul 7 22:49:20 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: 411688960 vsize: 411688960 resident: 202227712 share: 28233728 rss: 202227712 rss_rlim: 4294967295 CPU usage: start_time: 1216043919 rtime: 166502 utime: 134990 stime: 31512 cutime:80 cstime: 16 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 0xb684a6c0 (LWP 21403)] [New Thread 0xa2d75b90 (LWP 22556)] [New Thread 0xa7afeb90 (LWP 21466)] [New Thread 0xa3fffb90 (LWP 21464)] [New Thread 0xace34b90 (LWP 21448)] [New Thread 0xac633b90 (LWP 21446)] [New Thread 0xad6f2b90 (LWP 21411)] [New Thread 0xadf02b90 (LWP 21410)] [New Thread 0xae7ffb90 (LWP 21409)] _______________________________________________________________________________ eax:FFFFFE00 ebx:00006393 ecx:BF8C613C edx:00000000 eflags:00200293 esi:BF8C613C edi:00000000 esp:BF8C6054 ebp:BF8C6158 eip:FFFFE424 cs:0073 ds:007B es:007B fs:0000 gs:0033 ss:007B o d I t S z A p C [007B:BF8C6054]---------------------------------------------------------[stack] BF8C6084 : 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ BF8C6074 : 3C 61 8C BF 00 00 00 00 - 00 00 00 00 00 00 00 00 <a.............. BF8C6064 : F4 BF 47 B7 00 00 00 00 - 25 EE 41 B7 93 63 00 00 ..G.....%.A..c.. BF8C6054 : 58 61 8C BF 00 00 00 00 - 3C 61 8C BF AB 2F 3B B7 Xa......<a.../;. [007B:BF8C613C]---------------------------------------------------------[ data] BF8C613C : 40 43 3C B7 93 63 00 00 - FF FF FF FF FF FF FF FF @C<..c.......... BF8C614C : F4 BF 47 B7 00 00 00 00 - D8 61 8C BF A8 61 8C BF ..G......a...a.. [0073:FFFFE424]---------------------------------------------------------[ code] 0xffffe424 <__kernel_vsyscall+16>: pop %ebp 0xffffe425 <__kernel_vsyscall+17>: pop %edx 0xffffe426 <__kernel_vsyscall+18>: pop %ecx 0xffffe427 <__kernel_vsyscall+19>: ret 0xffffe428: add %ch,(%esi) 0xffffe42a: jae 0xffffe494 ------------------------------------------------------------------------------ 0xffffe424 in __kernel_vsyscall ()
+ Trace 202877
----------- .xsession-errors (56305 sec old) --------------------- (acroread:21502): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (acroread:21502): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject' (acroread:21502): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (acroread:21502): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (acroread:21502): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject' (acroread:21502): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (acroread:21502): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' 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 ***