Product Version = NetBeans IDE 6.9 Beta (Build 201004200117)
Operating System = Linux version 2.6.32-22-generic running on i386
Java; VM; Vendor = 1.6.0_18
Runtime = OpenJDK Client VM 14.0-b16
I was editing one of my PHP files as usual, but when I pressed ctrl-S, it would not save. I attempted to access "Save" through the "File" menu, but it was "grayed out". After switching to other files and trying a couple of different things to no avail, I attempted to close the editor. It gave me a notification that my file had not been saved and an option to save it. I clicked "Save" and the IDE shut down, but when I brought it back up, my changes had not been saved. Unfortunately, I have not been able to reproduce the error, but if it happens again I will add to this ticket.
To reported: Could you please attach messages.log of that NB session while save action was not working.
Reassigning to php.
Unlikely related to PHP support itself... Please, reopen this issue and attach the IDE log as we asked before so we can investigate it.
Thanks a lot.
Created attachment 99686 [details]
Log of the IDE shortly after the error occurred.
OK, sorry I didn't attach the IDE log before, but during my process of figuring
out what was going on, I had restarted the IDE (and I figured that the log
wouldn't have been present still, but I didn't actually check to make sure).
Anyway, the problem happened again. This time, I hit ctrl-Tab to change the
file I was editing and an Exception window popped up. I decided I didn't have
time to look at it at that moment, so I closed the Exception window by clicking
on "Cancel" (usually things continue to work as usual when this happens).
After clicking on "Cancel", I edited the file I was intending to work on and
hit ctrl-S, but nothing happened. I was still able to edit and save other
files, but not that particular file.
I have attached the IDE log this time.
This time, when I closed the file itself, and clicked "Save" when it asked me if I wanted to save it as it was closing, it seemed to save correctly.
(In reply to comment #4)
> I figured that the log wouldn't have been present still
Three logs are kept, have a look at <nbuserdir>/var/log/ directory.
Looking into the LOG file, exception occured in NB window system - please evaluate, thanks.
A duplicate of issue 180960?
Seems like that issue is more severe than we thought. If it prevents saving a file, we should consider fixing it in 6.9 rather than in 6.9.1 as we originally planned.
Created attachment 99702 [details]
reporter, please copy the patched module to your netbeans 6.9 RC folder (<netbeans dir>/platform/modules) and let us know if it fixes the problem.
if you can verify that you can no longer reproduce this issue with the patched jar within the next day or two we'll backport the fix to 6.9 release.
*** This bug has been marked as a duplicate of bug 180960 ***
I have copied the module and will be testing it over the next number of days. I'll notify if the problem happens again.
I have been using Netbeans 6.9 with the patched module, but today I ran into the problem once again.
Created attachment 99995 [details]
Created attachment 99996 [details]
UI Gestures Log.
I've attached the messages log and uigestures log.
the stack trace from the new log file is from unpatched version of the tab control module.
you either didn't copy the patched module or you copied to wrong location
I don't see how it could have been the unpatched module unless the unpatched module was the one attached.
I double-checked the bash script that I've been running to start Netbeans to make sure it was starting the version I thought it was from the directory I thought it was starting from. Then I re-downloaded the "patched module" and ran diff on it and the module which I have installed currently in that Netbeans installation. They are identical.
So, I see three possibilities here: Netbeans is using modules from a different directory than the one the binary file which executes Netbeans is in, the stack trace was from the patched module, or the "patched module" isn't actually patched at all (you gave me the wrong one).
you might need to clear the user dir first, i think that netbeans module system builds a cache of all jars there