-
Bug
-
Resolution: Won't Fix
-
P3
-
None
-
6u13
-
x86
-
linux_redhat_5.0
OS/Platform:
RHEL 5.2 x64
JDK: 6u6, 6u11 ( checked on b07 rev ), 6u12, 6u13 ( b01 j4b ) linux-i586 bundle
Host: stt-45.russia, stt-28.russia
User: root
Desc:
When we start ControlPanel( or javaws <jnlp_file_url> ) we got msg:
>/export/jdk/root/jdk1.6.0_11/jre/bin/ControlPanel
Launching a SCIM daemon with Socket FrontEnd...
GTK IM Module SCIM: Cannot connect to Panel!
There is no ControlPanel appeared ( no jnlp app is executed in case of javaws ),
'ps' shows several java processes running.
It happened under user root ( see attached 'set' output - set_root.txt), all OK under stt-robot ( see env in set_stt-robot.txt ).
Also there is no problems when we are using linux-amd64 bundle for both users.
In case of root + linux-x64 bundle we got messages:
[root@stt-45 root]# ./x64/jdk1.6.0_13/bin/ControlPanel
Launching a SCIM daemon with Socket FrontEnd...
Loading simple Config module ...
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
GTK Panel of SCIM 1.4.4
and ControlPanel appeared.
There is a workaround exist:
assign another ( not scim ) value to GTK_IM_MODULE var, f.e
GTK_IM_MODULE=gtk-im-context-simple or just GTK_IM_MODULE=""
Not sure if this issue is deployment related or not.
RHEL 5.2 x64
JDK: 6u6, 6u11 ( checked on b07 rev ), 6u12, 6u13 ( b01 j4b ) linux-i586 bundle
Host: stt-45.russia, stt-28.russia
User: root
Desc:
When we start ControlPanel( or javaws <jnlp_file_url> ) we got msg:
>/export/jdk/root/jdk1.6.0_11/jre/bin/ControlPanel
Launching a SCIM daemon with Socket FrontEnd...
GTK IM Module SCIM: Cannot connect to Panel!
There is no ControlPanel appeared ( no jnlp app is executed in case of javaws ),
'ps' shows several java processes running.
It happened under user root ( see attached 'set' output - set_root.txt), all OK under stt-robot ( see env in set_stt-robot.txt ).
Also there is no problems when we are using linux-amd64 bundle for both users.
In case of root + linux-x64 bundle we got messages:
[root@stt-45 root]# ./x64/jdk1.6.0_13/bin/ControlPanel
Launching a SCIM daemon with Socket FrontEnd...
Loading simple Config module ...
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
GTK Panel of SCIM 1.4.4
and ControlPanel appeared.
There is a workaround exist:
assign another ( not scim ) value to GTK_IM_MODULE var, f.e
GTK_IM_MODULE=gtk-im-context-simple or just GTK_IM_MODULE=""
Not sure if this issue is deployment related or not.