Red Hat Bugzilla – Bug 176281
Logging in via X session not possible: login screen blank
Last modified: 2015-01-04 18:19:44 EST
When attempting to run the startconsole application remotely via
X over ssh (client: Fedora Directory console on RHEL4, server: X11 for MacosX
v10.4.3), the login screen flashes briefly with the login parameters, then goes
blank as per the attached screengrab.
In addition, as the background splash screen is bigger than the login screen
window, clicking on the splash screen hides the login screen making it
impossible to either log in or shut down without killing startconsole.
Created attachment 122466 [details]
Screenshot of the problem
Looks like the splash screen is causing more problems. Try
startconsole -x nologo .....
Nathan, I think we are going to need to put some sort of timer on the splash
screen to make it disappear after a few seconds, or something like that.
Just tried the -x nologo, and the logo dutifully disappears, but the login
window still stays blank. :(
What version of java are you using? This is usually some problem with the
interaction between java and X and/or the window manager.
The Java version is
[root@gatekeeper fedora-ds]# java -version
java version "1.5.0_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-b05)
Java HotSpot(TM) Client VM (build 1.5.0_05-b05, mixed mode, sharing)
The same version works fine from X locally on the machine, as soon as it's over
X over ssh it doesn't want to work. :(
Yes. We always have weird problems with using java and a remote display. I've
seen similar problems over the years with PCAnywhere, VNC, remote X display
(especially if the host system X version is not exactly the same as the client
system X version).
Is this a Java problem or a Fedora console problem? Not being able to use the
console via X is a serious limitation on the usefulness of the console.
It's a java problem.
One way to work around the console remote display problem is to install the
console locally, and have it connect to the remote ldap and admin server via
ldap and http.
I'm going to close this bug as notabug, and just hope that some later version of java will not have this problem.