Hide Forgot
abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 30011 bytes cmdline: /usr/libexec/empathy-chat component: empathy Attached file: coredump, 34635776 bytes crash_function: chat_spelling_build_menu executable: /usr/libexec/empathy-chat kernel: 2.6.38-0.rc5.git1.1.fc15.x86_64 package: empathy-2.91.91.1-1.fc15 rating: 4 reason: Process /usr/libexec/empathy-chat was killed by signal 6 (SIGABRT) release: Fedora release 15 (Lovelock) time: 1300657357 uid: 500 How to reproduce ----- I was typing something in #fedora-qa and noticed that the spellchecker highlighted all the words. I right-clicked one of the words and empathy crashed.
Created attachment 486513 [details] File: backtrace
*** Bug 704704 has been marked as a duplicate of this bug. ***
*** Bug 708539 has been marked as a duplicate of this bug. ***
can you verify that you have a dictionary installed, and still get this error? 'rpm -qa hunspell-*'
I've got it installed and still have the problem. sudo rpm -qa hunspell* hunspell-1.2.15-2.fc15.i686
(In reply to comment #5) > I've got it installed and still have the problem. > > sudo rpm -qa hunspell* > hunspell-1.2.15-2.fc15.i686 Where's the language specific dict? You've only got the hunspell libs installed and not a specific language package. That would obviously cause spell checking not to work. Your output from the previous rpm command should be something like this (obviously with your language-specific package): bpepple@localhost Desktop]$ rpm -qa hunspell* hunspell-1.2.8-18.fc13.i686 hunspell-en-0.20100322-1.fc13.noarch
'yum install hunspell-en' fixed it for me. Thanks Brian.
Package: empathy-3.0.2-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Right clic on spell checker
Package: empathy-3.0.2-1.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- right click after some chat and fiddling with utf 8 chars related to alignment
Backtrace analysis found this bug to be similar to bug #755630, closing as duplicate. Bugs which were found to be similar to this bug: bug #704704, bug #755630 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 755630 ***