Summary: | Kmail crashes on start | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Ferry <ferry.toth> |
Component: | composer | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | ferry.toth, null |
Priority: | NOR | ||
Version: | 5.5.3 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Ferry
2017-10-27 08:49:19 UTC
I just upgraded to kubuntu backport ppa: ~$ kmail -v kmail2 5.5.3 Still kontact (and kmail) crash on each start. I think it tries to recover an e-mail and then crashes again and again. How do I stop this? Starting from command line now shows: ~$ kontact [3491:3510:1031/170506.962118:ERROR:nss_util.cc(808)] After loading Root Certs, loaded==false: NSS error code: -8018 Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. sonnet.plugins.hspell: HSpellDict::HSpellDict: Init failed sonnet.core: Missing trigrams for languages: QSet("es_VE", "es_AR", "fr_LU", "es_BO", "es_PY", "en_AU", "es_CL", "es_NI", "fr_MC", "es_PE", "nl_BE", "es_CO", "de_BE", "fr_CA", "fr_CH", "es_CU", "de_CH", "es_CR", "es_PR", "fr_BE", "en_CA", "es_UY", "es_PA", "es_EC", "de_AT", "sv_FI", "es_GT", "de_LU", "es_DO", "es_HN", "es_MX", "es_SV", "en_GB") org.kde.pim.webengineviewer: It's not necessary to check database now KXMLGUI file found at deprecated location ("/home/ferry/.local/share/kontact/kontactsummary_part.rc") -- please use ${KXMLGUI_INSTALL_DIR} to install this file instead. [SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token ![SASL-XOAUTH2] - filling prompts ![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token !org.kde.pim.webengineviewer: Database already initialized. It's a bug in code if you call it twice. "Tag 'a' is not defined in message {<__kuit_internal_top__>Voor meer informatie over het gebruikt van Akregator, kij...}." "Tag 'a' is not defined in message {<__kuit_internal_top__>Voor meer informatie over het gebruikt van Akregator, kij...}." *** KMail got signal 11 (Exiting) *** Dead letters dumped. QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 12 and type 'Read', disabling... QSocketNotifier: Invalid socket 11 and type 'Read', disabling... [1:1:0100/000000.525574:ERROR:broker_posix.cc(41)] Invalid node channel message QSocketNotifier: Invalid socket 71 and type 'Read', disabling... QSocketNotifier: Invalid socket 89 and type 'Read', disabling... KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kontact path = /usr/bin pid = 3491 KCrash: Arguments: /usr/bin/kontact Segmentatiefout (geheugendump gemaakt) OK I managed to work around this in the following way: - I went into ~ferry/.local/share/kmail2/autosave - removed the file there Started kmail, problem gone. May I suggest that if kmail is repeatedly trying to recover an open e-mail that it should give up on that and clear the autosave folder? Unfortunately I really deleted the file, so we can't use it here now to reproduce the problem. Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Unfortunately (or fortunately?) I never had the issue again since removing the autosave file. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |