GNOME Bugzilla – Bug 587359
evolution crashes when spell-checking a mail
Last modified: 2009-07-01 19:32:49 UTC
I have a 100% reproducible crash with evo, when I want to replace a miss-spelled word by a suggestion. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7f75b00 (LWP 20325)] 0x08a006d2 in free () from /lib/tls/i686/cmov/libc.so.6 (gdb) thread apply all bt
+ Trace 216254
Thread 1 (Thread 0xb7f75b00 (LWP 20325))
evolution version is 2.27.3 libgtkspell is 2.0.13-2 if it matters
Can you provide some steps to reproduce? For example, I see from the stack trace you were using the spell check dialog as opposed to inline spell checking. That may be important. Were you in HTML or text mode? Font face? Enabled dictionaries? Does it happen for all spell check corrections or just "committed"?
(In reply to comment #1) > Can you provide some steps to reproduce? > > For example, I see from the stack trace you were using the spell check dialog > as opposed to inline spell checking. That may be important. > > Were you in HTML or text mode? Font face? Enabled dictionaries? Does it > happen for all spell check corrections or just "committed"? > Hello Matthew, Actually the crash happens with the in-line and with the spell-check dialog, my mail was in text mode. The complete mail I sent is http://mail.gnome.org/archives/gnome-doc-list/2009-June/msg00032.html To reproduce the crash (I was able to reproduce it 5 or 6 times) this is rather simple: - I had my mail all written with the typo on "commited" (instead of committed) and "bluetooth" was also marked as an error. - I opened the menu for spell-checking (don't remember the menu path and name) - the first correction proposed was for "commited", the spell check dialog proposed me several corrections, "committed" was the third. - I selected "committed", and pressed the button "Replace" - Kaboom. for the other questions, I'll answer tonight.
*** Bug 587455 has been marked as a duplicate of this bug. ***
*** Bug 586569 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 584243 ***