Codeblocks triggers X Windows System error

[ASJ]

All of a sudden my Codeblocks doesn't start up anymore, giving the following message right after the splash screen flashes for a moment:

Code Select Expand


  The program 'codeblocks' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 1304 error_code 11 request_code 145 minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


After re-installing x.org this problem still remains. Also building a new version from svn does not change anything. I am using openSuse 10.3 (also tried the TuXKeeper rpm, it gives the same problems).
Does anyone have the same problem or have a clue to solve this problem?

TIA

[Jenna]

This is not (only) a C::B problem:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461410
You can downgrade "xserver-xorg-core" manually to make it work again.

[Jenna]

Ubuntu 7.10, Codeblocks svn4639
Reinstalling to Codeblocks svn4830 (from 'lgp203.free.fr' repository) don't help...

Again: it's not C::B related.
It's a bug in xserver-xorg caused by a security update.
For Ubuntu look here: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/183969 .

[Jenna]

I just got a mail from debian package-maintainer.

As workaround you can try to put the following into "xorg.conf" and restart XServer:

Code Select Expand


        Section "Extensions"
                Option "MIT-SHM" "no"
        EndSection


[HCHRIST]

xorg.conf addition works for me. Thanks lad.

[ASJ]

The xorg.conf addition works fine for me as well!
Thanks a lot! you saved my day!

[HCHRIST]

I noticed on my kubuntu machine that there was an update of the x-server-core, among others. So I removed the patch above from my xorg.conf file, to see if the problem was gone. And yep: everything works again with the old xorg.conf file.

So, probably a temporary problem.

[PauloH]

There is an upgrade right now. The problem was solved. My "gnome" made the update when I started my machine. No need to use the old xorg.conf again.

Bye.

[Hossein]

As workaround you can try to put the following into "xorg.conf" and restart XServer:

Code Select Expand


       Section "Extensions"
               Option "MIT-SHM" "no"
       EndSection


I seem to have difficulty finding my xorg.conf. In my VMWare Kubunutu, I searched for the file and found a directory containing vm*.* files. I added the above piece of code in a new file in the directory and restarted the machine. I still get the same error! Any idea? (I'm using CB 10.05 under KUbuntu 12.04 64B.)