[sisyphus] CodeBlocks
Rinat Bikov
bikoz.r на gmail.com
Вт Сен 8 01:20:04 UTC 2009
Здравствуйте, уважаемые!
Сегодня попробовал установить CodeBlocks на свежий компьютер (сизиф,
но давненько не обновлялся).
Получил такой ответ от apt'a:
The following extra packages will be installed:
gdb wxGTK
The following packages will be upgraded
wxGTK
The following NEW packages will be installed:
codeblocks gdb
Отлично, CodeBlocks запустился, однако при попытке
перенести консоль сценариев в другое место, IDE падает со следующей руганью:
(codeblocks:23676): Gdk-CRITICAL **:
gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed
(codeblocks:23676): Gdk-CRITICAL **:
gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
(codeblocks:23676): Gdk-CRITICAL **:
gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed
(codeblocks:23676): Gdk-CRITICAL **:
gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
(codeblocks:23676): Gdk-CRITICAL **:
gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
The program 'codeblocks' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 62822 error_code 3 request_code 15 minor_code 0)
(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.)
Это нормальное поведение, или такое только у меня?
--
С уважением, Ринат Биков.
Подробная информация о списке рассылки Sisyphus