Bug 477574 - Upgrading to eclipse-cdt-5.0.1-1.fc10 breaks eclipse
Upgrading to eclipse-cdt-5.0.1-1.fc10 breaks eclipse
Product: Fedora
Classification: Fedora
Component: eclipse-cdt (Show other bugs)
All Linux
low Severity high
: ---
: ---
Assigned To: Jeff Johnston
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-21 23:21 EST by Dave Ludlow
Modified: 2009-12-18 02:22 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 02:22:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Eclipse log file (248.23 KB, text/plain)
2008-12-21 23:21 EST, Dave Ludlow
no flags Details

  None (edit)
Description Dave Ludlow 2008-12-21 23:21:39 EST
Created attachment 327606 [details]
Eclipse log file

Description of problem:
Eclipse had been working fine on a Fedora 10 system.  The eclipse-cdt-5.0.1-1.fc10 update was applied on a x86_64 system, at which point the CDT functionality broke.  New C/C++ projects cannot be created (no suitable options are available in the File/New menu) and the C/C++ settings of existing projects no longer show up.

Confirmed same result on an i386 system. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Have a system that was current as of Dec 19th, 2008
2. Apply updates available as of Dec 21, including eclipse-cdt-5.0.1-1.fc10
3. CDT functionality is now broken
Actual results:
CDT functionality is broken

Expected results:
CDT working fine as usual

Additional info:
See attached log file.
Comment 1 Dave Ludlow 2008-12-21 23:25:41 EST
Forgot to mention that downgrading back to eclipse-cdt-5.0.0-10.fc10 does not correct the problem.
Comment 2 Andrew Overholt 2008-12-22 11:10:48 EST
Try running on the command line with the -clean argument.
Comment 3 Dave Ludlow 2008-12-22 11:49:03 EST
That did the trick - thanks!

This is more of a workaround than a fix since it requires user intervention.  I'm leaving the bug open in case there is a desire to automate the fix somehow.  Otherwise, I'm satisfied and this bug can be closed as far as I'm concerned.
Comment 4 Andrew Overholt 2008-12-22 15:22:09 EST
This is an upstream issue:


It's also here:

Comment 5 Bug Zapper 2009-11-18 04:42:26 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 6 Bug Zapper 2009-12-18 02:22:07 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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