Tdesktop: Desktop client is not "reading" my accentuated letters using composite keys

[facundobatista]

When I normally write in all the rest of the programs, if I hit ' and e, I see é.

However, in Telegram app it appears the e without the tilde.

Same happens for all the composite letters. Note that this doesn't seem to be an "unicode" problem... if I hit "ñ" (I have a separate key in the keyboard for it), it appears ok.

Thanks!

[facundobatista]

auchri: thanks for checking! I'm seeing that #27 is about _showing_ those characters... and my problem was about _inserting_ them

However, I just tried it again, and it worked! very, very strange: I just closed the window half an hour ago and now I reopened it: no even restarted the telegram process.

I'll have to debug this deeper... any hint? (like starting telegram in --debug in the terminal or something)

Thanks

[facundobatista]

So, I finally reproduced the sequence for this to happen. It's very weird.

Let's start from the process being started, the Telegram window is not open, but the icon in the systray is ok. I click in that icon, choose "Open Telegram", and the main window pops up.

There, if I use composite keys (again, for example, ' and e would make an é) all works ok. I send the message, the entry box is clean.

Then I commute with to other window (alt-tab, or clicking somewhere else), and when I'm back, the composite keys no longer work!!!

Then I close the window. Go to the systray icon, and make it open again, and composite keys work fine. Until next window switching, of course.

I'll very glad to help you with this debugging.

Thanks!

[ralesk]

I'm afraid your steps don't destroy neither dead keys nor compose sequences in my Telegram :(

(Fedora 21 + KDE 4 in my case)

[facundobatista]

So it doesn't happen everywhere! This is good news (even if it may complicate the debugging).

[ralesk]

I wonder if the linux release also uses its own Qt (and doesn't just ship with it, it really loads those libs), if it doesn't, maybe there's a bad patch (or the lack of it) in the distro's Qt.

Or maybe it's higher up. Maybe it's something in the desktop environment doing something weird with the keyboard (in early versions of KDE4 kwin the alt key could get stuck after alt-tabbing — so hmm, try another window manager than the one you're currently using and see if the issue can be reproduced then), maybe it's something on the X11 level (examining distro patches could help here, but I'm not sure which part of X.Org we should be looking at precisely).

[ricardobarantini]

I have the same problem in Ubuntu 14.10.

[kaluosi]

I have the same problem with Ubuntu 14.04 LTS. I have try to resolve it installing ibus-qt4
but it does not work.

[eullerborges]

Also having the same problem on Ubuntu Gnome 14.04 LTS. Installing ibus-qt4 didn't solve it either.

[musantro]

Also having the same problem on Ubuntu 15.10. Installing ibus-qt4 didn't solved it.
This issue only happens in Telegram desktop; in other programs the accent works fine.

[alfonsonishikawa]

Same problem in Xubuntu 15.10. I have to copy from Mousepad and paste in Telegram to get the tildes.

[Patola]

Same problem in Ubuntu 16.04 64-bits, Unity desktop environment. And I have an almost identical computer with the same version of Ubuntu in which it does not happen. Even tried to switch the GTK_IM_MODULE variable to no avail.

[kiov]

I have the same problem but only in the send image window, and sometimes it just works.

Steps:

1. Select a conversation
2. Click the camera icon
3. Select an image
4. On the new windows use compose key for any char sequence.

Workarround: minimize the application with the send image windows open and restore.

I'm using Debian testing/sid with 5.5.1 qtbase-abi-5-5-1 and almost all KDE/Plasma form experimental repos.

[narcelio]

Workaround: call with QT_IM_MODULE=xim /opt/telegram/Telegram

[alfonsonishikawa]

@narcelio's solution works in Xubuntu 16.04.

Had to write the command as env QT_IM_MODULE=xim /opt/telegram/Telegram in my launcher, although.

[eullerborges]

@narcelio's solution works like a charm on Ubuntu Gnome 14.04!

[aldonogueira]

Same problem here on elementary OS Loki. The workaround of setting QT_IM_MODULE=xim solves the problem, but then I noticed that the default value is QT_IM_MODULE=ibus. Thus, adding "ibus-daemon" to the list of apps run at initialization works as well.

[Starkie]

@narcelio's solution worked for me on Xubuntu 16.04, with Spanish keyboard layout.

[sgregori]

@facundobatista @narcelio Solution works like a charm ( spanish keyboard ) thank you very much!!

[xkrambler]

@narcelio +1 Solution works like a charm (Spanish keyboard also)

[caco13]

@narcelio's solution works well, adding @alfonsonishikawa tip (env) in Xubuntu Menu Editor Application Laucher.

[nienkeboomsma]

I am experiencing exactly the same bug on Windows. @facundobatista's observation that accented characters work again once you re-open Telegram from the system tray is still applicable. Not really workable though, to re-open Telegram from the system tray every time you've switched windows.

Happy to see there's a fix for Linux, has any fix been found for Windows?

[Darkhogg]

Still happening to me on Ubuntu 16.04, and @narcelio's solution works.

[vamcs]

Adding ibus-daemon to startup apps as @aldonogueira said on Elementary OS Loki worked for me.

[hearues-zueke-github]

Also this link helped me for the same problem:
https://askubuntu.com/questions/135548/how-to-add-ibus-to-start-up-applications
As @vamcs and @aldonogueira said before me.

[jjchico]

Same problem with telegram desktop 1.1.23 from the Ubuntu 16.04 snap repository (telegram-sergiusens).
None of the workarounds above work, IM is set to ibus and ibus-daemon is running.

[athosmoreno]

Still reproducible on Telegram Desktop 1.2.6 with Ubuntu 16.04.4. Installed via snap.

[edevil]

Still reproducible on Telegram Desktop 1.2.15 with Ubuntu 17.10.

Installed via Snap.

[athosmoreno]

@edevil try the normal build, for some reason the snap one still has this bug

[adialaleal]

Worked at Ubuntu 17.10.
If you install the Telegram Desktop from the Ubuntu Store the dead keys will not work.
But if you download the app from Telegram's site, will be work naturally!

[Igetin]

Just chiming in here: dead keys aren't working for me on the latest Telegram Desktop (1.2.17), on Ubuntu 16.04. I'm using fcitx as my input method, but the problem didn't disappear when I tried ibus and xim. The problem exists in all of my other QT applications as well.

[john-preston]

@Igetin There is some envvar for that? QT_IM_something?

[Igetin]

@john-preston QT_IM_MODULE, as @narcelio mentioned.

[john-preston]

@Igetin So it doesn’t work with it as well? In any of Qt apps?

[Igetin]

@john-preston That's right.

[sjmuniz]

Telegram 1.4.3
I've created a shell script to start telegram:

$ cat bin/telegram.sh 
export QT_IM_MODULE=xim
cd $HOME/Downloads/Telegram
./Telegram &

I am using US international with deade keys.
However it is odd that even when I have no IM method configured, and defaults to XIM, I need to pass this variable in order to inform QT I am using XIM.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.5 LTS
Release:    16.04
Codename:   xenial
using 
$ cat ~/.xinputrc
# im-config(8) generated on Mon, 26 Feb 2018 03:55:41 -0300
run_im none
# im-config signature: 047389d2485e586bf71ebb0c8d18fa12  -
smuniz@d630:~/Downloads/Telegram$ im-config -l
 xim
smuniz@d630:~/Downloads/Telegram$ im-config -m
default
none
none

none

Regards.

[g-bougard]

This problem just appeared to me on v1.4.3 after an Ubuntu upgrade from 12.04 to 16.04.
The QT_IM_MODULE=xim trick fixes the problem.

[KlausDevWalker]

Problem still present on version 1.6.0 installed through Snap on Kubuntu 18.10 KDE Plasma version. I have the vague impression that if I'd use the repository version, this bug will disappear. But it is not in the latest version though...

[mazulo]

I was having this issue and tried a LOT of things, like rebuild my locale, running with QT_IM_MODULE=xim, installing ibus and making some adjustments to its preferences, install the official package from telegram.org but nothing worked. I was still getting these weird chars instead of accents:

it was supposed to be: e num é que é memo

By the end what solved, for whatever reason, was to uninstall the package (installed by yay -S telegram-desktop-bin) and install again with sudo pacman -S telegram-desktop

[ralesk]

@mazulo out of curiosity, what was your locale when the � characters appear? I'm willing to bet something non-UTF-8, and that's weird in these days.

[fernandoval]

I did solve the problem editing the .desktop launcher and adding the environment variable before the program name in the Exec entry like this:

Exec=env QT_IM_MODULE=xim /home/fernando/Telegram/Telegram -- %u

[kaasknak]

I have a similar problem on ubuntu mate 18.04.
I have tried reinstalling from the website and reinstalling from the repos. Both don´t fix the situation. Just a bit ago it was working on the repo version but not the website version and then when I logged out and in again it was no longer working again.

EDIT: It seems that completely purging the website´s version and then reinstalling from the repos works. This does mean that I am many versions behind now though.
@fernandoval ´s solution did not work for me. It just fails to start then.

[brunodantas]

This just started happening today on Ubuntu 19.04.
@fernandoval's solution fixed it for me.

[filippobistaffa]

Same as @brunodantas, this bug re-appeared mysteriously today.
@fernandoval's solution confirmed to work smoothly.

[gmolledaj]

LinuxMint 19.2 Tina (Ubuntu 18.04)
dead key no trabaja, ne funkcias, don't work
remap keys ALT GR + ĉ,ĝ,ĥ,ĵ,ŝ,ŭ esperanto keys : ALT GR A,E,I,O : áéíó spanish keys
xmodmap -pke > $HOME/.xmodmap
cambiar, ŝanĝi, change:
keycode 26 = e E e E U00E9 U00C9 EuroSign
keycode 30 = u U u U U016D U016C U016D
keycode 31 = i I i I U00ED U00CD rightarrow
keycode 32 = o O o O U00F3 U00D3 oslash
keycode 38 = a A a A U00E1 U00C1 ae
keycode 39 = s S s S U015D U015C ssharp
keycode 42 = g G g G U011D U011C eng
keycode 43 = h H h H U0125 U0124 hstroke
keycode 44 = j J j J U0135 U0134 dead_hook
keycode 54 = c C c C U0109 U0108 cent
xmodmap ~/.xmodmap
Telegram

[teo1978]

This shitty bug appeared on my Telegram Desktop a few weeks ago (for the first time ever) on Ubuntu 16.04 (I've had Telegram Desktop installed on this computer for years, on the same Ubuntu 16.04 for years, and I did nothing other than get the automatic updates of the OS and those of Telegram).

Right now Telegram was updated to 1.8.11, and I have tested and it works as expected again.

I don't know whether you have finally fixed it after four fucking years, or if the issue just comes and goes randomly, or if it is triggered by something that has changed in some OS component that got udated.

[KlausDevWalker]

@teo1978 are you using Snap? This is a common problem in this version of Telegram. Try to use something from the official repos or try Telegreat.

[gmolledaj]

Now it works. The problem came with update package ibus and leaved with other update of package ibus. All right.

[Aokromes]

so, this was external bug and not telegram?

[ralesk]

It stopped working for me a few days ago, and no QT_IM_MODULE change fixes it (ibus or xim, it just doesn't work) — and Telegram is the only application doing this and I'm not really sure what broke. It's really quite strange that Telegram is so sensitive to this.

I notice that KDE applications stopped displaying the ⎄ and the underlined u character (during composition and Unicode insertion respectively), but they actually do the deed, just not as visibly as before. Telegram just straight up ignores everything to do with my IME now, and GTK apps seem perfectly content about IBus.

[teo1978]

so, this was external bug and not telegram?

That seems unlikely. I have never seen the issue on a single other application in my entire life.

I can't rule out completely that it's an external bug that only affects Telegram, but it seems more likely a Telegram bug that's triggered maybe by some external factor and/or bug.

[Aokromes]

so, this was external bug and not telegram?

That seems unlikely. I have never seen the issue on a single other application in my entire life.

I can't rule out completely that it's an external bug that only affects Telegram, but it seems more likely a Telegram bug that's triggered maybe by some external factor and/or bug.

well, if you don't updated telegram and it's fixed it's clear the bug was external, maybe no one using telegram used other affected applications :)

[gmolledaj]

1.- Telegram did not work
2.- Update ibus package and other as ibus-gtk3
3.- I view the update and reinit session for load changes in user session.
4.- Telegram works.
OS: LinuxMint 19 XFCE (Ubuntu 18.04)

[ralesk]

It stopped working for me a few days ago, and no QT_IM_MODULE change fixes it (ibus or xim, it just doesn't work) — and Telegram is the only application doing this and I'm not really sure what broke. It's really quite strange that Telegram is so sensitive to this.

I notice that KDE applications stopped displaying the ⎄ and the underlined u character (during composition and Unicode insertion respectively), but they actually _do_ the deed, just not as visibly as before. Telegram just straight up ignores everything to do with my IME now, and GTK apps seem perfectly content about IBus.

Okay, I eventually had further looks into it and it was all of my Qt/KDE not using IBus at the time. Konsole – for example – however did follow my normal keyboard's compose key (which Telegram didn't), and that part worked, which is what confused me. IME didn't work. I rebooted several times and no changes to the settings did anything... And then I booted today and it's back and functional in Konsole at least (compose letter appears, IME works, dead keys do their thing), and now Telegram still doesn't work.

This is amazingly finicky. And annoying.

[gmolledaj]

In my case, I think I remember that in the configuration (Linux Mint control panel) I did not specify whether ibus or xim, it was blank. When ibus was updated I checked the settings and chose ibus for keyboard operation, then I rebooted session and it worked. You can see if you have ibus selected in the keyboard settings.

[teo1978]

well, if you don't updated telegram and it's fixed it's clear the bug was external,

No it's not (unless by "it's clear" you mean "it makes you suspect"). It might be that the condition that triggers the bug went away.

Besides, I did update telegram (well it got updated automatically but that's when I observed the issue disappeared)

I'm not saying it must be a telegram bug, but given it's the only application that has ever been reported to be affected that we know of so far, it seems the most likely culprit.

[ralesk]

Environment context for my comments: I'm using MATE on Fedora (29 currently), and its keyboard settings have been set to ibus since forever and my env always contains the QT_IM_MODULE=ibus variable. IBus's IME and composition and whatnot works perfectly on any non-Qt application.

[teo1978]

@KlausDevWalker

@teo1978 are you using Snap? This is a common problem in this version of Telegram. Try to use something from the official repos or try Telegreat.

I don't think so, I don't know what Snap is. I got it from here:
https://desktop.telegram.org/

I hope that's the official version, otherwise it's pretty well disguised.

[kaasknak]

@KlausDevWalker

@teo1978 are you using Snap? This is a common problem in this version of Telegram. Try to use something from the official repos or try Telegreat.

I don't think so, I don't know what Snap is. I got it from here:
https://desktop.telegram.org/

I hope that's the official version, otherwise it's pretty well disguised.

That is indeed the official link and also where I experience the problem. Using the ubuntu 18.04 repo I get a very dated version but it does not have the problem with the keys.

[KlausDevWalker]

@teo1978

I don't think so, I don't know what Snap is. I got it from here:
https://desktop.telegram.org/

I hope that's the official version, otherwise it's pretty well disguised.

Snaps are official too, but they cause a lot of permission misbehaviours on system. So I keep them away. :)

[rolivegab]

i'm having that bug too, accents doesn't work, characters like "áéíóúãẽĩõũç"

using fedora 30, and snap version of telegram
ibus version 1.5.20-5

UPDATE: ç works, but the rest, no

i can't even write symbols like "~", or "`", or "´", or "^"

[edio]

FWIW, here are steps that are 100% reproducible for me. Hopefully this will help tracking down the issue

Case 1

1. Open telegram with any chat
2. Type known compose sequence, f.ex. <compose>'o to get ó
   ✔ It works, ó is typed

Case 2

1. Open telegram with any chat having previous messages
2. Right click on any message form history and select _Reply_
3. Type known compose sequence, f.ex. <compose>'o to get ó
   ✘ It doesn't work, 'o is typed instead

Case 3

1. Open telegram with any chat having previous messages
2. Right click on any message form history and select _Reply_
3. Type known compose sequence, f.ex. <compose>'o to get ó
   ✘ It doesn't work, 'o is typed instead
4. Switch to any other window and then back to telegram
5. Type known compose sequence, f.ex. <compose>'o to get ó
   ✔ It works, ó is typed

So for me the issue happens only when _Reply_ feature is used. Similar _Forward_ feature doesn't have the bug.

[teo1978]

Not for me. When I was observing the issue, it would happen always, not only when using Reply.
Now I'm not observing it anymore.

[anarcobuda]

@narcelio's solution works in Xubuntu 16.04.

Had to write the command as env QT_IM_MODULE=xim /opt/telegram/Telegram in my launcher, although.

Works like beautiful magic, thank you very much wizards!

[rolivegab]

here solved by installing through dnf rpm-fusion repo

>

[ravanscafi]

I'm still experiencing the issue using the snap version. (just in case someone is tracking it)

[gchaincl]

I have the same problem than @edio

[amd77]

Happened today with Debian 10. Ibus 1.5.19. Its like magic... only in Telegram window. QT_IM_MODULE=xim fix works. This is a useful tip if you dont want to apply it:

In my keyboard layout (us international with dead keys), i can type 'é' using dead key ''' and next pressing 'e'. And also using ALTGr+e.

ALTGr+e works while dead key not.

[danilocesar]

Same here.

Looks like settings the keyboard to anything with Dead Keys triggers the problem. Like Brazilian Portuguese or English with Dead Keys.

Currently using Fedora 30 and ibus 1.5.20-5.fc30

[jayypluss]

I'm experiencing the same problem as @rolivegab.
QT_IM_MODULE=xim /usr/bin/telegram-desktop doesn't fix it for me.
Output for QT_IM_MODULE=xim /usr/bin/telegram-desktop --debug is:

➜  ~ QT_IM_MODULE=xim /usr/bin/telegram-desktop --debug
QApplication: invalid style override passed, ignoring it.
    Available styles: dsemilight, dsemidark, dlight, ddark, Windows, Fusion
qt.xkb.compose: failed to create compose table

System info (using _screenfetch_):

                   -`                 
                  .o+`                 user@user
                 `ooo/                 OS: Arch Linux 
                `+oooo:                Kernel: x86_64 Linux 5.2.14-arch2-1-ARCH
               `+oooooo:               Uptime: 1h 8m
               -+oooooo+:              Packages: 1311
             `/:-:++oooo+:             Shell: zsh 5.7.1
            `/++++/+++++++:            Resolution: 1920x1848
           `/++++++++++++++:           DE: Cinnamon 4.2.4
          `/+++ooooooooooooo/`         WM: Muffin
         ./ooosssso++osssssso+`        WM Theme: Numix-Cinnamon-Transparent (Numix-Frost-Light)
        .oossssso-````/ossssss+`       GTK Theme: Numix-Frost-Light [GTK2/3]
       -osssssso.      :ssssssso.      Icon Theme: Flat-Remix-Blue-Dark
      :osssssss/        osssso+++.     Font: Sans 9
     /ossssssss/        +ssssooo/-     CPU: Intel Core i7-7500U @ 4x 3.5GHz [25.0°C]
   `/ossssso+/:-        -:/+osssso+-   GPU: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) 
  `+sso+:-`                 `.-/+oso:  RAM: 3448MiB / 7854MiB
 `++:.                           `-/+/
 .`                                 `/

[ribeirobreno]

This bug happens 100% of the time (any input field, chat, ... and no need to alt+tab or do anything) for me at Ubuntu Xenial with XFCE and ABNT2 keyboard.
Two workarounds work here:

• QT_IM_MODULE=xim /path/to/telegram mentioned above
• writing the text in other applications and copying it to telegram.

[ghost]

Fedora 31 wtih 3.34.1 happens this issue, I cannot put accents in Spanish.

[nunesgh]

I came here thinking I was going to report something new, but this issue has been around since 2015! Wow!

[fccoelho]

For me what worked was to remove the Snap installation and installing from apt

snap remove telegram-desktop
apt install telegram-desktop

[gsilvapt]

Still happens in Ubuntu 19.04 and 19.10. The solution is to not use the snap and install via the binaries from their website (Telegram has simple instructions, so it shouldn't be hard even for people not used to the terminal.

[zoltanp]

I'm having this issue on Linux (Xubuntu 18.04, Telegram v 1.9.7, keyboard layout US International with AltGr dead keys).

After starting the system and starting Telegram, key combinations like AltGr + e (=é) work, but key combinations like AltGr+Shift+2,o = (ő) do not.

However, after pasting text containing the ő character into the message input in Telegram, the key combinations like AltGr+Shift+2,o start working, and continue to work even after restarting Telegram.

[joaquinferrero]

I have the same problem in Ubuntu 14.10.

Same problem with Linux Mint 17.3

[nunesgh]

@auchri doesn't this issue deserve a "bug" tag?

[shoorick]

Compose key doesn’t work as expected: it gives ⁈ character immediately then ignore sequence rules and print following characters as is.
Example: sequence Compose, ', a shown as á in other apps and as ⁈'a in Telegram.

env QT_IM_MODULE=xim telegram-desktop doesn’t help.

Debian 10, telegram-desktop 1.5.11-1.

MuseScore which uses QT, have the same issue.

[joaquinferrero]

I have the same problem in Ubuntu 14.10.

Same problem with Linux Mint 17.3

The fix

env QT_IM_MODULE=xim /path/to/Telegram

works!

[nunesgh]

Workaround: call with QT_IM_MODULE=xim /opt/telegram/Telegram

Does not work on KDE neon 5.18 User Edition.

Default command was env BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/telegram-desktop_telegram-desktop.desktop /snap/bin/telegram-desktop -- %u

I use a Brazilian Portuguese keyboard and I can type the ç character, but no accented letters.

[ravanscafi]

This workaround worked until a few versions ago. Using "source A" or "source B" to install the client is not a real solution too, because you are simply getting an old version, where it used to work.

The problem is that on newer versions of the client, this issue happens and there is NO solution till this day.

[php4fan]

The problem is that on newer versions of the client, this issue happens

That's funny because I had the issue for a "brief" period (meaning an awfully long period of several weeks if not months) long ago, and then it got fixed with some automatic update (I never did anything about it) and I've never had it again.

[ilya-fedin]

because you are simply getting an old version

No, it is deeper. When you're installing a version from system repositories, it uses system Qt and can use system Qt's integration plugins, including platforminputcontext. The static version from official site or github releases can't use these plugins. Snaps and fllatpaks have a predefined set of Qt plugins in itself (telegram-desktop snap has been reworked some time ago, you can check if this is fixed on it).

So, for anyone who uses some input engines or other external things to type, the only option is to use distribution package.

[EdnilsonRobert]

For me what worked was to remove the Snap installation and installing from apt

snap remove telegram-desktop
apt install telegram-desktop

Works like a charm.

[nunesgh]

For me what worked was to remove the Snap installation and installing from apt

snap remove telegram-desktop
apt install telegram-desktop

But the feature gap between the snap and the apt releases is huge, isn't it? The snap version is currently 2.0.1 while the apt version is still 1.2.17-1.

[Aokromes]

For me what worked was to remove the Snap installation and installing from apt

snap remove telegram-desktop
apt install telegram-desktop

But the feature gap between the snap and the apt releases is huge, isn't it? The snap version is currently 2.0.1 while the apt version is still 1.2.17-1.

download telegram from desktop.telegram.org or github->releases.

[ilya-fedin]

There are flatpak version also

[ilya-fedin]

Snap was transferred to kde-neon extension as a base with Qt 5.12.3 instead of 5.9.
Maybe something is changed?

[jayypluss]

I use Arch Linux and I have uninstalled the community/telegram-desktop package from pacman that I was using before and installed the latest x64 binary downloaded from this git project.
Now it works.

[gsilvapt]

Yes, that has been the deal all along. If you install the binaries (either from GitHub or from the website), they work. Snaps or repository, do not. Not sure about flatpak, never tried that one.

[nunesgh]

I am currently using the flatpak version and this issue is not present there.

[herzenschein]

For those people whose workaround QT_IM_MODULE=xim telegram does not work, or for those who use Telegram on Wayland, could you try the following and report whether this works?
XCOMPOSEFILE=/usr/share/X11/locale/$LANG/Compose telegram

[xthiago]

For those people whose workaround QT_IM_MODULE=xim telegram does not work, or for those who use Telegram on Wayland, could you try the following and report whether this works?
XCOMPOSEFILE=/usr/share/X11/locale/$LANG/Compose telegram

XCOMPOSEFILE=/usr/share/X11/locale/$LANG/Compose telegram-desktop

It did not work on Ubuntu 20.04.

[ilya-fedin]

It did not work on Ubuntu 20.04.

pls specify installation method

[xthiago]

It did not work on Ubuntu 20.04.

pls specify installation method

Using snap (snap install telegram-desktop).

To get accents to work properly I removed it (snap install telegram-desktop) and installed it manually (downloading the binary from telegram.org and putting it on /opt).

[ilya-fedin]

Do you use ibus?

[xthiago]

I don't know. I have the default distribution of Ubuntu 20.04 without relevant customizations.

Should I install it manually?

[ilya-fedin]

I don't know.

echo $QT_IM_MODULE

Should I install it manually?

No

[ilya-fedin]

Everyone who affected by this issue, please, test version 2.1.11-1-ge009ac026 on the edge channel

snap refresh --edge telegram-desktop

[ilya-fedin]

Anyone? :thinking:

[Nottt]

that fixed it for me @ilya-fedin can't believe this bug is from 2015!

[ilya-fedin]

Wow

[ilya-fedin]

The fix in 2.1.12
If no one says that the issue still valid in 7 days, the issue will be closed

[joaquinferrero]

Linux Mint 17.3 Rosa : Fail
Workaround (at first glance) with QT_IM_MODULE=xim

[ilya-fedin]

Linux Mint 17.3 Rosa : Fail

How did you install tdesktop?

[joaquinferrero]

Linux Mint 17.3 Rosa : Fail

How did you install tdesktop?

Humm... Updated from the program itself and it failed.

I tried now the desktop.telegram.org version and for now it is working.

Edit: After leaving the computer one night in "sleep" mode, this morning the Telegram Desktop has started to fail to write accented text. Restarting the application works again, but it fails on the next on-screen application change (Alt-Tab).

[ilya-fedin]

Restarting the application works again, but it fails on the next on-screen application change (Alt-Tab).

Well, looks like this bug has multiple causes
And I fixed only one of them

But I need more info about your system to try to reproduce that (distro name, distro version, DE name, DE version, echo $QT_IM_MODULE (without QT_IM_MODULE=xim)

[joaquinferrero]

Description: Linux Mint 17.3 Rosa
echo $QT_IM_MODULE: ibus

[ilya-fedin]

Description: Linux Mint 17.3 Rosa

DE?..

[joaquinferrero]

KDE 4:4.14.2-0ubuntu1~ubuntu14.04~ppa1

[ilya-fedin]

KDE 4:4.14.2-0ubuntu1~ubuntu14.04~ppa1

Could you tell how you configured the compose key in ibus and with which language you using this key? (i never used compose key feature before)

[herzenschein]

Possibly related: https://bugs.kde.org/show_bug.cgi?id=411729

[ilya-fedin]

As you can see, Telegram is stated as working, that's due to the backported fix for ibus on wayland from Qt dev branch: https://github.com/desktop-app/patches/blob/master/qtbase_5_12_8/0025-fix-ibus-on-wayland.patch

But that thing would work only with static binary, since it is impossible to control how Qt is built with other ways of distribution (snap, flatpak, packages in distro repositories)

That Qt bug was discussed there: https://github.com/telegramdesktop/tdesktop/issues/2013#issuecomment-614030382

[ilya-fedin]

And there are no need in XCOMPOSEFILE, since libxkbcommon is built with the right path now: https://github.com/telegramdesktop/tdesktop/blob/0b939e72c1305d96727c84d1b4a4978dfe43ea43/.github/workflows/linux.yml#L406-L407

[ilya-fedin]

Well, I found that Qt bug report: https://bugreports.qt.io/browse/QTBUG-44847
But I have a feel that this bug is reproducible only on old systems and the bug is in old system libraries actually rather than in Qt :thinking:

[ilya-fedin]

It would be very helpful if someone who experience the problem with losing of accent letters after focus change (note: when you opening a context menu, it's actually a separate window and focus changes) test the issue with other Qt applications on the same system (e.g. qbittorent, vlc, etc)

[joaquinferrero]

I usually leave the computer in "sleep" mode at night. Some days, when waking up the computer, I have noticed that some applications, like the Mozilla Thunderbird, lose the ability to write with accents. In that case, I switch to another application, for example Kate, or the same Telegram (started with the workaround), and when I return to edit the mail message it already works well. Other days, I don't notice any problems in any application.

[ilya-fedin]

I don't notice any problems in any application.

That might be just because you aren't using any other Qt applications or use them not so intensive. I saw a lot of issues where people say "I saw this problem only with telegram", but after testing with qbittorrent/vlc they confirm that they can reproduce the issue with these apps.

[ilya-fedin]

Just checked Ubuntu 14.04 repositories (I assume that's the base of Linux Mint 17.3) and found that almost all Qt apps are using Qt4 (VLC, qBittorrent, Kate). That explains why you can't reproduce even with Kate. But then I don't know which app suggest you to test.
I suggest to update your OS.

[teo1978]

I have just started observing the issue again.

I'm using my laptop's built-in keyboard now, while I usually use an external one (which I don't have at hand right now).

So either:

• the issue was fixed (except for Snap, whatever that is) and now has regressed
• the issue affects different physical keyboards differently

And also:

• right while I was reporting this I went back to the very chat where I was observing the issue, tried typing an accented character, and it worked. So it's also random. Like, you may be observing the issue, then switch focus forth and back to/from different windows, maybe use the keyboard with them, then go back to Telegram and it might start working.

This whole thing is f@ing pathetic. The issue was first reported five f@ing years ago.

[ilya-fedin]

except for Snap, whatever that is

it is fixed in snap, by adding ibus-daemon binary

[ilya-fedin]

The issue was first reported five f@ing years ago.

No one can fix the issue if no one knows why it's happening :see_no_evil:

[BondarenkoArtur]

I've same issue...
Seems ralt works as tab or something like that, because it insert big space when I'm pressing it.
It types oC instead of ℃
$ printf " oC" | hexdump -C
00000000 09 6f 43 |.oC|
calling QT_IM_MODULE=xim telegram-desktop not fixing issue for me

OS: Manjaro 20.0.3 Lysia
Kernel: x86_64 Linux 4.19.133-1-MANJARO

Telegram Desktop Version 2.2 AUR telegram-desktop-bin

[ilya-fedin]

Seems ralt works as tab or something like that

What do you mean by "ralt"? Did you set ralt as a compose key or just trying to use it with out-of-the-box settings? AFAIK manjaro doesn't use ralt out-of-the-box for anything, at least with Qt apps.

[BondarenkoArtur]

ralt is Compose Key
Here is line from my xorg config
Option "XkbOptions" "grp:caps_toggle,grp_led:caps,compose:ralt"

This strange behavior appears only in telegram…

[ilya-fedin]

This strange behavior appears only in telegram…

Are you sure that other Qt applications aren't affected? vlc, qbittorrent...

[BondarenkoArtur]

VLC works fine

qbittorrent also fine

[ilya-fedin]

echo $QT_IM_MODULE

[BondarenkoArtur]

echo $QT_IM_MODULE

Empty. Nothing there

[ilya-fedin]

I have no idea, sorry :man_shrugging:

[BondarenkoArtur]

Package from here
https://aur.archlinux.org/packages/telegram-desktop-bin

[ilya-fedin]

Package from here

Started my VM with Manjaro XFCE, updated to the latest packages, executed setxkbmap -layout us,ru -option grp:caps_toggle,grp_led:caps,compose:ralt, started tdesktop 2.2 downloaded from desktop.telegram.org, opened some chat, clicked on the input field, pushed ralt, typed o, c - got copyright symbol.

[BondarenkoArtur]

Don't know what changed, but now it works, thanks :)

[Woundorf]

I can now type accentuated letters without the env QT_IM_MODULE=xim trick from one of the other tickets. But I have a local passcode and since recently (few weeks, the last month at most) I can't type accentuated letters there, with or without the previous trick. The only way to unlock Telegram now is to copy the password from another place and then paste it into the password field.

System: Fedora 32, GNOME 3.36.6, X11.

[ilya-fedin]

But I have a local passcode and since recently (few weeks, the last month at most) I can't type accentuated letters there, with or without the previous trick.

If your system uses ibus, it's by design.