This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
As requested by the ide, the ide.log is attached (in a second try - the real home path has been substituted by the string "$HOME"). The JDK used is the only one of the 1.3-JDK which let NetBeans pop up with the initial picture and the right font. Aside the exceptions as shown below the main ide frame starts each time with an y-offset. That is not the case with other 1.3-JDKs (e.g., that shipped with JBuilder5, but there no initial picture pops up and the fonts used ignore some chars (<,> for example)).
Created attachment 2486 [details] The ide log file as created by NetBeans and requested as an attachement for a bug report
I checked the behaviour in the last 3.3dev build #20010911 and have to say that it works form me (the shortcut changed to ctrl+shift+f11 - build project). BUt to be sure assigning to Dafe to check the exception from window system.
updating subcomponent field
Cannot reproduce on Solaris and Win2000 (build #200109200100). Could you give us some more information about your window system, please? Which window manager do you use?
Answer from Walter: Thank you for your response! I'm using the KDE2 window manager on a SuSE 7.2 distribution. Attached to this mail is a tarchiv screenshots.tar.gz including four screenshots made while reproducing the mailed error. Sorry for the huge attachement, but may be you can see a little bit more from these images: 1. netbeans1_start.png is showing the ide after starting up (note the y-offset). 2. netbeans2_ctrl_shift_f10.png. IDE window moved to top of screen, all is fine. 3. netbeans3_close_output_window.png: Closing the output window. A panel is left where the output window has been before. 4. netbeans4_ctrl_shift_f10_again.png: Pressing CTRL-SHIFT-F10 a second time reproduces the error. The JAVA_HOME env var pointed to the JDK/JRE 1.3 shipped with the foundation version of JBuilder4. Yours, Walter
Created attachment 2669 [details] screenshots
*** Issue 15345 has been marked as a duplicate of this issue. ***
Ok ;-) I get the root of this issue. First, you are using IBM jdk. On others jdks this doesn't occur. And the good news is that this is fixed in the 3.3beta2. There was some side efect in our code that was corrected. Closing this as a duplicate. If you will be testing/playing with the 3.3 beta check the y-offset behaviour and file issues if needed. Thanks. *** This issue has been marked as a duplicate of 10024 ***
Resolved for 3.4.x or earlier, no new info since then -> verified.
Resolved for 3.4.x or earlier, no new info since then -> closing.