Ubuntu hangs when debugging with codeblocks

[Yves]

I don't know if this bug is related to 0ad or if it's a Codeblocks- or Ubuntu bug.

Steps to reproduce:

1. Open pyrogenesis.workspace in Codeblocks
2. Build (debug or release)
3. Press F8 to start debugging. Switch to another program before the 0ad window opens
4. Switch back to 0ad and exit it

Now the system hangs somehow. The mouse pointer can still be moved but nothing can be clicked and the keyboard does not react (no numlock, no Alt+F1 etc...). Pressing Ctrl+Alt+Print Scrn+K to restart X and kill all programs in the current session works.

Running codeblocks with "codeblocks --debug-log &> cb.log" writes some debugging information too a file. There was always something like that when the crash happened (notice the fatal IO error):

[...]
Nothing to be done (all items are up-to-date).
-------------- Build: Debug in mocks_real (compiler: GNU GCC Compiler)---------------
Target is up to date.
codeblocks: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :4.
-------------- Build: Debug in network (compiler: GNU GCC Compiler)---------------
Target is up to date.
-------------- Build: Debug in simulation2 (compiler: GNU GCC Compiler)---------------
Target is up to date.
-------------- Build: Debug in scriptinterface (compiler: GNU GCC Compiler)---------------
[...]

Translated to english "Die Ressource ist zur Zeit nicht verfügbar" means "The resource is temporarily unavailable".

I'm using Ubuntu 12.04 and codeblocks svn version (rev 8164). Tests on different operating systems (and Linux distributions) and with different versions of Codeblocks appreciated!

[Yves]

I could not reproduce the problem on a VirtualBox VM with Ubuntu 12.04. I've tried the versions 10.05 and SVN 8164 of Codeblocks. I'll try with a different graphics card driver tomorrow.

[Yves]

I can't reproduce it anymore after uninstalling fglrx. Now I'm going to try if it works with the updated version of fglrx. Ubuntu offers two versions by default : a version that stays the same until the next release and one that is updated regularly. The bug occurred in the version not being updated.

I keep this ticket open at the moment even though it doesn't seem to be a problem of 0ad. It could potentially affect multiple users/developers and it must be fixed at least for me ;).

[Yves]

I can't install the updated fglrx driver and don't want to dig deeper to find a solution for that. I'm closing this ticket because:

1. It seems to be bug in the graphics driver and not in 0ad
2. There's a workaround (use another driver).
3. The problem just affects developers who use codeblocks for 0ad development
4. I don't know anyone else who's affected. Maybe I'm the only one.

Resolved as "invalid" because it's not a bug of 0ad.