Hello, Solaris Community!
We have Solaris 10 installed on Sun Blade 1000.
When connected to Gnome(Sun Java Desktop System 3) Xterminal from PC using X-Win v6.1 Xterminal client keyboard input doesn't work. Mouse works properly and there are no any another bugs. When connected to CDE Xterminal keyboard work fine. Have you any suggestions about it?
Sincerely yours, TafKoS
I met the same problem:
when using Xterminal software, no keyboard response under
JDS in Solaris 10 GA version,though I am using commercial Xterminal software: Reflection X 11.0.0 from WRQ, so the problem is not restricted to only Cgywin or others alike.
Waiting for Sun's solution...
> I can't use my home,
> end, pageup, and pagedown keys inside of
> gnome-terminal form the system in question (not
> remotely).
Solaris' xterm terminfo database entry does not define key
sequences for these keys.
Can be fixed by re-compiling the xterm entry, with khome, kend,
knp, kpp sequences defined:
mkdir /tmp/foo
env TERMINFO=/usr/share/lib/terminfo /bin/infocmp xterm > /tmp/foo/xterm.ti
echo ' knp=\E[6~, kpp=\E[5~, kend=\EOF, khome=\EOH, ' >> /tmp/foo/xterm.ti
env TERMINFO=/tmp/foo /bin/tic -v /tmp/foo/xterm.ti
env TERMINFO=/tmp/foo less /etc/termcap
For gnome-terminal, you must replace the original
/usr/share/lib/terminfo/x/xterm file with the new one in
/tmp/foo/x/xterm, then stop all gnome-terminal processes and
restart gnome-terminal.
Got my keyboard working, not really sure how
After installing Solaris 10 3/05 and JDS 3 on a headless E450 I experienced the exact problem described in this post. I tried connecting using both Exceed and VNC and was not able to enter text from the keyboard after starting a JDS session. Now I am able to enter text, but unfortunately I'm not sure which change fixed the problem so I'll list the changes I made that may have had an affect. Since, the keyboard is now working I am not able to test these individually.
1. I noticed that I had inadvertantly left my .cshrc file owned by root. I fixed this.
2. I logged into the server using CDE rather than JDS. While logged into CDE the keyboard worked fine.
3. I opened the Launch/Preferences/Desktop Preferences/Keyboard/Behavior window and unchecked the Repeat Keys and Cursor Blinking check boxes, then closed the window.
After making the changes listed above I was am able to enter text into multiple applications while using JDS. I'm not sure which, if any, of these changes eliminated the problem.
I have also notice an error message each time I log in now. It says that the wnck-applet has unexpectedly quit and is then followed by: "The panel encoutered a problem while loading OAFIID:GNOME_ShowDesktopApplet Details: Unknown CORBA exception id: 'IDL:omg.org/CORBA/INV_OBJREF:1.0'
I am having the exact same issue trying to remotely login to a headless Ultra10 running Solaris10 build 74 (JDS- When logging into CDE...no probs).
I have tried the suggestions in these replies but to no avail.
It seems to be an incompatability between the kb extension and gnome as the dt session log states:
Window manager warning: Log level 32: could not find XKB extension.
Yet my Xsun process seems to have the kb extension activated:
/usr/openwin/bin/Xsun :0 -aud it 0 -nobanner +kb -auth /var/lib/gdm/:0.Xauth
Are we any closer to this one yet?
Cheers, db101
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!
> 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!
I tried this on an ultra 5 and it still doesn't work.
Dan
I've found this on SunSolve today and it's work:
A workaround is to log directly on the sparc machine (or remotely via a CDE or failsafe session).
run gconf-editor and remove all key defined in /apps/gnome_settings_daemon/keybindings
Then remotely login in a JDS 3 session, the key grab won't happen.
I've unset the values, it create a file %gconf.xml in the directory $HOME/.gconf/apps/gnome_settings_daemon/keybindings
The file contains the following lines:
<?xml version="1.0"?>
<gconf>
<entry name="volume_up" mtime="1110896708" type="string">
<stringvalue></stringvalue>
</entry>
<entry name="volume_mute" mtime="1110896705" type="string">
<stringvalue></stringvalue>
</entry>
<entry name="volume_down" mtime="1110896702" type="string">
<stringvalue></stringvalue>
</entry>
<entry name="help" mtime="1110896698" type="string">
<stringvalue></stringvalue>
</entry>
</gconf>
> I've found this on SunSolve today and it's work:
>
> A workaround is to log directly on the sparc machine
> (or remotely via a CDE or failsafe session).
>
> run gconf-editor and remove all key defined in
> /apps/gnome_settings_daemon/keybindings
>
> Then remotely login in a JDS 3 session, the key grab
> won't happen.
It works for me, but do you have a link for the sunsolve article I had already looked and found nothing.
T
> These workarounds have not solved the issue for me.
> Even if they did, they are just workarounds, and not
> something we want to implement across hundreds of
> users.
>
> I have lodged a case with SUN support and I will
> report back on progress and a bugid as soon as I get
> one.
If you copy that file to relevant place in /etc/gconf/gconf.xml.defaults it will work for other users.
Same here, and creating it with the file inside has not worked for me. I get the following error on login:
Error activating XKB configuration.
Probably internal libxklavier or gnome-settings-daemon problem.
X server version data:
The Cygwin/X Project
60801000
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/peripherals/keyboard/xkb
The output from the above xprop command (run by ssh'ing to the system and redirecting X to a local cygwin X sever on the PC):
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us", "", ""
The output from the above gconftool-2 command is:
layouts = [us]
model = pc105
overrideSettings = false
options = []
Perhaps the problem is something to do with xkb thinking its a xorg server rather than the SUN X server - not sure why the xprop output has xorg in it - x86 uses xorg, but not the SPARC version.
After some testing I think i've got it, it works for every user i've tried.
Create the file :
/etc/gconf/gconf.xml.defaults/apps/gnome_settings_daemon/keybindings/%gconf.xml
Put in it :
<?xml version="1.0"?>
<gconf>
<entry name="volume_up" mtime="1110896708" type="string">
<stringvalue></stringvalue>
</entry>
<entry name="volume_mute" mtime="1110896705" type="string">
<stringvalue></stringvalue>
</entry>
<entry name="volume_down" mtime="1110896702" type="string">
<stringvalue></stringvalue>
</entry>
<entry name="help" mtime="1110896698" type="string">
<stringvalue></stringvalue>
</entry>
</gconf>
Can anyone test this on a different machine. I've tried it on my Ultra 5 and seems to sort the problem on new and existing users.
Dan
> I've unset the values, it create a file %gconf.xml in
> the directory
> $HOME/.gconf/apps/gnome_settings_daemon/keybindings
>
> The file contains the following lines:
>
> <?xml version="1.0"?>
> <gconf>
> <entry name="volume_up" mtime="1110896708"
> 0896708" type="string">
><stringvalue></stringvalue>
> </entry>
> <entry name="volume_mute" mtime="1110896705"
> 0896705" type="string">
><stringvalue></stringvalue>
> </entry>
> <entry name="volume_down" mtime="1110896702"
> 0896702" type="string">
><stringvalue></stringvalue>
> </entry>
> <entry name="help" mtime="1110896698"
> 0896698" type="string">
><stringvalue></stringvalue>
> </entry>
> </gconf>
This is quite intresting..., this folder did not exist in my $HOME, and even by creating it, with this %gconf.xml, the problem was still there....
But, when I change /etc/gconf/gconf.xml.defaults/apps/gnome_settings_daemon/keybindings/%gconf.xml with the values described..., I still receive an error message, but the keyboard works!!!
> After some testing I think i've got it, it works for
> every user i've tried.
> Create the file :
>
> /etc/gconf/gconf.xml.defaults/apps/gnome_settings_daem
> on/keybindings/%gconf.xml
>
> Put in it :
>
> <?xml version="1.0"?>
> <gconf>
> <entry name="volume_up" mtime="1110896708"
> type="string">
> <stringvalue></stringvalue>
> </entry>
> <entry name="volume_mute" mtime="1110896705"
> type="string">
> <stringvalue></stringvalue>
> </entry>
> <entry name="volume_down" mtime="1110896702"
> type="string">
> <stringvalue></stringvalue>
> </entry>
> <entry name="help" mtime="1110896698" type="string">
> <stringvalue></stringvalue>
> </entry>
> </gconf>
>
>
> Can anyone test this on a different machine. I've
> tried it on my Ultra 5 and seems to sort the problem
> on new and existing users.
>
> Dan
Hi There,
I just tried this on my older sun box (clone - Dual Ultra Sparc II - 400Mhz) and this worked like a charm. When I tried making these changes through the gconf-editor (to unset the keybindings) it would never set properly.
This has done the trick!
Thanks!
Indeed, this also allowed me to login and use the keyboard, however I still get the xkb error on login. For a completely fresh, new user, this appears 8 times, thereafter on each login only once.
I still have the problem of the logout option not working. It simply hangs the "Java" start here button - is anyone else experiencing this?
My system is a V440 with 03/05 on it.
I tried your suggestion, but it did not work.
My machine:
SunOS xxxxx 5.10 Generic sun4u sparc SUNW,Sun-Fire-V440
My Xserver running on Windows is eXceed 7.0.
Can you undo your change and see if the problem reoccurs?
(I suspect there is some other trick or a combination of tricks
to get this to work. That single trick does not work for me.)
-David
For anyones info, I spent several hours looking into this.
The sun doucment below exactly provides the solution, not that I understand why though.
http://sunsolve.sun.com/search/document.do?assetkey=1-9-81175-1&searchclaus e=
Prioe to this solution Itried many different PC X Servers with no success, CDE was fine. The file mentioned in the above document already existed but I removed it all and put the suggested values in. It works.
Using Solaris 10 and E450.
Simon
The solution provided resolves the keyboard problem, however I also get the same error cited previously:
the wnck-applet has unexpectedly quit and is then followed by: "The panel encoutered a problem while loading OAFIID:GNOME_ShowDesktopApplet Details: Unknown CORBA exception id: 'IDL:omg.org/CORBA/INV_OBJREF:1.0'
Dan is the MAN!!!!!
I don't understand how the "volume" string values have anything to do with my keyboard not working in my Xterm session, but you were right on the money. It worked great for me. Thanks for saving me hours of agony!!!!
BTW...using Cygwin to connect to Sun Ultra 5
Brian
It worked for me as well.
I still get the dialogues about XKB and so on but I can type again.
I had Solaris 10 3/05 on a V240 and I was using X-Win v8 to connect to it.
There were entries in the .xml file already but they didn't include the emtpy string value portion.
I replaced them with the ones in this list and viola!
now to upgrade to 6/06.
I found a way out:
Just replace fiel /etc/gconf/gconf.xml.defaults/apps/gnome_settings_daemon/keybindings/%gconf.xml with contents below:
<gconf>
<entry name="volume_up" mtime="1110896708" type="string">
<stringvalue></stringvalue>
</entry>
<entry name="volume_mute" mtime="1110896705" type="string">
<stringvalue></stringvalue>
</entry>
<entry name="volume_down" mtime="1110896702" type="string">
<stringvalue></stringvalue>
</entry>
<entry name="help" mtime="1110896698" type="string">
<stringvalue></stringvalue>
</entry>
</gconf>
save your file and relogin with your xmanager,you can use your xterminal now.
wish you good luck.
I found it on:http://sunsolve.sun.com/search/document.do?assetkey=1-9-81175-1
