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 94844 - java.lang.IllegalStateException: No Toolbars/
Summary: java.lang.IllegalStateException: No Toolbars/
Status: RESOLVED DUPLICATE of bug 61130
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-07 14:10 UTC by zebu_alex
Modified: 2008-12-22 11:42 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log (191.35 KB, application/octet-stream)
2007-02-07 14:11 UTC, zebu_alex
Details

Note You need to log in before you can comment on or make changes to this bug.
Description zebu_alex 2007-02-07 14:10:27 UTC
Despite having worked fine previously, now when I try to launch NetBeans I get
an IllegalStateException and cannot open it.
Comment 1 zebu_alex 2007-02-07 14:11:18 UTC
Created attachment 38172 [details]
messages.log
Comment 2 Marian Mirilovic 2007-02-13 10:45:40 UTC
Reassign to openide/awt :
I am not sure, this is 5th issue that should be closed as duplicate of 61130,
but it's closed WORKSFORME ;(

Reporter, how did you finish your previous IDE session ? It looks like your user
directory is corrupted.
Comment 3 David Simonek 2007-02-16 11:51:24 UTC
Reporter, we need to know *how* you get NetBeans installation into this state.
Did you kill NetBeans session somehow? Did the computer crashed? Did you install
newer version of NetBeans over older version into the same directory without
deleting older version first?

Please answer, we can't fix without your info, thanks.
Comment 4 David Simonek 2007-02-16 11:52:49 UTC
Jardo don't you have a clue by a chance how system can be brought into such state?
Comment 5 Jaroslav Tulach 2007-02-19 12:52:39 UTC
I have made the logging more verbose:

core/src/org/netbeans/core/xml/FileEntityResolver.java,v  <--  
FileEntityResolver.java
new revision: 1.36; previous revision: 1.35

since 6.0m8 it will tell us the name of the file that cannot be parsed. 
Otherwise I do not know what is wrong, CCing Radek, but I would not have high 
hopes: We need to be able to reproduce the problem...
Comment 6 David Simonek 2007-03-21 19:13:25 UTC
No response for a long time, closing. Unfortunately we need reproduction in
order to fix this. Please reopen when you have reproduction info, thanks.
Comment 7 Marian Mirilovic 2007-04-03 09:06:08 UTC
reopen to track as duplicate of issue 61130
Comment 8 Marian Mirilovic 2007-04-03 09:07:01 UTC

*** This issue has been marked as a duplicate of 61130 ***