User forums > Help

Codeblocks hangs when trying to change environment or scripts

<< < (2/2)

pabristow:
I had a Codeblocks install from about 5 years ago and a Ubuntu 12 that hadn't been used since then.
I upgraded Ubuntu to 12 and then 16.04 LTS.
I tried hard to remove all files relating to Codeblocks, including all my old and brief hello world projects, and then installed from Damien's PPA.
But maybe there was something old that was picked up to alter the config file?

I do have the current and 'bad' config files still.  Are they of any interest?

Since it is working OK now, I'm not convinced that running the debugger will now help?

Thanks for yoru continuing help.

dmoore:

--- Quote from: pabristow on May 18, 2016, 11:31:01 am ---I had a Codeblocks install from about 5 years ago and a Ubuntu 12 that hadn't been used since then.
I upgraded Ubuntu to 12 and then 16.04 LTS.
I tried hard to remove all files relating to Codeblocks, including all my old and brief hello world projects, and then installed from Damien's PPA.
But maybe there was something old that was picked up to alter the config file?

I do have the current and 'bad' config files still.  Are they of any interest?

Since it is working OK now, I'm not convinced that running the debugger will now help?

Thanks for yoru continuing help.

--- End quote ---

I think that explains the problem. Lots of unintentional incompatibility between new and old settings has crept in over time. I recall a particular issue with compiler settings needing to be converted to a new format and for some reason causing the system to hang on startup. Possibly that's because of the CodeCompletion plugin accessing compiler framework data while it is being changed. (I think I used to suggest a remedy to people of starting in safemode then enabling plugins one by one.)

EDIT: The bad configs might be useful if someone is willing to test them and make sure the system is bullet proof to whatever is in them.

pabristow:
All sounds plausible, and hard to prevent.

So for anyone else troubled by this sort of trouble, is the simplest 'fix' to delete the file default.config ?

oBFusCATed:
pabristow: I'm interested in these config files. I'll probably need your original ~/.codeblocks folder (or whatever it is).

Navigation

[0] Message Index

[*] Previous page