Version: (using Devel) OS: Linux Installed from: Compiled sources Changes in the CMake configuration are lost when KDevelop crashes. Example: 1. You import a new CMakeLists.txt project 2. KDevelop asks for the CMake build directory, which you set 3. KDevelop crashes 4. KDevelop is restarted manually 5. On startup, it asks for the CMake build directory again Changes in the CMake configuration should be saved immediately.
Do you have a backtrace from the crash? Because in fact the code does try to save the information immediately (it calls sync on the kconfig). Hence I think the problem is that it crashed before it could write out all the config options and save the file. Without a backtrace however I don't have any other option than closing this as worksforme.
The crash and the backtrace is at bug 204092.
Note that the crash in question happened long after the CMakeLists.txt was opened and configured.
Also, it is not the first time this happened for me, I've seen this with other crashes as well. (sorry for the many small comments)
Hmm, I'm tempted to move this to kdelibs then, we're executing KConfigGroup::sync() right after reading the data from the dialog.
So this should be moved to kdelibs. The sync call exists. This shouldn't be VHI anyway, this is not a major showstopper.
(In reply to comment #6) > So this should be moved to kdelibs. > > The sync call exists. This shouldn't be VHI anyway, this is not a major > showstopper. I've set it to VHI so we're "aware" of it and can do something about it. I didn't want to do a final decision on the move myself :) Moving it now.
(In reply to Thomas McGuire from comment #4) > Also, it is not the first time this happened for me, I've seen this with > other crashes as well. > (sorry for the many small comments) Thomas are you able to confirm if this is still an issue, thanks.
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!