KMail was just about to finish downloading new E-Mails when it crashed. Because i started KMail in a Konsole-window, the last messages in the konsole-window read [warn] epoll_wait: Bad file descriptor Before that, KMail sometimes shows a message saing that Akonadi is not running and on the konsole-window i read s.th. akonadicore_log: Socket error occurred: "QLocalSocket: Remote closed" and afterward akonadi gets restarted. The crash after download is relatively new, the closing of akonadi also happend with Qt-5.6.9999 (gentoo-live-ebuild). The crash can be reproduced sometimes. Reproducible: Sometimes Steps to Reproduce: 1. Open Kmail 2. Check mails 3. crash Expected Results: Kmail should not crash. The part of akonadi not running happened also with Qt-5.6.9999. Application: kmail (5.2.49 pre (QtWebEngine)) (Compiled from sources) Qt Version: 5.7.0 Frameworks Version: 5.23.0 Operating System: Linux 4.6.0-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Backtrace: Application: KMail (kmail), signal: Segmentation fault. Backtrace can be provided. I can't paste it due to it's size.
Created attachment 99458 [details] Crash-report using the Crash Reporting Assistant including backtrace
Just had pages and pages of this warning on kmail 5.3.0 using Qt: 5.6.1 KDE Frameworks: 5.25.0 kf5-config: 1.0 KDE Plasma: 5.7.3 Kernel: 4.7.1-1-default "openSUSE Tumbleweed (20160820) (x86_64)"
had the same problems after updating to the newest packages of opensuse tumbleweed. Akonadiserver always restarts with the following message: Database "akonadi" opened using driver "QMYSQL" Executing search "searchUpdate-1472078875" searchUpdateResultsAvailable 270 0 results Got 0 results, out of which 0 are already in the collection Added 0 Search done "searchUpdate-1472078875" (without remote search) Search update finished All results: 0 Removed results: 0 Executing search "searchUpdate-1472078875" log_akonadiplugin_indexer: unknown term "attachment" "[\n0: akonadiserver() [0x574fe6]\n1: akonadiserver() [0x575300]\n2: /lib64/libc.so.6(+0x349f0) [0x7f7589a619f0]\n3: [0x7f7560050030]\n]\n" ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error) So i thougt it might have to do something with email Search. I went to Kontact Search Folder and deleted the folder "last search". This brings Kontact to crash. But after starting Kontact again the problem with akonadiserver restart was gone. To verify i did again in Kontact a search, after this i had the same behaviour. Akonadiserver begins to restart again. After delete the last search folder again akonadiserver is stable. Regards, Thomas
(In reply to wurfbaum from comment #3) > had the same problems after updating to the newest packages of opensuse > tumbleweed. > Akonadiserver always restarts with the following message: > Database "akonadi" opened using driver "QMYSQL" > Executing search "searchUpdate-1472078875" > searchUpdateResultsAvailable 270 0 results > Got 0 results, out of which 0 are already in the collection > Added 0 > Search done "searchUpdate-1472078875" (without remote search) > Search update finished > All results: 0 > Removed results: 0 > Executing search "searchUpdate-1472078875" > log_akonadiplugin_indexer: unknown term "attachment" > "[\n0: akonadiserver() [0x574fe6]\n1: akonadiserver() [0x575300]\n2: > /lib64/libc.so.6(+0x349f0) [0x7f7589a619f0]\n3: [0x7f7560050030]\n]\n" > ProcessControl: Application 'akonadiserver' returned with exit code 255 > (Unknown error) > > > So i thougt it might have to do something with email Search. > I went to Kontact Search Folder and deleted the folder "last search". This > brings Kontact to crash. But after starting Kontact again the problem with > akonadiserver restart was gone. > > To verify i did again in Kontact a search, after this i had the same > behaviour. Akonadiserver begins to restart again. After delete the last > search folder again akonadiserver is stable. > > Regards, > Thomas Cheers Thomas, that seems to work for me as well. kmail still crashes for other reasons though
Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Status correction.
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!