Re: No backend found for spell checking

2016-09-02 Thread Tim Folger 
On Friday, September 2, 2016 7:38:13 AM MDT Pino Toscano wrote:
> In data giovedì 1 settembre 2016 23:28:04 CEST, Tim Folger ha scritto:
> > I'm running debian testing, which I upgrade every few days. After my most
> > recent upgrade, spell checking no longer works in kde. In system settings
> > >
> > regional settings > spell check it says "No back end found for spell
> > checking." The same message appears when I try to check the spellingn in a
> > message before sending it. I'm using kmail version 5.2.3, kde plasma
> > version 5.6.5, and kde frameworks version 5.25.0. Has anyone else
> > encountered this?
> Check whether sonnet-plugins is installed (installing it if not).

Thanks--installing sonnet-plugins solved the issue.

Re: No backend found for spell checking

2016-09-01 Thread Pino Toscano 
In data giovedì 1 settembre 2016 23:28:04 CEST, Tim Folger ha scritto:
> I'm running debian testing, which I upgrade every few days. After my most 
> recent upgrade, spell checking no longer works in kde. In system settings > 
> regional settings > spell check it says "No back end found for spell 
> checking." The same message appears when I try to check the spellingn in a 
> message before sending it. I'm using kmail version 5.2.3, kde plasma version 
> 5.6.5, and kde frameworks version 5.25.0. Has anyone else encountered this?

Check whether sonnet-plugins is installed (installing it if not).

-- 
Pino Toscano

signature.asc
Description: This is a digitally signed message part.

No backend found for spell checking

2016-09-01 Thread Tim Folger 
Hi,

I'm running debian testing, which I upgrade every few days. After my most 
recent upgrade, spell checking no longer works in kde. In system settings > 
regional settings > spell check it says "No back end found for spell 
checking." The same message appears when I try to check the spellingn in a 
message before sending it. I'm using kmail version 5.2.3, kde plasma version 
5.6.5, and kde frameworks version 5.25.0. Has anyone else encountered this?

Thanks,

Tim