[Fedora-i18n-bugs] [Bug 1231499] New: ibus can't type in Telegram(from KDE 5)

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1231499

Bug ID: 1231499
           Summary: ibus can't type in Telegram(from KDE 5)
           Product: Fedora
           Version: 22
         Component: ibus
          Assignee: [e-mail]
          Reporter: [e-mail]
        QA Contact: [e-mail]
                CC: [e-mail],
                    [e-mail], [e-mail]

Description of problem:
I can't type Chinese with ibus-libpinyin in Telegram, which is provided by KDE5
in Fedora 22

Version-Release number of selected component (if applicable):
ibus 1.5.10
Intelligent Pinyin 1.7.1

How reproducible:
Always

Steps to Reproduce:
1. Logging into Telegram, start a chat
2. Switch Input Method ibus-libpinyin by Ctrl+Space (My config)
3. Type something, like "nihao". In other softwares, there will be a list of
candidates to choose, including 你好, 你, 泥, etc. But in Telegram, "nihao" is
shown in the chat box, and no candidates are shown.
4. If I type Chinese in other places, then copy them to Telegram, then it works
fine

Actual results:

Expected results:

Additional info:
My .xprofile:
export GTK_IM_MODULE="ibus"
export QT_IM_MODULE="ibus"

My .bashrc:
export GTK_IM_MODULE="ibus"
export QT_IM_MODULE="ibus"
export XMODIFIERS=@im=ibus

[Fedora-i18n-bugs] [Bug 1231499] ibus can't type in Telegram(from KDE 5)

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1231499

fujiwara  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |NOTABUG
        Last Closed|                            |2015-06-15 01:16:58

--- Comment #1 from fujiwara  ---
I downloaded Telegram from https://telegram.org/dl/tdesktop
and run ldd

# ldd Telegram/Telegram 
    linux-vdso.so.1 (0x00007ffcef5e9000)
    libX11.so.6 => /lib64/libX11.so.6 (0x00007f4eb94df000)
    libX11-xcb.so.1 => /lib64/libX11-xcb.so.1 (0x00007f4eb92dd000)
    libxcb.so.1 => /lib64/libxcb.so.1 (0x00007f4eb90bb000)
    libdl.so.2 => /lib64/libdl.so.2 (0x00007f4eb8eb7000)
    librt.so.1 => /lib64/librt.so.1 (0x00007f4eb8caf000)
    libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f4eb8975000)
    libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f4eb8759000)
    libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f4eb83d7000)
    libm.so.6 => /lib64/libm.so.6 (0x00007f4eb80cf000)
    libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f4eb7eb8000)
    libc.so.6 => /lib64/libc.so.6 (0x00007f4eb7af8000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f4eb9820000)
    libXau.so.6 => /lib64/libXau.so.6 (0x00007f4eb78f4000)

It does not link qt libraries so I guess this runs qt with a special way it
does not send QT_IM_MODULE to QApplication::QApplication(int&, char**, int)().
I think this problem cannot be fixed in ibus and Telegram is a closed code.

http://twitter.com/telegram or http://telegram.org/support

telegram-cli can be downloaded and it works with ibus.

% telegram-cli
> msg peer test