| Summary: | net-im/telegram-desktop-2.7.1-r1: Switching IBus input methods does not work in Telegram | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Petr Šabata <contyk> |
| Component: | Current packages | Assignee: | Esteve Varela Colominas <esteve.varela> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | ionen, proxy-maint |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Petr Šabata
2021-03-30 11:04:10 UTC
Additionally, using more complicated input methods (such as ibus-hangul) doesn't appear to work at all -- it just outputs latin characters instead of entering the combining mode. Again, this works elsewhere, including Featherpad. As reproducing this requires setting up some programs I'm not familiar with, could you first test it with the official tdesktop binaries downloaded from https://desktop.telegram.org/ ? Also, for future reference, it'd be helpful to know what your telegram-desktop USE and C(XX)FLAGS flags are, your QT_QPA_PLATFORMTHEME and DESKTOP_APP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY variables. (In reply to Esteve Varela Colominas from comment #2) > As reproducing this requires setting up some programs I'm not familiar with, > could you first test it with the official tdesktop binaries downloaded from > https://desktop.telegram.org/ ? Okay, this happens with 2.7.1 from upstream, too. So either it's an upstream bug or Telegram suddenly requires something else to be configured :| I think I'll try building IBus with the "kde" USE flag to see if that helps... > Also, for future reference, it'd be helpful to know what your > telegram-desktop USE and C(XX)FLAGS flags are, your QT_QPA_PLATFORMTHEME and > DESKTOP_APP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY variables. Okay, for the record here: USE="X dbus gtk hunspell pulseaudio spell -enchant (-libressl) -wayland" C[XX]FLAGS are the same as the global ones shown in the initial report. QT_QPA_PLATFORMTHEME is unset. DESKTOP_APP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY is unset. (In reply to Petr Šabata from comment #3) > I think I'll try building IBus with the "kde" USE flag to see if that > helps... That actually fixed it. Hopefully this report will help someone in the future. Closing. I wonder if there's a way to warn people about this; I can't make telegram-desktop depend on ibus so can't enforce this USE flag... (In reply to Esteve Varela Colominas from comment #5) > I wonder if there's a way to warn people about this; I can't make > telegram-desktop depend on ibus so can't enforce this USE flag... If want to have a elog/warn message to warn without bothering non-ibus users, you could have a "has_version app-i18n/ibus && ! has_version app-i18n/ibus[kde]" in postinst. Not that it's perfect given ibus might not even be installed yet or those having it might not actually be using it. If there's a lot of other small things to convey, making a wiki page could also be an option, good odds people will find it when having issues. (In reply to Ionen Wolkens from comment #6) very good suggestions for pkg_postinst/wiki.. also you may take a look at readme.gentoo-r1.eclass if you find the warning/info are tedious.. Well, after a reboot the broken behavior is back even with IBus being built with the "kde" USE flag. Mysterious. I'll let you know if I ever figure it out. |
