Bugzilla – Bug 133
Error on [Shift+Ctrl+Alt] release.
Last modified: 2013-10-03 07:14:06 CEST
None critical error triggered on releasing key-combo [Shift-Ctrl-Alt] when a container(like a cupboard) is also open. OS: Windows Xp Java: 1.7.0.13 Client: autohaven.jnlp Error message: >Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException > at sun.awt.SunToolkit.getWindowDeactivationTime(Unknown Source) > at com.sun.java.swing.plaf.windows.WindowsRootPaneUI$AltProcessor.altReleased(Unknown Source) > at com.sun.java.swing.plaf.windows.WindowsRootPaneUI$AltProcessor.postProcessKeyEvent(Unknown Source) > at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(Unknown Source) > at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(Unknown Source) > at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(Unknown Source) > at java.awt.DefaultKeyboardFocusManager.dispatchEvent(Unknown Source) > at java.awt.Component.dispatchEventImpl(Unknown Source) > at java.awt.Component.dispatchEvent(Unknown Source) > at java.awt.EventQueue.dispatchEventImpl(Unknown Source) > at java.awt.EventQueue.access$200(Unknown Source) > at java.awt.EventQueue$3.run(Unknown Source) > at java.awt.EventQueue$3.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) > at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) > at java.awt.EventQueue$4.run(Unknown Source) > at java.awt.EventQueue$4.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) > at java.awt.EventQueue.dispatchEvent(Unknown Source) > at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) > at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) > at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) > at java.awt.EventDispatchThread.pumpEvents(Unknown Source) > at java.awt.EventDispatchThread.pumpEvents(Unknown Source) > at java.awt.EventDispatchThread.run(Unknown Source)
From the stacktrace, this looks like a bug in Java, rather than a bug in the actual client.