Codeblocks hangs when trying to change environment or scripts

[pabristow]

Codeblocks hangs when trying to change environment or scripts.

It is new install from damian moore PPA   SVN 10853 2016-05-13 00:05:41  gcc 5.3.1 Linux /unicode - 32 bit

Editor options can be changed OK and are saved (with prompt and judged by the file update time) to

/home/paul/.config/codeblocks/default.conf contains some plausible xml

/home/paul/.config/codeblocks/default.conf
application info:
    svn_revision:   10853
    build_date:   May 13 2016, 06:15:19
    gcc_version:   5.3.1
    Linux
    Unix Unicode
...

(and this is the only default.conf file on the system that I can find with locate)

The log when using --safe-mode is

paul@hetp1:~$ codeblocks --safe-mode
Starting Code::Blocks svn build  rev 10853 May 13 2016, 06:16:35 - wx3.0.2 (Linux, unicode) - 32 bit
Initialize EditColourSet .....
Initialize EditColourSet: done.
Loading menubar...
FilesExtensionHandler: loaded
OccurrencesHighlighting: loaded
Autosave: loaded
ScriptedWizard: loaded
ProjectsImporter: loaded
Compiler: loaded
ClassWizard: loaded
CodeCompletion: loaded
OpenFilesList: loaded
Debugger: loaded
Abbreviations: loaded
AStylePlugin: loaded
ToDoList: loaded
Loading toolbar...
Initializing plugins...
Deinitializing plugins...
10:08:18: Debug: 3 threads were not terminated by the application.
[1]+  Killed                  codeblocks --safe-mode

I can build projects etc as normal, but this is a bit of puzzle and a big snag.

Suggestions welcome.  Thanks

[dmoore]

Have you tried apt-get removing all of codeblocks and reinstalling?

Also did you try temporarily renaming the config file?

[pabristow]

I haven't tried apt-get remove because I had done that before installing.

But changing the name of the default.conf caused it not to find the gcc compiler.

But it allowed me to change environment options and to save.

But when I restarted codeblocks, it hung with the logo splash screen greyed out.

After I had found out how to kill a Ubuntu process, it is now working to build and run a project.

Fingers crossed...

Thanks.  Paul

[oBFusCATed]

Can you start cb under a debugger and show us a backtrace of the crashes?

[dmoore]

I gathered this started happening after an upgrade of either Code::Block or Ubuntu. What version were you using before?

[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]

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.

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).