Mailinglist Archive: opensuse-bugs (13484 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=331614#c15





--- Comment #15 from Mike Fabian <mfabian@xxxxxxxxxx>  2007-10-18 04:57:03 MST 
---
There are a few things I don’t understand though.

The script /etc/X11/xim.d/scim-bridge, which is used to init the input
method when scim-bridge is used, contains:

    export XMODIFIERS=@im=SCIM
    export GTK_IM_MODULE=scim-bridge
    export QT_IM_SWITCHER=imsw-multi
    export QT_IM_MODULE=scim-bridge
    case "$WINDOWMANAGER" in
        *kde)
            if ! type -p skim > /dev/null 2>&1 \
              || grep -i -q "^[[:space:]]*Autostart.*=.*false"
$HOME/.kde/share/config/skimrc
            then
                scim -d
            else
            # skim will be  used. But we don't start it here,
            # we rely on the KDE autostart
            # mechanism used in the skim package instead.
            # skim -d
            :
            fi
        ;;
        *)
            scim -d          
        ;;
    esac

I.e. in the non-KDE case it already executes "scim -d".  In case of
KDE, it executes "scim -d" only if the automatic start of skim has
been disabled in the setup dialog of skim, then it assumes that the
user wants to use scim instead of skim and therefore it starts "scim
-d" in this case. If skim is not disabled, the autostart mechanism of
KDE will start skim, which should be the same as calling "skim -d"
from the command line.

So why doesn’t this work for Truth and why does it work for me?

I am using KDE on a 64bit system as well and I don’t run into that
problem.

And what does this have to do with 64bit? Nothing in the
/etc/X11/xim.d/scim-bridge is 64bit specific and Peng Wu’s patch
doesnt’t seem to be 64bit specific either.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.