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.
Product Version = NetBeans IDE Dev (Build 200211080100) IDE Versioning = IDE/1 spec=3.18 impl=200211080100 Operating System = Linux version 2.4.18 running on i386 Java; VM; Vendor = 1.4.1_01; Java HotSpot(TM) Client VM 1.4.1_01-b01; Sun Microsystems Inc. Java Home = /usr/java/j2sdk1.4/sun/jdk1.4.1_01/jre System Locale; Encod. = cs_CZ; ISO-8859-2 Home Dir; Current Dir = /home.local/danielm; /DISKS/storage3/forte/NBdev-last/netbeans/bin IDE Install; User Dir = /home.local/danielm/NBdev-last; /home.local/danielm/.netbeans/dev ------------------------------------------------------------------------------- This occures very rearly. But the fact it happens sometimes is enough to enter it as a bug. For JavaCVSValidationTest suite it is critical 'cause it causes that test fails. But it happens rearly as I said -> P5 (is it OK?) Please see mentioned URL (or I hope I'll succed and attach it:) How it happens: ================ On a file versioncontroled via JavaCVS FS perform Status Command. Let it opened and perform Log command. It is docked into the same Window and you have to TABs in it: Status - file.java Log -file.java but the title is staing the same as it was construct for the first Status commmand: CVS Output [Status -file.java] but it has contains "Log" string instead of "Status" in it while you have active LOG TAB.
Created attachment 7892 [details] CVS Outout command
Hi Martin, I'm increasing the priority to P4 'cause it happens more often then it could be accepted... But I found that it happens only on Soalris 5.8 (CDE) or I didn't observe it so often on others machines :-/
IMHO this must be some problem in window system. TopComponents set their title correctly, maybe it's not always repainted? Moving to core for evaluation.
If you need some hints how to run this tests, please have a look into very similar issue #26842, where I accidentaly described (even thought it was obsolate) how to get test environment, etc... thanks -Daniel P.S. i don't mind to set this as P5, but for P4 is the fact that it ahppens regulary each day on one of testing machines....
Illegal URL, provide new one, than reopen, thanks.
URL has changed because it was too many builds back and we don't have enough space to archive whole results:-( Next time I'll attache the file instead of making links on it... FYI: from recent results it seems that problem disappeared :-)
Previously VERIFIED issue that was mistakenly put into the NEW state... closing again...
... verified.