Solaris 10 + Cygwin Xwin on a headless system
I'm getting the following error when I connect from a PC using "C:\cygwin\usr\X11R6\bin\XWin.exe -query hostname -fullscreen -fp tcp/hostname:7100". My version of Cygwin is 1.5.9. Do I need to upgrade? ...Is this a known problem?
Error activating XKB configuration.
Probably internal libxklavier or gnome-settings-daemon problem.
X server version data:
The Cygwin/X Project
40300059
If you report this situation as a bug, please include:
- The result of xprop -root |grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherials/keyboard/xkb
Thanks!
# 1
BTW.I can't use the keyboard even if I'm running CDE over XDMCP. PC Xfree used to work fine with Solaris 9.
# 2
Nevermind. CDE works fine now. I only can't use the keyboard when running JDS.
# 3
I still need help getting XKB working with JDS in case there is any confusion.Thanks! :)
# 4
Hi,
i'm using hummingbird exceed, and under cde the keyboard works fine. in jds the keyboard also doesn't work, only the arrows, when a menu is open. Same behavior at your x-emulator ?
Than it is not a problem of your or my x server, but on the x-system with solaris 10 or specially with jds. Maybe a bug ?
Holger
# 5
Thanks for the prompt response, Holger!
That's pretty much what's going on with my system. I'll check if the arrows work under JDS when I get home tonight. I really hope that someone has a solution for me ...I'd love to take JDS for a spin but the CRT PC monitor (Sony 200SX) I have doesn't support the the refresh rate of the video board that's my Ultra-10, which BTW, is:
PROM Information: @(#)ffb2p.fth 2.9 98/07/14
FBC: version 0x3241906d
DAC: Brooktree 9070, version 1 (Pac2)
3DRAM: Mitsubishi 130a, version 1
EDID Data: Not Available
# 6
I have JDS working with Hummingbirds Exceed to a Solaris 10 intel box but a colleague with a similar setup fails. We are both running Exceed from an XP boxes so could it be something on his XP box JDS doesn抰 like?Peter
# 7
I too am getting this problem using either Exceed or the cygnus setup. Again it is only in JDS.The Solaris box is headless and doesn't actually have a keyboard, which might be what is causing the problem.
# 8
Same problem occurs when using VNC. Has anyone found a solution yet?
# 9
I have the same problem, I am using Exceed and X-Win 32, everything is fine when I use CDE environment but keyboard input does not work with JDS (sometime I have an input working).
# 10
I got the same problem with Xmanager, eXceed and some other Xserver i tested it with.. A bit weird that no sun people responds to this thread since its been discussed since Sol 10 GA was released..
# 11
Agreed. I also am suffering from this problem and we will not be using Solaris 10 on many of our systems until it is resolved.
Has anyone officially lodged a bug report with SUN?
Does anyone know if they are working on a patch or solution?
Would anyone from SUN care to respond?
This problem makes Solaris 10 on SPARC *useless* for anyone who requires XDMCP access for their users, which would constitute a significant percentage of users.
It also is quite embarassing for SUN. You can't tout a wonderful new look GUI to compete against Linux and Windows and then have it *not* work! Most SPARC boxes are not on peoples desks, they a larger shared machines, hence this problem is a showstopper.
# 12
It is a big big kidding. eh? The Solaris 10 X86 does not have the same problem. I hope Sun can solve it as soon as they can do.
# 13
I Use ReflectionX and I have the same exact problem, CDE is just fine, Under Java Desktop no keyboard, mouse is OK... I have been killing my self to get this fixed for a few days now... It's bug!!!
# 14
btw, my machine is a Sun Ultra 5, JDS looks really good and promising, it's a shame SUN does not mention on a fix yet.
# 15
I have the same problem with JDS3 on a SunFire E2900 (headless server). CDE keyboard works fine.
I found out something interesting though. If you install Soalris 10 on a box *with* a head, the same keyboard problem occurs until you log in *local* which then does something to make remote XDMCP access work from then on too. Of course, on a headless box this simply isn't an option.
Please post any patches to this thread!
# 16
I tried your workaround but did not work for me :-(
# 17
This may have something to do with this:
http://bugzilla.gnome.org/show_bug.cgi?id=152105
Also, I was able to temporarily get my keyboard to work by killing the gnome-settings-daemon. But this window was for maybe 1 second. Basically, I killed the daemon in an ssh windows to the server and then in my VNC session which has JDS up on a Sun Blade 100 running Solaris 10 GA I typed some random "stuff" in a terminal window. After a brief pause my text actually appeared in the terminal window but then the gnome-settings-daemon restarts and the keyboard goes dead again.
One way to get response is to call Sun Support and report this. The more people who do maybe something will get communicated.
# 18
Just out of curiousity - has anyone tried doing a VNC or XDMCP connection to a Solaris 10 x64 server rather then a Solaris 10 SPARC server ?I asked because Solaris 10 x64 uses the Xorg X server and Solaris 10 SPARC appears to still be using the Sun X server.
# 19
Running Solaris 10 SPARC using JDS, I had mouse but not keyboard in a Exceed 9 XDMCP session on Windows XP.
I quit the session and logged into the Sun box locally (as suggested by stan.buchanan). I then went back to the XP box and restarted the XDMCP session.
The screen resolution was different from the first session. It now mimicked the resolution on the Sun rather than the lower resolution I was using on the PC. During session startup, I received two error messages:
* The application "wnck-applet" quit unexpectedly.
* The panel encountered a problem while loading "OAFIID:GNOME_ShowDesktopApplet". Details: Unknown CORBA exception id: 'IDL:omg.org/CORBA/INV_OBJREF:1.0'
But the mouse and keyboard now work fine.
# 20
There is a sunsolve doc that implements a workaround that fixed the problem for me: http://sunsolve.sun.com/search/document.do?assetkey=1-9-81175-1&searchclaus e hthRob.
# 21
I followed the instrucations. Now I can't start JDS at all. I get the login screen, type in my credentials, it goes away and then it comes right back. What am I doing wrong?
# 22
In my case, the file already existed. The way i solved it was to rename the original, touch a new file, vi the new file and then paste in the fixed lines. Finally, i logged out of the console.All of this was done as root, and worked first time.
# 23
Patches have been issued to fix JDS bug 6239595 ("keyboard does not work when remote logged in from linux to sparc", which applies not just to Linux but pretty much remote display to anything not a SPARC).
Solaris 10 SPARC patch: http://sunsolve.sun.com/search/document.do?assetkey=1-21-119542-01-1
Solaris 10 x86 patch: http://sunsolve.sun.com/search/document.do?assetkey=1-21-119543-01-1
# 24
I just applied http://sunsolve.sun.com/search/document.do?assetkey=1-21-119542-05-1 (119542-05) to my Ultra 10, and I can now use my keyboard using Cygwin/X to XDMCP into the Ultra10 from Windows XP SP1 (otherwise fully-patched Windows box) with a Dell UK keyboard.
# 25
I am facing the sam eproblem when using Cygwin from my PC to log-on my SUN Workstation. I cannot use the keyboard. It gives me some XKB error..
# 26
Hey I just wanted to mentioned that I have the same problem but something wierd just happened. I left my session logged in over night and I come today and was able to type into the screen saver window!!! Then I was like how is that possible, so I started to type in other windows and it worked. Maybe this can lend some clues on what to do to at least get a temp solution going?
brando.
# 27
I posted previously at the end of this thread, and found that xscreensaver saves the day sort of. Once I found that after xscreensaver starts the keyboard is activated I decided to put xscreensaver in my startup programs that way it would activate the keyboard once I logged in. It worked just as expected but gnome-panel crashed. No worries just opened up a terminal sessions and started it up.
# Once xscreensaver started, in about 15 minutes of no activity I found out where command was and then used java launch menu to added it to
# sessions startup programs menu. That is located in Preferences -> Desktop Preferences -> Sessions
/usr/openwin/bin/xscreensaver-command -lock
So once I was able to log in xscreensaver started but I had a problem logging out so I just closed the Xwindows session. Gnome-panel still must have been active because I recieved error stating that fact.
First time I just opened up terminal by right clicking and chosing Open Terminal. Then type in "gnome-panel" and it worked. I tried to log out again, but again I could not log out so closed window again. Then I log in again, this time the previous command did not work. So I did these commands.
ps -ef |grep gnome-panel
# found id of process and killed it
kill id_that_found
# started gnome-panel again.
gnome-panel
brando.
