Created attachment 697338 [details] screenshot Description of problem: In Eclipse user interface, there are many menu entries that have no icon, then Eclipse replace them with a red square. Version-Release number of selected component (if applicable): ***From Eclipse->About*** Version: 4.2.1 Build id: @build@ ***From yum*** Nome : eclipse-platform Arch : x86_64 Epoch : 1 Versione : 4.2.2 Rilascio : 0.1.git20121217.fc18 Dimensione : 48 M Repo : installed Additional info: Isn't wrong the version in Eclipse->About? 4.2.1 VS 4.2.2 in yum...
Hey, regarding versions - it's a snapshot made from a 4.2.2 development branch, although not all versions were updated yet. It will be done before final Eclipse 4.2.2 is out. Regarding the red icons - there is one bug associated with it - when you change the number of plugins, Eclipse changes the caching, but the part that loads icons from the cache is unaware of that. Could you describe the steps that led to the problem?
I installed from yum eclipse-platform and eclipse-cdt, together with their package dependencies
I'm experiencing this as well. I tried 'eclipse -clean', which did not resolve this issue. In addition, if you start with a new workspace, most of the Perspectives are missing (java, CDT, Fedora Packaging, etc). Perspectives available after updating to eclipse-platform 4.2.2-4.fc18 CVS Repository Exploring Debug Resource Team Synchronizing Downgrading got me back to a working state: yum downgrade eclipse-platform eclipse-pde eclipse-jdt eclipse-swt eclipse-equinox-osgi
I think this may have to do with presto/deltaRPM . I updated eclipse to 4.2.2-5 from updates-testing repository and did not observe the problem above. I updated eclipse from 4.2.1-21 to 4.2.2-5 (now in updates) and I observed the same problem as above. I reinstalled eclipse 4.2.2-5 and did not observed the problem above. The problem only occurs (for me at least) when updating using a drpm .
Hey Canyon, Thanks for all the info. There is a way to debug it - you need to find two bundles.info files. One is in the Eclipse installation (somewhere in /usr/lib64/eclipse/configuration) referred as master one, and one is deep in your ~/.eclipse folder. If you go to help->about->details->configuration, properties osgi.sharedConfiguration.area and osgi.configuration.area will tell you exactly where you should look for those files. If you're feeling adventurous and would like to help with the investigation - find an entry that is present in the master bundles.info, but is not present in the user bundles.info, when red squares appear. You may as well attach those files to this bug entry, and I will look into this.
I wish I could help. I tried to go back to the failed state but it seems fine now. I'm guessing the reinstall cleaned out whatever the problem was.
Ok, then I'm closing this bug.
Created attachment 716277 [details] /home/user/.eclipse/org.eclipse.platform_4.2.0_793567567/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info
Created attachment 716278 [details] /usr/lib64/eclipse/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info
I attached the files you required
Hey Germano, Thanks for those files. It looks like you've removed the lock that prevents Eclipse from running in an administrative mode (as root). This locked your "master" configuration at a certain point of time, and no further updates will work. You can only reinstall your core Eclipse packages now. Ensure that after you uninstall Eclipse, the entire Eclipse directory (/usr/lib64/eclipse) is empty or not existing. Eclipse should be never run in an administrative mode. Avoid it in the future. If you have to install non-standard things into master installation (you've advanced setup where you have many users using the same installation) please prepare binary rpms.
(In reply to comment #11) > It looks like you've removed the lock that prevents Eclipse from running in > an administrative mode (as root). This locked your "master" configuration at > a certain point of time, and no further updates will work. > > You can only reinstall your core Eclipse packages now. Ensure that after you > uninstall Eclipse, the entire Eclipse directory (/usr/lib64/eclipse) is > empty or not existing. > > Eclipse should be never run in an administrative mode. Avoid it in the > future. > > If you have to install non-standard things into master installation (you've > advanced setup where you have many users using the same installation) please > prepare binary rpms. I have never heard before about that lock. I usually use plugins from: - Fedora repositories RPMs; - upstream Eclipse's repositories in Help->Install new software-> Juno - http://download.eclipse.org/releases/juno I needed the second option too because the Fedora's RPM of Web Development Tools is not complete as the upstream (Akurtatov told me). I don't remember any strange thing I could have done to have the administrative mode triggered on. Do you have any ideas about?
Germano, there is another possibility - you could have installed upstream Juno Platform on the top of the Fedora packaged one. This could have the same effect :-(.
Anyway, running Fedora Eclipse as an administrator is a bad idea. I have introduced a lock to prevent that, but apparently it can be bypassed. Will think about that.
(In reply to comment #13) > Germano, > > there is another possibility - you could have installed upstream Juno > Platform on the top of the Fedora packaged one. This could have the same > effect :-(. Platform is a very general concept. Can you be more specific? Do you mean plugins?
Eclipse consists of plugins and features. Plugins contains actual code, and features group plugins into sets providing certain functionality. You can go to /usr/lib64/eclipse/features and open any feature.xml to see how this looks like on a technical level. Eclipse update mechanism allows you to update any plugin at any time. So, if you update any of those features listed in /usr/lib64/eclipse/features, you get Eclipse from eclipse.org, which is not able to handle other Eclipse packages properly. It also breaks updates.
(In reply to comment #11) > You can only reinstall your core Eclipse packages now. Ensure that after you > uninstall Eclipse, the entire Eclipse directory (/usr/lib64/eclipse) is > empty or not existing. I: 1) removed all Eclipse packages except for eclipse-equinox-osgi.x86_64 eclipse-swt because they were taking away other softwares like freemind; 2) erased /usr/lib64/eclipse/ ; 3) reinstalled Eclipse from Fedora repos; 4) reinstalled eclipse-equinox-osgi.x86_64 eclipse-swt because I erased their files when I deleted /usr/lib64/eclipse/ I am going to attach four bundles.info files: - first two are immediately after Eclipse reinstallation from yum - last two are after I installed WebDevelopmentTools from upstream Eclipse's repositories in Help->Install new software-> Juno - http://download.eclipse.org/releases/juno I need that because Web Development Tools in Fedora repos are incomplete/non existent. (In reply to comment #16) > Eclipse update mechanism allows you to update any plugin at any time. So, if > you update any of those features listed in /usr/lib64/eclipse/features, you > get Eclipse from eclipse.org, which is not able to handle other Eclipse > packages properly. > > It also breaks updates. So, in a few words: installing plugins from upstream Eclipse's repositories in Help->Install new software-> Juno - http://download.eclipse.org/releases/juno does it break Fedora Eclipse?
Created attachment 718129 [details] (Before WDT plugin installation) /usr/lib64/eclipse/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info
Created attachment 718130 [details] (Before WDT plugin installation) /home/user/.eclipse/org.eclipse.platform_4.2.0_793567567/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info
Created attachment 718131 [details] (After WDT plugin installation) /usr/lib64/eclipse/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info
Created attachment 718132 [details] (After WDT plugin installation) /home/user/.eclipse/org.eclipse.platform_4.2.0_793567567/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info
An update (sorry for the little offtopic): I found out that Fedora packages for web development tools have been improved a lot last year. Then I completely erased again Eclipse and installed only Fedora RPM packages for Eclipse plugins. Then you can not care about last 4 attachment I committed. I am sorry for the mess.
This is all about bridging P2 and RPM. The work will happen upstream. http://wiki.eclipse.org/Equinox/p2/Plan/3rd_party_installers