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 152315 - NullPointerException at org.netbeans.swing.dirchooser.DirectoryChooserUI$IconIndenter.getIconWidth
Summary: NullPointerException at org.netbeans.swing.dirchooser.DirectoryChooserUI$Icon...
Status: RESOLVED DUPLICATE of bug 177280
Alias: None
Product: platform
Classification: Unclassified
Component: Directory Chooser (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Simonek
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-04 16:25 UTC by xtecuan
Modified: 2009-11-20 11:35 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 135971


Attachments
stacktrace (9.18 KB, text/plain)
2008-11-04 16:25 UTC, xtecuan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description xtecuan 2008-11-04 16:25:28 UTC
Build: NetBeans IDE 6.1 (Build 200804211638)
VM: Java HotSpot(TM) Client VM, 10.0-b22, Java(TM) SE Runtime Environment, 1.6.0_06-b02
OS: Linux, 2.6.25-2-686, i386

Stacktrace: 
java.lang.NullPointerException
        at org.netbeans.swing.dirchooser.DirectoryChooserUI$IconIndenter.getIconWidth(DirectoryChooserUI.java:1613)
        at javax.swing.SwingUtilities.layoutCompoundLabelImpl(SwingUtilities.java:946)
        at javax.swing.SwingUtilities.layoutCompoundLabel(SwingUtilities.java:873)
        at javax.swing.plaf.basic.BasicLabelUI.layoutCL(BasicLabelUI.java:72)
        at javax.swing.plaf.basic.BasicLabelUI.getPreferredSize(BasicLabelUI.java:235)
        at javax.swing.JComponent.getPreferredSize(JComponent.java:1632)
Comment 1 xtecuan 2008-11-04 16:25:46 UTC
Created attachment 73204 [details]
stacktrace
Comment 2 David Simonek 2008-12-05 13:04:26 UTC
Already fixed in 6.5, please upgrade, thanks.
Comment 3 Alexander Simon 2009-11-20 09:49:58 UTC
wrong fix
Comment 4 David Simonek 2009-11-20 11:35:33 UTC
I agree now that it was wrong fix, but what is the reason to have two reports opened for one problem? Closing as duplicate, solution will continue in 177280.

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