[Paraview] No keyboard input on CentOS 5 (==Redhat Enterprise 5)

[Sean Ziegeler]

SCIM is respawned by init.  I haven't taken the time to determine what 
config file is responsible for that, since I can't do much about it 
where I work anyway.  As far as I can tell, SCIM lets you change things 
like keyboard layout and language on the fly.  It seems like the 
KWWidgets interface doesn't like it at times.  But I'm betting that the 
Qt interface in PV 3 doesn't have the problem.

While PV 3 will replace its predecessors soon, this little bug is kind 
of a put-off for new users that don't know what's going on.  If someone 
thinks its worth filing a bug report, I will.

-Sean

Bernhard Gschaider wrote:
> Yep. That did it for me. The fascinating thing is: scim came back
> (don't know why) and paraview kept accepting my keyboard input.
> 
> Thanks.
> 
> 
>>>>>> On Wed, 18 Apr 2007 08:16:23 -0500
>>>>>> "SZ" == Sean Ziegeler <seanzig at users.sourceforge.net> wrote:
> 
>     SZ> I don't know about the graphical problems, but I may be able
>     SZ> to help with the keyboard issue.  I've been meaning to post
>     SZ> this to the list anyway, but haven't bothered because it will
>     SZ> probably be resolved by PV 3 anyway.
> 
>     SZ> I use Fedora Core 6 which includes the Smart Common Input
>     SZ> Method (SCIM), and RHEL/CentOS 5 may as well.  It seems to
>     SZ> intermittently cause both PV 2.4.x & 2.6.x to ignore the
>     SZ> keyboard.  If you have root you can probably disable it, but I
>     SZ> don't, so I just kill SCIM and when it resets everything is
>     SZ> ok.  The following works for me:
> 
>     SZ> killall scim-launcher scim-helper-manager scim-panel-gtk
>     SZ> scim-bridge
> 
>     SZ> Hope that helps, Sean
> 
>     SZ> Bernhard Gschaider wrote:
>     >> Hi!  I've just recently updated my computer to CentOS 5. The
>     >> paraview installation remained the same.  Now Paraview is
>     >> behaving strangly: - When starting, the Splash-Screen looks
>     >> washed out (I think solarized is the name for the effects). The
>     >> filter-icons look the same. (But thats OK for working) - Some
>     >> of the textboxes (but not all of them) don't accept keyboard
>     >> input (that is serious). Among them are - the textboxes for the
>     >> editing of the colormap - the textbox for the file dialogs -
>     >> The "wheels" that are used for the transformations (scale etc)
>     >> look like the icons and behave strangly (hard to explain, but
>     >> they're hard to click and keep spinning) Does anyone have an
>     >> idea what the problem could be?  As I said: system is a CenOS
>     >> 5(for all practical purposes equal to Redhat Enterprise 5). The
>     >> machine is an Opeteron. Graphics-Board is an NVidia with the
>     >> vendor-driver compiled as a kernel-module.  The same effect can
>     >> be seen in a Paraview 2.4.3 and a 2.6 version I think one of
>     >> the libraries got updated and doesn't like paraview any
>     >> more. Canh anyone here with a deeper knowleadge about paraview
>     >> tell me which library could be to blame?  Thanks
>     >> _______________________________________________ ParaView
>     >> mailing list ParaView at paraview.org
>     >> http://www.paraview.org/mailman/listinfo/paraview
>     >> 
> 
> 
>