Description of problem: Activating SystemTap perspective causes errors, adds an additional process, and prevents Eclipse from being shut down in the normal way. A kill (terminate) command is required in order to shut down Eclipse. Version-Release number of selected component (if applicable): Note: f12 is running on F13 OS, so this issue may be the same for both versions! ===========================vvvv eclipse-systemtapgui-1.0-8.fc12.noarch systemtap-runtime-1.3-1.fc13.i686 systemtap-1.3-1.fc13.i686 How reproducible: Every time Steps to Reproduce: 1. Install/Run Eclipse. 2. Update then install SVN and SystemTap. Subversive and Subsclipse are both installed. When SVN configuration is completed, and when popup appears, select all JavaHL versions. 3. Configure SVN and check that SVN has full color/revision/menu support. 4. Open SystemTap perspective, and note high CPU activity via gkrellm and there are two processes running: 1: /bin/sh /usr/bin/eclipse (Eclipse) 2: /usr/lib/eclipse/eclipse (Started by SystemTap) Also note that many errors are appearing in error console. 5. Try to exit Eclipse - error message pops up explaining there is an internal error and fails to exit Eclipse. 6. Since Eclipse refuses to exit normally: 1. Close the SystemTap perspective 2. kill Eclipse process ID obtained from step 4.2 above. 7. Restart Eclipse 8. Make sure your SystemTap perspective is not opened nor running. Your mileage may vary, but note that some/all of your configurations may be lost - note the SVN perspective - all configuration data for a previously set up repository may be gone. Ok, let's add it back in. Uh oh, adding back a repository brings up another error: =============================== Subclipse talks to Subversion via a Java API that requires access to native libraries. Those libraries were either not found or an incompatible version was loaded. The errors are displayed below. Information on getting a proper version installed and visible to Eclipse is available here: http://subclipse.tigris.org/wiki/javaHL =============================== Errors: Failed to load JavaHL Library. These are the errors that were encountered: no libsvnjavahl-1 in java.library.path Native Library /usr/lib/libsvnjavahl-1.so.0.0.0 already loaded in another classloader no svnjavahl in java.library.path java.library.path = /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386/client:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386:/usr/lib/alliance/lib:/usr/lib/xulrunner-1.9.2:/usr/lib/xulrunner-1.9.2:/usr/java/packages/lib/i386:/lib:/usr/lib =============================== Pressing OK closes this error, but you are able to connect to your SVN repository with noted exception: minimal SVN support: no colors, no revision information, no menu support. Actual results: My Dual-core CPU are both hitting hard because there are two eclipse processes, and errors are appearing in the error console. You cannot terminate Eclipse the normal way due to internal errors, therefore a forced terminate (kill) is required. Removing SystemTap from the perspective menu seems to prevent this issue from re-occurring. SVN and some configurations that was setup prior to forced termination may be lost, such as SVN. CVS configuration remained intact. Prior to forced termination, SVN configuration had full color support, revision data, menus for the branches, tags, trunks but after forced termination, a different error appeared when adding back the repository configuration data, there was a lost of color, revision data, menus support, simply, it is not possible to get level of support back. Expected results: 1) Expected single process eclipse 2) Expected initial SVN configuration to remain intact, with full color, revision data, menu support. Additional info:
Hi Dan, The latest version of systemtapgui should work fine. - eclipse-systemtapgui-1.1-1.fc13 . Please let me know if it doesnt.
Results of SystemTap testing: 1) SystemTap does not hang when closing eclipse : good! 2) SystemTap does not have two eclipse processes: good! 3) SystemTap causes both CPUs to run @ 100% : bad? 4) Closing SystemTap perspective does not stop stap: runs both CPUs @ 100% : bad? 5) With SystemTap perspective closed, restarting eclipse does not start stap : good! 6) If SystemTap perspective is not closed, is active, restarting eclipse starts stap, both CPUs runs @ 100% : bad?
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.