Community
Participate
Working Groups
Build Identifier: 20110615-0604 OS: Linux Mint 64 After saving the code with Ctrl+S, key is stuck and I cannot move around or do anything. When I use Alt+Tab to switch to other program and come back then it works. Also, Eclipse autosaves briefly after I make change and shows the same key-stuck behavior. Any solutions? This is annoying. (Currently coding in Fortran90 format). Reproducible: Always Steps to Reproduce: 1.Write a code 2.Make a change 3.Save with Ctrl+S 4.Try to move around by arrow keys or insert a space. 5.If it works fine, try steps 2-4 again.
In which editor does this happen? Maybe the focus is gone from the editor?
This happens in the main editor of Eclipse Indigo (Photran). That is, the editor for source code. I cannot understand the meaning of 'focus is gone from the editor'. What does 'focus' mean? Thank you.
>That is, the editor for source code. What kind of source? Fortran? Does the problem also appear in the normal Eclipse text editor, e.g. when you edit a foo.txt file? >What does 'focus' mean? It means which widget is active and takes the input.
Yes, it happens the same when I write and edit a 'Foo.txt'. I was coding in Fortran90. (*.f90) After pressing Ctrl+S or just clicking on the diskette icon to save changes, the cursor still blinks in the main editor window, but as I mentioned, the key is stuck and Eclipse does not accept any input from keyboard unless I circulate around other programs with Alt+Tab or right-click and press 'Esc'.
If you use a base eclipse (i.e. without the fortran installed) can you reproduce this behavior ? We're just trying to determine where we should triage this defect...
With base install (that is, without Photran), this behavior shows up very rarely. When writing a C/C++ code and then Ctrl+S or pressing the diskette icon to save, mostly this problem does not show up. But as I said, just once in a while (1 out of 10) it shows up. But when Photran (FORTRAN) is installed, it always behaves like this.
Hi, Just to clarify... if Photran is *not* installed, this behavior *does* happen in a regular text editor, at least sometimes? And, if CDT is installed but not Photran, it happened in the C/C++ editor? But it happens more frequently with the Fortran editor?
Also, what Linux distribution are you using? Are you using a standard US keyboard?
(In reply to comment #7) > Hi, > > Just to clarify... if Photran is *not* installed, this behavior *does* happen > in a regular text editor, at least sometimes? And, if CDT is installed but not > Photran, it happened in the C/C++ editor? But it happens more frequently with > the Fortran editor? In regular text editor like GEdit or VIm, this does not happen at all. But in Photran it always happens. When Photran is no installed but only CDT is installed, it happens sometimes in the C/C++ editor. That is right, it happens more frequently in Fortran editor.
(In reply to comment #8) > Also, what Linux distribution are you using? Are you using a standard US > keyboard? The Linux Distribution I am using is "Linux Mint 11 Katya" with GNOME. Keyboard: Standard US.
OK, thanks. If this is happening in other Eclipse editors, when Photran is not installed, then it's probably not something we can fix in Photran. It sounds like an SWT/JFace issue, but I'm not sure. We've never seen this behavior with any other Linux distributions... I wonder if there's something unique about Linux Mint...
(In reply to comment #11) > OK, thanks. If this is happening in other Eclipse editors, when Photran is not > installed, then it's probably not something we can fix in Photran. It sounds > like an SWT/JFace issue, but I'm not sure. We've never seen this behavior with > any other Linux distributions... I wonder if there's something unique about > Linux Mint... Thank you for your interest in this matter. I think it is some uniqueness in Linux Mint as you said, or just from the combination of Mint and my machine. Even though I have not tested this in all Linux distros, this problem did not occur at least in Fedora.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
