On Tue, Dec 19, 2006 at 11:27:35AM +0100, Agustin Martin wrote: > No, is not working, I was using the info from > > http://bugs.kde.org/show_bug.cgi?id=125487 > > together with your file from > > https://bugs.kde.org/show_bug.cgi?id=128067 > > and did not follow your exact steps. So I am unmerging and leaving things as > they were before. Also, I do not think KDE#125487 and KDE#128067 are the > same problem, KDE#125487 seems related to version inconsistencies > while KDE#128067 seems completely different, as a matter of fact backtraces > seem different, and I have my doubts that is an aspell problem.
Some aditional info, I have seen this aspell bug report [#351240: libgtkspell0: crashes when you call popup menu on word written in Cyrlic] and after the backtrace it seems the same problem, but from the gtk side. As reported to aspell.sf I could also reproduce this with kword and the string "123". So, seems that when the program sends so aspell a string containing non-valid chars, either libaspell return something invalid or gtkspell/kword do not know how to handle it (depending on POV). Kevin Atkinson has just released aspell 0.60.5, is better if we wait until Brian can prepare an experimental package for it (note that etch is currently frozen). -- Agustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
