Bug#403004: kmail: Kmail does not start after sarge-etch upgrade
Hi, please post outpot of $ grep ImapPath ~/.kde/share/config/kmailrc pgpO0M9xH5vGo.pgp Description: PGP signature
Bug#403004: kmail: Kmail does not start after sarge-etch upgrade
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403004: kmail: Kmail does not start after sarge-etch upgrade
Sorry for late reply, I have debian machine at home and I have not chance to rich it yet. 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 I am using kmail to handle local mail from misc daemons and use cyrus imap account to read work emails. 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 :( This is not too hard, thanks for the solution. 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?). All my folders are under INBOX. (This is the default behavior for cyrus without shared folders) 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. I will try today evening (~12 hours after this mail sent). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403004: kmail: Kmail does not start after sarge-etch upgrade
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. When I am running kmail from konsole I saw: -- konsole start -- kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name move_message_to_folder kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name copy_message_to_folder kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name jump_to_folder kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name remove_duplicate_messages kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name cancel kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name inc_current_folder kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name dec_current_folder kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name select_current_folder kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name inc_current_message kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name dec_current_message kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name select_current_message kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name delete kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name edit kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel( kacc = 0x8367990 ): KAccel object already contains an action name display_message ERROR: Communication problem with kmail, it probably crashed. KCrash: Application 'kmail' crashing... -- konsole end -- The stack trace is: -- stack start -- (no debugging symbols found) Using host libthread_db library /lib/tls/libthread_db.so.1. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1248647488 (LWP 3514)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no
