Created attachment 47564 [details] DO NOT RUN THIS SCRIPT.. unless you know what you are doing Version: unspecified OS: Linux When I clean (see attached clean-kde.sh) my devel user's ~/ of all kde/akonadi files, then start kmail fresh with "kmail --nofork" it takes two sometimes three executions of this command for kmail to start successfully. Reproducible: Always Steps to Reproduce: 1. run 'bash clean-kde.sh' 2. execute 'kmail --nofork' 3. see the "starting akonadi server" progress bar appear 4. see the akonadi server self-test tool report errors 5. close the server self-test tool 6. execute 'kmail --nofork' 7. goto 3 and repeat until kmail starts sucessfully It has taken up to 4 tries, for kmail to start properly.
Created attachment 47565 [details] debug from executing kmail --nofork the first time
Created attachment 47566 [details] debug from executing kmail --nofork the second time (still doesn't startup correctly)
Created attachment 47567 [details] debug from executing kmail --nofork a third time (this time it starts up)
Having KMail start up on the first run is important for making a good impression.
Casey--can you re-test this? I think my recent changes to specialcollections during startup might have resolved it.
Any news on this?
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!
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!