Kontact 4.9.5, KDE 4.9.5, FreeBSD 9.1-RELEASE amd64 Reproducible: Always Steps to Reproduce: 1. Have the option "start with = overview" in Kontact, and an IMAP mail account. 2. Start Kontact 3. Click on an mail inbox that has new mail Actual Results: Kontact crashes Expected Results: The KMail module shall be started and show the mailbox that was clicked I consider any crash of severety > normal.
backtrace ?
Laurent, unfortunately the binaries for FreeBSD do not come with extra debug libs like in e.g. Kubuntu. And I don't want to compile myself from the ports -- it's easy, evrything is pre-configured, but it takes looooooong time, naturally. I could probably send you a backtrace w/o debug symbols, but that wouldn't be useful, n'est pas? I will ask the FreeBSD KDE maintainers to supply debug libs by default, IMHO that'd make sense. And, more important: you could not reproduce this? When I have a new mail, it crashes _everytime_ I clcik in the overview. Thus I click E-Mail on the sidebar to view the mail.
backtrace without debug symbols is still much better than no backtrace at all.
I can't reproduce it, and I can't debug without a crash or backtrace.
Created attachment 77929 [details] kontact-20130311-025941.kcrash You must have "start with overview" enabled. Quit any running Kontact (or KMail) with Ctrl+Q or Alt+F4 or from within the menu, clicking the X right/top corner id not enough. Then start Kontact. If there's new mail, this will be shown in the overview. Do _nothing_ else after starting Kontact freshly, than clicking on a mailbox with new mail in shown in the overview: crash. But if you do s/th different firts, e.g. go to EMail through the sidebar, then back to the overview, then you can savely click on the mailbox. Strange, but that's what I encounter.
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
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 set the bug status 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!
Dear Bug Submitter, 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!