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 19530

Summary:	"Cannot read relative bounds of frame properties, ignoring." for no apparent reason
Product:	platform	Reporter:	Jesse Glick <jglick>
Component:	Window System	Assignee:	mslama <mslama>
Status:	CLOSED DUPLICATE
Severity:	blocker	CC:	dsimonek
Priority:	P3
Version:	3.x
Hardware:	PC
OS:	Linux
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Stack trace at end of log file from r33, after first normal start (after sanity start) User system dir, after shutdown of first normal start - gzipped tar format

Description Jesse Glick 2002-01-17 13:38:56 UTC

I have seen this appear in log files (not console) recently in the trunk, as
well as in today's release33 sources. Seems to happen during first or second
startup of the IDE, not afterwards. For example, today I made a clean build of
r33 incl. sanity start. Then I ran the IDE using the testuserdir the sanity
start left. Chose MDI mode. The property sheet was way too short (maybe twenty
pixels high on my 1024x768 screen) but that may be a different bug. I opened a
Java source in the editing workspace; it opened in a strange position: not at
all maximized, somewhat small (500x400 maybe), floating somewhere in the middle
of the free area. I shut down, and saw that my log file had the attached. I did
not explicitly move around any windows, so whatever was invalid in the window
system XML, was generated by the window system itself.

Comment 1 Jesse Glick 2002-01-17 13:39:56 UTC

Created attachment 4242 [details]
Stack trace at end of log file from r33, after first normal start (after sanity start)

Comment 2 Jesse Glick 2002-01-17 13:42:25 UTC

Created attachment 4243 [details]
User system dir, after shutdown of first normal start - gzipped tar format

Comment 3 David Simonek 2002-01-17 14:06:36 UTC

Marek, can you take this? You did some fixes that touched bounds,
could it has some connection with this bug?

Comment 4 mslama 2002-01-17 14:25:05 UTC

I will check that. My last change was in main trunk not in release33.

Comment 5 David Simonek 2002-01-25 16:56:04 UTC

Isn't it fixed? (duplicate of Tor's bug?)

Comment 6 mslama 2002-01-25 17:00:05 UTC

Yes Dafe is right.

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

Comment 7 Quality Engineering 2003-07-01 16:01:43 UTC

Resolved for 3.4.x or earlier, no new info since then -> verified.

Comment 8 Quality Engineering 2003-07-01 16:18:00 UTC

Resolved for 3.4.x or earlier, no new info since then -> closing.