Re: Bug#403004: kmail: Kmail does not start after sarge->etch upgrade
On Thursday 14 December 2006 12:49, Ana Guerrero wrote:
> Hi,
>
> On Thu, Dec 14, 2006 at 09:22:36AM +0600, Alexander Litvinov wrote:
> > Package: kmail
> > Version: 4:3.5.5.dfsg.1-2
> > Severity: grave
> > Justification: renders package unusable
> >
> > I have updgraded from sarge to etch at 14 dec 2006. After this upgrade
> > my kmail does not start. Just after starting it shows KDE's crash
> > window with the text (not exact, translated from russian):
> > Application kmail has broken with signal 11 (SIGSEGV). Stack trace will
> > be included later.
>
> [...]
>
> I just reproduced this bug.
>
> But i agree with Josh Metzler about the severity:
>
> <jdmetz> I'm not sure it is grave, though, as I think it only applies to
> people using IMAP with a courier-imap server <jdmetz> that isn't "most
> people"
>
> Alexander:
> If you rename your file $HOME/.kde/share/config/kmailrc as kmailrc.old,
> you will be able to start kmail again, but all your account info will be
> lost. Basically, you will have to configure all your accounts in kmail
> again :(
>
> Ana
First, I've been assuming that you are accessing a courier-imap server for
at least one account. Is that true? (Are all your folders under the
inbox, or did you have to set INBOX. as the prefix to folders in sarge's
kmail?).
If not, then this is a different problem. If you are accessing a
courier-imap server, rather than reconfiguring all your accounts, I believe
that renaming or deleting $HOME/.kde/share/apps/kmail/imap/* should allow
kmail to start up. Deleting this is fine, as it is just kmail's cache of
all the e-mail headers. Since kmail in KDE 3.5 handles namespace/prefix
differently, if will have to redownload all the headers anyway. That was
enough to let me start kmail when I upgraded to KDE 3.5.
Josh
Reply to: