Description of problem: When opening a systemtap .stp file from the File menu, the created editor contains no text (and ignores keyboard input), regardless of whether the file is empty or not. Version-Release number of selected component (if applicable): eclipse-systemtapgui-1.1-2.fc15.noarch How reproducible: Always Steps to Reproduce: 1. Go into the SystemTap IDE perspective 2. File menu->Open file 3. Open an existing .stp file Actual results: File appears to be empty. No text can be entered. Expected results: Contents of file should be displayed, and should be editable. Additional info: No error appears in the Error Log view. Creating new scripts works OK.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Bug still present in Fedora 17.
I can definitely confirm this is occuring on f17. Unfortunately I haven't had that much time to work on this particular plugin, but I know that there's a lot of work being done to improve this Eclipse plugin upstream. Sami, I know the latest release is in a much more usable state, and the .stp file seems to open correctly in 1.2.0. Would it be possible to update in f17 ? If not, can the fix be backported ?
Yes this has been fixed. I see no reason not to upgrade to 1.2... I'll push an update.
eclipse-systemtapgui-1.2-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/eclipse-systemtapgui-1.2-4.fc17
Package eclipse-systemtapgui-1.2-4.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing eclipse-systemtapgui-1.2-4.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-0724/eclipse-systemtapgui-1.2-4.fc17 then log in and leave karma (feedback).
eclipse-systemtapgui-1.2-4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.