Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 249133 - codeblocks start fails
codeblocks start fails
Status: CLOSED DUPLICATE of bug 241450
Product: Fedora
Classification: Fedora
Component: codeblocks (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Dan Horák
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-07-21 05:30 EDT by Ronny Fischer
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-21 05:47:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ronny Fischer 2007-07-21 05:30:42 EDT
Description of problem:
codeblocks fails to start properly

Version-Release number of selected component (if applicable):
codeblocks 1.0 svn version 3816, Fedora 7

How reproducible:

Steps to Reproduce:
1. install codeblocks on F7
2. start codeblocks
Actual results:
codeblocks start results in high cpu load and does not start properly

Expected results:
normal start up  of codeblocks

Additional info:
I've upgraded from FC6 to F7 and after that, codeblocks isn't working anymore. 
When I try to start, it shows me the availabyle compilers and when it comes to 
the "Tip of the day" CPU load raises up to 100% and CB hangs at this level.

Starting CB from the commandline shows the following error:

$ codeblocks 

(codeblocks:4207): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info-
>icon_pixmap == NULL' failed

All updates available are installed. Hardware is an IBM Thinkpad R52, Kernel is 
2.6.22, but this error also occurs on former kernel versions in F7.

CB worked fine before the update of Fedora.
Comment 1 Dan Horák 2007-07-21 05:47:45 EDT
Please apply the comment #9 from the linked bug for an immediate solution or
wait few days for an stable update of wxGTK.

*** This bug has been marked as a duplicate of 241450 ***

Note You need to log in before you can comment on or make changes to this bug.