print a file and settings - strange behaviours

[Huipil]

I have ubuntu 12.04 with kde. I have installed code::blocks v12.11 rev 8629 build: 8 Dec 2012
I have 2 problems:

- when I print a file like this --> http://img189.imageshack.us/img189/9109/schermata8p.png
 the result is --> http://img23.imageshack.us/img23/6131/schermata7v.png

- I try to change editor settings (like Syntax highlighting or margins and carte) but it doesn't save them after restart,
 and most of all the program does not close when I click close button, I've used system monitor and I have seen that the program is still running after I made some settings change and tried to close it.

 So, summarizing it, I can close codeblocks correctly only if I don't make any setting change, otherwise it stays running and after force closing it doesn't apply changes.

How can I solve?

thanks a lot

[Huipil]

any help?

[Alpha]

Where did you get the package from that you used to install?
Does it close if you disable all plugins (and/or start Code::Blocks in safe mode)?

[Huipil]

from this ppa: https://launchpad.net/~pasgui/+archive/ppa/
but it's the same for codeblocks from repositories

however, how can i do that? I disabled all plugins manually and saved prospective, but now it's still opened and I can't close it. I force closed it.
I reopened it (without any opened .c file in it) , it didn't save anything from last session so all plugins are enabled, but now I just closed it and now it closed well

[Alpha]

Safe mode:
codeblocks --safe-mode

[Alpha]

Also, does anything change if you delete the configuration files (located in ~/.codeblocks)?

[Huipil]

I already deleted ./codeblocks and nothing changed, but in safe-mode it worked: i have opened a .c file and then changes prospective and it has closed well, but after reaopening codeblocks normally it didn't close

[Alpha]

If you launch Code::Blocks from terminal, once you close Code::Blocks (and it hangs in memory), what messages are left in the terminal window?

@Anyone: Ideas? ... I seem to be getting nowhere.

[Huipil]

I have just unistalled everything from synaptic, I reinstalled codeblocks and now I decided to install also the package codeblocks-contrib with updated plugins.
I have opened codeblocks from terminal and I just did nothing and it has closed well, after that i reopened codeblocks from terminal and I open a .c file with it and compiled it, after that I've closed codeblocks and now it still opened: these are the last few lines from terminal:

Code Select Expand

Found 1 files:
- /home/user/Dekstop/file.c
Updating class browser...
Class browser updated.

(codeblocks:20329): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed
Deinitializing plugins...

(codeblocks:20329): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkRadioMenuItem'

(codeblocks:20329): Gtk-CRITICAL **: IA__gtk_radio_menu_item_get_group: assertion `GTK_IS_RADIO_MENU_ITEM (radio_menu_item)' failed

(codeblocks:20329): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkRadioMenuItem'

(codeblocks:20329): Gtk-CRITICAL **: IA__gtk_radio_menu_item_get_group: assertion `GTK_IS_RADIO_MENU_ITEM (radio_menu_item)' failed

and it stays on the last line.

[Huipil]

I understood that the problem is concerned to editor maybe, because codeblocks doesn't close only when I open a .c file: Infact I made another try from terminal and I had this:

Code Select Expand


Editor Open
Caching GCC default include dir: /usr/include/c++/4.6
Caching GCC default include dir: /usr/include/c++/4.6/x86_64-linux-gnu
Caching GCC default include dir: /usr/include/c++/4.6/backward
Caching GCC default include dir: /usr/lib/gcc/x86_64-linux-gnu/4.6/include
Caching GCC default include dir: /usr/local/include
Caching GCC default include dir: /usr/lib/gcc/x86_64-linux-gnu/4.6/include-fixed
Caching GCC default include dir: /usr/include/x86_64-linux-gnu
Caching GCC default include dir: /usr/include
Passing list of files to batch-parser.
Header to parse with priority: '/usr/include/c++/4.6/cstddef'
Add 1 priority parsing file(s) for project '*NONE*'...
No active project available.
Traversing '/home/user/Scrivania' for: Untitled1.*
Found 1 files:
- /home/user/Scrivania/Untitled1.c
Create new parser for project '*NONE*'
Updating class browser...
Class browser updated.
Starting batch parsing for project '*NONE*'...
Pool task operated?!
Pool task operated?!
Pool task operated?!
Already current parser present?!
Project '*NONE*' parsing stage done!
Project '*NONE*' parsing stage done (9 total parsed files, 589 tokens in 0 minute(s), 0.059 seconds).
No active project available.
Traversing '/home/user/Scrivania' for: Untitled1.*
Found 1 files:
- /home/user/Scrivania/Untitled1.c
Updating class browser...
Class browser updated.

(codeblocks:2985): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed
Deinitializing plugins...

(codeblocks:2985): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkRadioMenuItem'

(codeblocks:2985): Gtk-CRITICAL **: IA__gtk_radio_menu_item_get_group: assertion `GTK_IS_RADIO_MENU_ITEM (radio_menu_item)' failed

(codeblocks:2985): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkRadioMenuItem'

(codeblocks:2985): Gtk-CRITICAL **: IA__gtk_radio_menu_item_get_group: assertion `GTK_IS_RADIO_MENU_ITEM (radio_menu_item)' failed

I hope it will help to solve my problem, thanks

edit: same thing in --safemode

[Jenna]

edit: same thing in --safemode

Did you use --safemode or --safe-mode (note the hyphen) ?

[Huipil]

sorry you are right, now I used the right command "codeblocks --safe-mode" and if I open a .c file this time it works and closes well. So what is the problem?

[Jenna]

sorry you are right, now I used the right command "codeblocks --safe-mode" and if I open a .c file this time it works and closes well. So what is the problem?

Try to start C::B normal and disable the codecompletion-plugin from "Plugins -> Manage plugins".
If it is not the cc-plugin, you can disable all plugins and enable the one by one until you find which one causes the issue.

In any cases you can attach the *.c file (if possible), that leads to the issue

[Huipil]

any *.c file causes the problem, even if I create a new .c file, btw I will try as you said thanks

[Jenna]

any *.c file causes the problem, even if I create a new .c file, btw I will try as you said thanks

Even if it is empty ?