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.

Bug 210952 - NullPointerException at org.netbeans.core.windows.WindowSystemImpl.load
Summary: NullPointerException at org.netbeans.core.windows.WindowSystemImpl.load
Status: RESOLVED DUPLICATE of bug 210279
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-10 13:44 UTC by gilbertoca
Modified: 2012-04-10 14:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 186795

Attachments
stacktrace (1.25 KB, text/plain)
2012-04-10 13:45 UTC, gilbertoca 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description gilbertoca 2012-04-10 13:44:59 UTC 
Build: NetBeans IDE Dev (Build 201203260401)
VM: Java HotSpot(TM) Client VM, 22.1-b02, Java(TM) SE Runtime Environment, 1.7.0_03-b04
OS: Linux

User Comments:
GUEST: ??????????, ? ?????? ????? ??????????

gilbertoca: Today, the update icon appers. After install all the plugins updates and click on Restart IDE I get this nullpointexceptions




Stacktrace: 
java.lang.NullPointerException
   at org.netbeans.core.windows.WindowSystemImpl.load(WindowSystemImpl.java:79)
   at org.netbeans.core.GuiRunLevel$InitWinSys.run(GuiRunLevel.java:234)
   at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
   at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:705)
   at java.awt.EventQueue.access$000(EventQueue.java:101)
   at java.awt.EventQueue$3.run(EventQueue.java:666)
Comment 1 gilbertoca 2012-04-10 13:45:04 UTC 
Created attachment 118063 [details]
stacktrace
Comment 2 Stanislav Aubrecht 2012-04-10 14:00:50 UTC 
Looks like a duplicate of #210279 - WindowManagerImpl is not present in the global Lookup...

*** This bug has been marked as a duplicate of bug 210279 ***