Community
Participate
Working Groups
Hi, I am using Eclipse CDT (Version: Luna Service Release 1 (4.4.1) Build id: 20140925-1800) on CentOS 7 to edit some file (without any extension). The control key works fine for awhile and then all a sudden, it stops working (i.e. ctrl+c doesn't copy anything I highlight the editor but it still works if I copy the version of eclipse in its "About Eclipse" dialog). If I kill the eclipse process and then start again, the ctrl key works for awhile and then the same issue kicks in. Any idea?
And interesting enough, as soon as I finished my first comment, I went back to Eclipse CDT. The ctrl key works again. Not sure it provides any extra info.
When Ctrl key stops working in C/C++ Editor, does it continue to work in Eclipse text editor?
I haven't tried yet. But instead, on the same machine, I tried to use purely C++ editor only. At some point, the ctrl+any key stopped working but if I double clicked on a C++ file to open, the ctrl+any key works again.
Please reopen if you can provide reproduction steps.
I don't have definite steps to reproduce. It just keeps happening. Is there a way to enable the "trace" level of logging so that I can collect logs for you guys to look into. It is very not productive that I have to close Eclipse CDT every hour or so. P.S. I have updated to Build id: 20150109-0600.
(In reply to Henry Chan from comment #5) Please respond to the question contained in comment #2
Are you using GTK3? There is known bug about this somewhere... Could you try launching with SWT_GTK3=0 environment variable? For example: SWT_GTK3=0 ./eclipse
Bug 435742? When it happens to me, I switch to a different editor tab, and then it usually works again.
Hi Marc, Yes, I am indeed using GTK 3.0: $ ldconfig -p | grep gtk libwebkitgtk-3.0.so.0 (libc6,x86-64) => /lib64/libwebkitgtk-3.0.so.0 libspice-client-gtk-3.0.so.4 (libc6,x86-64) => /lib64/libspice-client-gtk-3.0.so.4 libreport-gtk.so.0 (libc6,x86-64) => /lib64/libreport-gtk.so.0 libpeas-gtk-1.0.so.0 (libc6,x86-64) => /lib64/libpeas-gtk-1.0.so.0 libnm-gtk.so.0 (libc6,x86-64) => /lib64/libnm-gtk.so.0 libjavascriptcoregtk-3.0.so.0 (libc6,x86-64) => /lib64/libjavascriptcoregtk-3.0.so.0 libgtksourceview-3.0.so.1 (libc6,x86-64) => /lib64/libgtksourceview-3.0.so.1 libgtkmm-3.0.so.1 (libc6,x86-64) => /lib64/libgtkmm-3.0.so.1 libgtkmm-2.4.so.1 (libc6,x86-64) => /lib64/libgtkmm-2.4.so.1 libgtk-3.so.0 (libc6,x86-64) => /lib64/libgtk-3.so.0 libgtk-x11-2.0.so.0 (libc6,x86-64) => /lib64/libgtk-x11-2.0.so.0 libgtk-vnc-2.0.so.0 (libc6,x86-64) => /lib64/libgtk-vnc-2.0.so.0 libcolord-gtk.so.1 (libc6,x86-64) => /lib64/libcolord-gtk.so.1 libclutter-gtk-1.0.so.0 (libc6,x86-64) => /lib64/libclutter-gtk-1.0.so.0 libcheese-gtk.so.23 (libc6,x86-64) => /lib64/libcheese-gtk.so.23 libchamplain-gtk-0.12.so.0 (libc6,x86-64) => /lib64/libchamplain-gtk-0.12.so.0 libcanberra-gtk3.so.0 (libc6,x86-64) => /lib64/libcanberra-gtk3.so.0 libcanberra-gtk.so.0 (libc6,x86-64) => /lib64/libcanberra-gtk.so.0 libavahi-ui-gtk3.so.0 (libc6,x86-64) => /lib64/libavahi-ui-gtk3.so.0 I tried to minimize Eclipse CDT and then maximize few times but the problem persisted. Let me try out your workaround -- SWT_GTK3=0. I will report back after a week. Thanks!
Marc's workaround SWT_GTK3=0 ./eclipse works. I have been using it for a week without running into the same issue. Thanks!
Thank you for the update! This will be fixed (hopefully) in SWT. *** This bug has been marked as a duplicate of bug 435742 ***
