I have a 64bit Debian Squeeze system running on an AMD platform:
root@kvm1:/home/nugai# uname -a
Linux kvm1 2.6.32-5-amd64 #1 SMP Fri May 10 08:43:19 UTC 2013 x86_64 GNU/Linux
The system is equipped with two Radeon HD6450 cards and four 1920x1280 monitors using the AMD proprietary 64bit drivers in Xinerama mode (acting pretty much as a single desktop). These displays seem to run fine.
I installed both Eclipse 4.2 Juno and Eclipse 4.3 Kepler (because of the problems I encountered) and both environments seem to run fine -- until the screensaver is activated in screen lock mode (i.e. screensaver with password protection; there is no problem without password protection). Whenever I have Eclipse running and the screensaver password protection kicks in (either because of inactivity timer or by selecting "System->Lock Screen" from System menu), I cannot get the user interface back: The Debian login screen with the password dialog box does not appear and the system doesn't accept the screensaver password even if typed blindly. I can tell that the display system must be running as I see the mouse pointer appear quickly (flashing) with every keystroke before the screen turns dark again. This behavior is independent of what the last active window was (Eclipse or some other application), or window size (full screen or not) and there is no difference in behavior depending on whether the system is just in screen lock mode or the displays have switched to power save mode (I see the monitors wake up from power save but I still cannot log in).
I isolated the problem to the point that I'm fairly sure it's Eclipse related. When the problem occurs, I can establish an SSH terminal session to the system and kill the Eclipse PID -- and then the login screen comes back immediately on the next keystroke on the affected system and it runs normally until I start Eclipse again and the screensaver kicks in once more.
The commands I execute on the SSH terminal to kill Eclipse are as follows (with the PID number changing every time):
root@kvm1:/home/nugai# ps aux |grep eclipse
nugai 13411 0.0 0.0 10668 936 ? S 12:19 0:00 eclipse
nugai 13412 36.7 1.6 1552608 413488 ? Sl 12:19 0:25 /usr/bin/java -Dosgi.requiredJavaVersion=1.6 -XX:MaxPermSize=256m -Xms40m -Xmx512m -jar /opt/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar -os linux -ws gtk -arch x86_64 -showsplash /opt/eclipse//plugins/org.eclipse.platform_4.3.0.v20130605-2000/splash.bmp -launcher /opt/eclipse/eclipse -name Eclipse --launcher.library /opt/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20130521-0416/eclipse_1506.so -startup /opt/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar --launcher.appendVmargs -exitdata 2128011 -product org.eclipse.epp.package.jee.product -vm /usr/bin/java -vmargs -Dosgi.requiredJavaVersion=1.6 -XX:MaxPermSize=256m -Xms40m -Xmx512m -jar /opt/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
root 13483 0.0 0.0 7548 872 pts/2 S+ 12:21 0:00 grep eclipse
root@kvm1:/home/nugai# kill -9 13412
I cannot figure out whether this is an Eclipse configuration problem or a bug. In the "ps aux" command, I noticed "-Dosgi.requiredJavaVersion=1.6" but I have Sun JDK 1.7 installed:
root@kvm1:/home/nugai# java -version
java version "1.7.0_17"
Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
Can anybody suggest how I can isolate this problem further and eventually solve it? Would there be a better forum for asking Eclipse installation questions?
[Updated on: Wed, 24 July 2013 01:21]
Report message to a moderator