Each time I start Code blocks, I need to chose my compiler an change to color of the mouse cursor because it simply does not save this information from a session to another. It also does not remember which recent projects were opened.
So how can I make sure that the config gets saved?
Where is that information saved, there could be a problem with the target file like for example access rights?
Can you show us the permissions of your config folders (~/.config/codeblocks)?
To do so fun the command:
find ~/.config/codeblocks -ls
This is very common problem and I want to know what people do to mess it up.
Please don't fix permissions before showing the listing.
Thanks.
OK, thanks, it worked. The file was owned by root. Which not only did not saved the config, but C::B crashed randomly while simply typing text. So far the config is saved, I assume it won't crash randomly now.
It will still crash, these are unrelated problems. I've already helped an ubuntu user how to solve these in the last few days.
So search the forum please.
And I asked for a file listing, but I'm not getting it.
I guess I'll have to answer this question many more times and not really fix the bug... Or improve the situation.
You are right, it is not related. I thought it crashed because it tried to save the config file in background. But it crashed again this afternoon.
I have not done much so far. Imported some code highlighting theme, and modified a theme. stated a new project and that's it. Everything else is fresh install.
What file listing do you require?
It is over, you've changed the permissions, so the listing is useless now.
The crashes are known and they are fixed in the latest night builds.
See this post where http://forums.next.codeblocks.org/index.php/topic,22143.msg150708.html#msg150708 for links to launchpad where to report that you have the same problem. I guess this is the only way to attract ubuntu dev's attention, so they could update the package in this distro.
Oh! it's an update that has just been made. Forget it, it will take years before debian get's updated. It seems I am stuck without codeblocks.
It's weird because normally debian only use old stable versions, I am surprised to have the most recent version.
The most stable version of codeblocks is the version of trunk. It has least known bugs.
I though you're using ubuntu. But it seems you're not. Can you state the OS and its version?
Can you show a backtrace of a crash? (https://wiki.debian.org/HowToGetABacktrace)
Also can you check if the symbol browser is enabled in the settings -> editor -> code completion?
If it is try to disable it and try to reproduce the crashes.
I am running on Debian 9, just installed this summer.
I disabled the symbol browser and did some minor editor. It did not crash so far. I'll have to do more intensive work tomorrow and check if the program will hold.
I don't mind losing a simple feature for stability.