Processing 1.0.1 main release.

Ubuntu Linux "Intrepid Ibex" 8.10, kernel 2.6.27-11, GNOME 2.24.1, OpenGL
fglrx release 2.1.8304. 2 GiB RAM, 2.2 Ghz Intel Core Duo. Sun Java 6
runtime environment build 6-10-0ubuntu2.

After dismissing a program window (either by closing the window or clicking
the Stop button), the editor enters a curious state where the keyboard
doesn't function at all, but the menu options still work fine. Switching to
another window and back, opening a new file, etc. do not help. An
application restart fixes the problem. There is no exception given.

My mistake. Opening a new file does solve the problem, but only for the new
file, not the original window.

So is this not a bug? Or if it is, can you provide a new description based
on what you've learned?

(In reply to comment #2)
> So is this not a bug? Or if it is, can you provide a new
description based
> on what you've learned?

I was just clarifying something, everything else I stated in my first post
is still correct.

Have you tried using the version of Java that's included with Processing,
or did it not work?

I can't replicate this on my Ubuntu 8.04 box, though the editor code (based
on JEditSyntax) is known to have problems of that sort from time to time.

Is there anything about your window manager setup, etc that might be give a
clue or help me replicate it?

Oh, hmm. Okay, Processing is using its own version of Java, not the Ubuntu
version.

As for my window manager, I really can't think of anything other than what
I already mentioned in the original post.

K, we'll keep this around in case others run across it; hopefully we can
figure out what's going on.

I can confirm that on my Ubuntu 8.10 netbook. I found out that saving the
file with another name restores normal operation. Ditto adding another tab
to the sketch or removing one.

Incidentally, I have no problems with either Ubuntu 7.10 or 8.04 installed
on another notebook and in my desktop, respectively. I should also add that
Ubuntu 8.10 netbook uses the "netbook remix" desktop and that I use
processing 1.0.3 on all three.

I think I figured this out. The SCIM is to blame. Disable it and things
will return to normal. You probably don't need SCIM anyway if you are not
using Asian languages.

If someone can confirm, I'll close the bug and add a note to the Linux
section of the troubleshooting notes.

I can confirm that SCIM is the source of the problem, but I have an even
better solution than disabling it. Go into SCIM Setup, and under Global
Setup, change the Keyboard Layout from "Unknown" to "English (US)." It
should work fine now.

(Of course, if your keyboard layout is not US, you should probably set it
to whatever is appropriate for your region.)

Thanks very much for the info--I'll add that to the Linux troubleshooting
page and close this report once I've had a chance to take care of that.

That solution stopped working this morning. Not sure why, but it's probably
because I restarted my computer.

Argh.

meaning that you need to redo the SCIM setting again after reboot? or after
reboot the "fix" doesn't work anymore?

and does disabling SCIM work consistently to fix the behavior?

Okay, I think I've figured it out now. It doesn't have anything to do with
the settings. You just have to close out of SCIM and open it up again. On
Ubuntu, you can do that by right clicking on the SCIM icon (usually a
keyboard) in the notification area and choosing "Exit SCIM" - it'll
automatically open up again.

Hope that helps.

k, searching for scim/java/ubuntu turns up plenty of reports of similar
problems, so it's clear that it's not a processing bug, but some kind of
scim issue. for instance:
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/293001
(that also lists another possible workaround)

marking as "invalid" since it's not a p5 bug, but i'll add these notes to
the linux troubleshooting page since it's clearly causing problems for a
handful of people.

feel free to post if there are further updates to the problem.

*** Bug 1265 has been marked as a duplicate of this bug. ***