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.
1. install netbeans 6.7 or a daily build 2. at the command prompt: rm -r .netbeans/ .asadmintruststore .personalDomain/ 3! start netbeans. often (usually on my laptop), the output window is created as an editor window and there's no way to put it in its proper place. the times that the output window is created in the right place, it appears to start off as an editor window (and a peer to the Start Page) before it is 'transformed' into a standard window at the bottom of the IDE. so maybe it's a race condition...
Created attachment 84270 [details] the Output window is created as an editor window
Product Version: NetBeans IDE Dev (Build 200907010200) Java: 1.6.0_14; Java HotSpot(TM) 64-Bit Server VM 14.0-b16 System: Linux version 2.6.30-10-generic running on amd64; UTF-8; en_US (nb) Userdir: /home/alvin/.netbeans/dev this is an Ubuntu Karmic system, but IIRC it happens on Jaunty as well.
to be more explicit, the problem is that the Output window often never gets transformed into the proper window type, and thus remains as an editor-type window.
if, during install, you uncheck the 'features on demand' 'feature' you usually get the problem on first startup.
seems like a problem in 'ergonomics', some module opens output window before core.io.ui module where output 'mode' is defined loads/activates
see my previous comment...
See athomson's previous to previous comment. The FoD is not even installed and the problem can still appear.
athompson, please attach your ide log next time you encounter this issue, thanks
Created attachment 90101 [details] netbeans 6.8 beta first start
it seems that glassfish domain is being created before the window system is loaded and activated
i've checked ModuleInstall class for j2ee.sun.appsrv81 module and the registration is invoked correctly in WindowManager.invokeWhenUIReady() but there are some other public static methods that might be invoked from elsewhere, reassigning to glassfish team for evaluation
*** This issue has been marked as a duplicate of 175128 ***