Re: [gentoo-user] Kmail editor freezes

[Alan McKinnon]

Apparently, though unproven, at 16:10 on Sunday 10 October 2010, Daniel D 
Jones did opine thusly:

> On Sunday, October 10, 2010 03:06:08 Alan McKinnon wrote:
> > > Another clue is that it does a very similar thing when I press the Send
> > > button.  It freezes for about ten to fifteen seconds before sending.
> >
> > I agree it's likely caused by some network resource, I get similar things
> > happening to me (to use imap on exchange and it's addressbook from home I
> > have to run ssh tunnels through to the exchange machines. It's *easy* to
> > forget to run the script that sets them up)
> >
> > Look for things like imap stores not available and the hard one to track
> > down is accessing addressbooks using LDAP. The passwords are not stored
> > in kwallet! Check your various KResources configs and grep for likely
> > passwords in ~/.kde4/share/config
>
> I'm still looking and investigating.  No luck yet.
>
> It doesn't appear to be a network problem for a couple of reasons.  I run
> my own mail server and it's sitting right here on my local subnet.
> There's no problem communicating with it on either port 25 or 110.  (I
> don't use imap, so that isn't involved.)  Kmail itself doesn't exhibit any
> symptoms when I'm reading mail.  It's only when I have Composer open.
>
> I'm not using LDAP or any sort of external addressbook, and I'm not sure
> why Composer would be accessing the addressbook while I'm in the middle of
> writing an email.  I can see it happening on either opening or closing
> Composer, but not mid sentence.  (Which, of course, doesn't mean it isn't
> happening.  I'm just not sure why it would.)
>
> The only external resource I can think of that Composer would be accessing
> as I'm writing is the spellchecker and turning off automatic (ie inline)
> spellchecking doesn't mitigate the issue.
>
> Is anyone using or tried to use an external editor with Kmail recently?  If
> not, would someone be willing to take a moment and attempt to do so and see
> if it works correctly for you?

This is starting to look like strace -p is your good friend.

You'll get heaps of output most likely but at least there's a good chance we 
can pin down what resource it's trying to access.



-- 
alan dot mckinnon at gmail dot com