[kmail2] [Bug 386238] Kmail crashes on start

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=386238

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #6 from Bug Janitor Service  ---
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!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 386238] Kmail crashes on start

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=386238

--- Comment #5 from Bug Janitor Service  ---
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!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 386238] Kmail crashes on start

[Ferry]

https://bugs.kde.org/show_bug.cgi?id=386238

--- Comment #4 from Ferry  ---
Unfortunately (or fortunately?) I never had the issue again since removing the
autosave file.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 386238] Kmail crashes on start

[Justin Zobel]

https://bugs.kde.org/show_bug.cgi?id=386238

Justin Zobel  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #3 from Justin Zobel  ---
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!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 386238] Kmail crashes on start

[Francesco Turco]

https://bugs.kde.org/show_bug.cgi?id=386238

Francesco Turco  changed:

   What|Removed |Added

 CC||ftu...@fastmail.fm

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 386238] Kmail crashes on start

[Ferry]

https://bugs.kde.org/show_bug.cgi?id=386238

--- Comment #2 from Ferry  ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 386238] Kmail crashes on start

[Ferry]

https://bugs.kde.org/show_bug.cgi?id=386238

Ferry  changed:

   What|Removed |Added

 CC||ft...@telfort.nl

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 386238] Kmail crashes on start

[Ferry]

https://bugs.kde.org/show_bug.cgi?id=386238

--- Comment #1 from Ferry  ---
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/00.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)

-- 
You are receiving this mail because:
You are the assignee for the bug.