New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Graphic accents in vocals (èéàú...) do not appear #1360

Closed
plagasul opened this Issue Dec 3, 2015 · 60 comments

Comments

Projects
None yet
@plagasul

plagasul commented Dec 3, 2015

I am on Telegram Desktop 0.9.10 under Linux Mint 17.2 Rafaela Cinnamon

Spanish/catalan graphic accents on vocals, such as é è ú.... but also ü, etc, are simply not written when writing a message. They are not shown on text input, and neither when the message is sent and appears in the shared part of the screen.

Graphic accents work without any problem in any other part of the system, without exceptions, at least that I come accross.

Thank you

@auchri auchri added the linux label Dec 3, 2015

@auchri

This comment has been minimized.

Show comment
Hide comment
@auchri

auchri Dec 3, 2015

Member

Works on windows
image

Member

auchri commented Dec 3, 2015

Works on windows
image

@z3ntu

This comment has been minimized.

Show comment
Hide comment
@z3ntu

z3ntu Dec 8, 2015

selection_010
Works in Ubuntu 15.10

z3ntu commented Dec 8, 2015

selection_010
Works in Ubuntu 15.10

@psergiojr

This comment has been minimized.

Show comment
Hide comment
@psergiojr

psergiojr Dec 22, 2015

Here on Telegram 0.9.15 under Ubuntu 14.04 LTS

I've noticed this too. But it only happens after some time. Right after opening the window, it works perfectly. I keep it opened while doing anything else with another program, and then back to the Telegram window, accents do not appear anymore.

If I close the window, then reopen it from the tray icon, it still doesn't work. But if I change the keyboard layout to any other language (here between pt-BR and en-US) and then back, it works again. Just to stop working again after some time :)

psergiojr commented Dec 22, 2015

Here on Telegram 0.9.15 under Ubuntu 14.04 LTS

I've noticed this too. But it only happens after some time. Right after opening the window, it works perfectly. I keep it opened while doing anything else with another program, and then back to the Telegram window, accents do not appear anymore.

If I close the window, then reopen it from the tray icon, it still doesn't work. But if I change the keyboard layout to any other language (here between pt-BR and en-US) and then back, it works again. Just to stop working again after some time :)

@psergiojr

This comment has been minimized.

Show comment
Hide comment
@psergiojr

psergiojr Dec 22, 2015

Testing now, I found something strange. When switching between windows using the mouse, it works perfectly. But when switching using Alt+Tab the accents stop working.

psergiojr commented Dec 22, 2015

Testing now, I found something strange. When switching between windows using the mouse, it works perfectly. But when switching using Alt+Tab the accents stop working.

@psergiojr

This comment has been minimized.

Show comment
Hide comment
@psergiojr

psergiojr Jan 16, 2016

If it helps tracking the problem: I was testing in Manjaro, and the problem doesn't happen here. Even the Alt+Tab works fine with accents. XFCE 4.12

Maybe it's like #1041

psergiojr commented Jan 16, 2016

If it helps tracking the problem: I was testing in Manjaro, and the problem doesn't happen here. Even the Alt+Tab works fine with accents. XFCE 4.12

Maybe it's like #1041

@Crashillo

This comment has been minimized.

Show comment
Hide comment
@Crashillo

Crashillo May 22, 2016

Problem persists. Telegram just ignores accent keys.
xfce4-about 4.11.1 (Xfce 4.10)
VERSION="14.04.4 LTS, Trusty Tahr"
Telegram Desktop: v 0.9.49

UPDATE The same at my working computer:
xfce4-about 4.12.1 (Xfce 4.12)
VERSION="16.04 LTS (Xenial Xerus)"
Telegram Desktop: v 0.9.49

Crashillo commented May 22, 2016

Problem persists. Telegram just ignores accent keys.
xfce4-about 4.11.1 (Xfce 4.10)
VERSION="14.04.4 LTS, Trusty Tahr"
Telegram Desktop: v 0.9.49

UPDATE The same at my working computer:
xfce4-about 4.12.1 (Xfce 4.12)
VERSION="16.04 LTS (Xenial Xerus)"
Telegram Desktop: v 0.9.49

@Contraculto

This comment has been minimized.

Show comment
Hide comment
@Contraculto

Contraculto Jun 6, 2016

I also have this problem.
In XFCE 4.12 over Ubuntu 16.04 accented characters don't work, they're simply ignored.
It works perfectly if I switch to Gnome.
Telegram version is 0.9.49, but I have at least a few times in the last couple of weeks.

Contraculto commented Jun 6, 2016

I also have this problem.
In XFCE 4.12 over Ubuntu 16.04 accented characters don't work, they're simply ignored.
It works perfectly if I switch to Gnome.
Telegram version is 0.9.49, but I have at least a few times in the last couple of weeks.

@z3ntu

This comment has been minimized.

Show comment
Hide comment
@z3ntu

z3ntu Jun 6, 2016

Happened on:
XFCE (Ubuntu 16.04, Ubuntu 14.04)
Unity (Ubuntu 16.04)
Cinnamon (Mint)

Did NOT happen on:
XFCE (Manjaro)
GNOME (Ubuntu 16.04)
Unity (Ubuntu 15.10)
i3 (Arch Linux)

z3ntu commented Jun 6, 2016

Happened on:
XFCE (Ubuntu 16.04, Ubuntu 14.04)
Unity (Ubuntu 16.04)
Cinnamon (Mint)

Did NOT happen on:
XFCE (Manjaro)
GNOME (Ubuntu 16.04)
Unity (Ubuntu 15.10)
i3 (Arch Linux)

@Rom4nB

This comment has been minimized.

Show comment
Hide comment
@Rom4nB

Rom4nB Jun 7, 2016

Same behaviour here. Any dead keys, i.e. accents as well, don't work on Telegram Desktop.

Operating System
Ubuntu 16.04 64-bit

Telegram Desktop Version
0.9.49

Rom4nB commented Jun 7, 2016

Same behaviour here. Any dead keys, i.e. accents as well, don't work on Telegram Desktop.

Operating System
Ubuntu 16.04 64-bit

Telegram Desktop Version
0.9.49

@z3ntu

This comment has been minimized.

Show comment
Hide comment
@z3ntu

z3ntu Jun 7, 2016

@Rom4nB what Desktop environment are you using?

z3ntu commented Jun 7, 2016

@Rom4nB what Desktop environment are you using?

@Rom4nB

This comment has been minimized.

Show comment
Hide comment
@Rom4nB

Rom4nB Jun 7, 2016

@z3ntu I use the standard Unity 7 Desktop environment of Ubuntu 16.04.

Unity Version 7.4.0

Rom4nB commented Jun 7, 2016

@z3ntu I use the standard Unity 7 Desktop environment of Ubuntu 16.04.

Unity Version 7.4.0

@z3ntu

This comment has been minimized.

Show comment
Hide comment
@z3ntu

z3ntu Jun 7, 2016

@auchri @john-preston I compiled a list where it worked and where it didn't: #1360 (comment)

z3ntu commented Jun 7, 2016

@auchri @john-preston I compiled a list where it worked and where it didn't: #1360 (comment)

@soadroxs

This comment has been minimized.

Show comment
Hide comment
@soadroxs

soadroxs Jun 9, 2016

Not working here either.

XFCE 4.12
Xubuntu 16.04
Telegram 0.9.51

EDIT
Layout:

rules: evdev
model: pc105
layout: pt

soadroxs commented Jun 9, 2016

Not working here either.

XFCE 4.12
Xubuntu 16.04
Telegram 0.9.51

EDIT
Layout:

rules: evdev
model: pc105
layout: pt

@Patola

This comment has been minimized.

Show comment
Hide comment
@Patola

Patola Jun 10, 2016

Working in one computer (Ubuntu 16.04 64 bits with NVidia and Unity), not working in another (same configuration). First computer uses abnt2 brazilian portuguese layout for accents, second one does not. Tested in both with dead keys and non-dead keys (composed letters), same thing, in the first one it works, in the second it does not.

Telegram version: 0.9.49

Patola commented Jun 10, 2016

Working in one computer (Ubuntu 16.04 64 bits with NVidia and Unity), not working in another (same configuration). First computer uses abnt2 brazilian portuguese layout for accents, second one does not. Tested in both with dead keys and non-dead keys (composed letters), same thing, in the first one it works, in the second it does not.

Telegram version: 0.9.49

@luccamendonca

This comment has been minimized.

Show comment
Hide comment
@luccamendonca

luccamendonca Jun 15, 2016

Doesn't work here either

XFCE 4.1
Xubuntu 15.10
Linux 4.4.4-040404-generic
Telegram 0.9.51

[EDIT]

Keyboard layout: PT-BR (ABNT2)

luccamendonca commented Jun 15, 2016

Doesn't work here either

XFCE 4.1
Xubuntu 15.10
Linux 4.4.4-040404-generic
Telegram 0.9.51

[EDIT]

Keyboard layout: PT-BR (ABNT2)

@rcotrina94

This comment has been minimized.

Show comment
Hide comment
@rcotrina94

rcotrina94 Jun 15, 2016

+1 Doesn't work here either

GNOME Shell 3.16.4
Ubuntu GNOME 15.10
GNU/Linux 4.2.0-36-generic
Telegram 0.9.51

[EDIT]

$ setxkbmap -query
rules:      evdev
model:      pc105
layout:     latam,us
variant:    ,

rcotrina94 commented Jun 15, 2016

+1 Doesn't work here either

GNOME Shell 3.16.4
Ubuntu GNOME 15.10
GNU/Linux 4.2.0-36-generic
Telegram 0.9.51

[EDIT]

$ setxkbmap -query
rules:      evdev
model:      pc105
layout:     latam,us
variant:    ,

@telegramdesktop telegramdesktop locked and limited conversation to collaborators Jun 15, 2016

@telegramdesktop telegramdesktop unlocked this conversation Jun 15, 2016

@z3ntu

This comment has been minimized.

Show comment
Hide comment
@z3ntu

z3ntu Jun 16, 2016

PLEASE! If you write, that it doesn't work for you, please also write what keyboard layout you are using! I am pretty sure, that it isn't because of a desktop environment/window manager, but because of the "special" keyboard layout you are using.

z3ntu commented Jun 16, 2016

PLEASE! If you write, that it doesn't work for you, please also write what keyboard layout you are using! I am pretty sure, that it isn't because of a desktop environment/window manager, but because of the "special" keyboard layout you are using.

@ByScripts

This comment has been minimized.

Show comment
Hide comment
@ByScripts

ByScripts Jun 18, 2016

Same problem here with dead keys.

Keyboard layout: "Français (Variante)" (AZERTY)

For the moment, I don't have problem with accented letters (éàù...), only with composition (^ ¨ ...)

rules:      evdev
model:      pc105
layout:     fr,us,fr
variant:    oss,,oss

ByScripts commented Jun 18, 2016

Same problem here with dead keys.

Keyboard layout: "Français (Variante)" (AZERTY)

For the moment, I don't have problem with accented letters (éàù...), only with composition (^ ¨ ...)

rules:      evdev
model:      pc105
layout:     fr,us,fr
variant:    oss,,oss
@plagasul

This comment has been minimized.

Show comment
Hide comment
@plagasul

plagasul Jun 19, 2016

I initiated this thread, I've noticed the following message on the terminal when updating telegram that I believe may be related, at least in my case, to the problem at hand:

Configurando telegram (0.9.50-0ubuntu0) ...
Telegram/
Telegram/Updater
Telegram/Telegram
Configurando kpartx (0.4.9-3ubuntu7.13) ...
Configurando kpartx-boot (0.4.9-3ubuntu7.13) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for menu (2.1.46ubuntu1) ...
Processing triggers for initramfs-tools (0.103ubuntu4.3) ...
update-initramfs: Generating /boot/initrd.img-3.19.0-32-generic
Warning: No support for locale: es_ES.utf8

plagasul commented Jun 19, 2016

I initiated this thread, I've noticed the following message on the terminal when updating telegram that I believe may be related, at least in my case, to the problem at hand:

Configurando telegram (0.9.50-0ubuntu0) ...
Telegram/
Telegram/Updater
Telegram/Telegram
Configurando kpartx (0.4.9-3ubuntu7.13) ...
Configurando kpartx-boot (0.4.9-3ubuntu7.13) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for menu (2.1.46ubuntu1) ...
Processing triggers for initramfs-tools (0.103ubuntu4.3) ...
update-initramfs: Generating /boot/initrd.img-3.19.0-32-generic
Warning: No support for locale: es_ES.utf8

@z3ntu

This comment has been minimized.

Show comment
Hide comment
@z3ntu

z3ntu Jun 19, 2016

@plagasul is the language uncommented in your /etc/locale.conf? If not, uncomment it and run locale-gen. (I don't know if this works on Ubuntu, but it works on Arch Linux so try it)

z3ntu commented Jun 19, 2016

@plagasul is the language uncommented in your /etc/locale.conf? If not, uncomment it and run locale-gen. (I don't know if this works on Ubuntu, but it works on Arch Linux so try it)

@plagasul

This comment has been minimized.

Show comment
Hide comment
@plagasul

plagasul Jun 19, 2016

@z3ntu, there is a etc/locale.alias with a "spanish es_ES.ISO-8859-1" line, uncommented, I run locale-gen, shutdown and up Telegram, but nothing particular happened, graphic accents still not visible. Thanks. Any other ideas?

plagasul commented Jun 19, 2016

@z3ntu, there is a etc/locale.alias with a "spanish es_ES.ISO-8859-1" line, uncommented, I run locale-gen, shutdown and up Telegram, but nothing particular happened, graphic accents still not visible. Thanks. Any other ideas?

@plagasul

This comment has been minimized.

Show comment
Hide comment
@plagasul

plagasul Jun 19, 2016

I tried reinstalling telegram and got this:

perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_TIME = "es_ES.UTF-8", LC_MONETARY = "es_ES.UTF-8", LC_ADDRESS = "es_ES.UTF-8", LC_TELEPHONE = "es_ES.UTF-8", LC_NAME = "es_ES.UTF-8", LC_MEASUREMENT = "es_ES.UTF-8", LC_IDENTIFICATION = "es_ES.UTF-8", LC_NUMERIC = "es_ES.UTF-8", LC_PAPER = "es_ES.UTF-8", LANG = "es_ES.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory Selecting previously unselected package telegram. (Reading database ... 286519 files and directories currently installed.) Preparing to unpack .../telegram_0.9.50-0ubuntu0_amd64.deb ... Unpacking telegram (0.9.50-0ubuntu0) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gnome-menus (3.10.1-0ubuntu2) ... Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for mime-support (3.54ubuntu1.1) ... Setting up telegram (0.9.50-0ubuntu0) ... Telegram/ Telegram/Updater

plagasul commented Jun 19, 2016

I tried reinstalling telegram and got this:

perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_TIME = "es_ES.UTF-8", LC_MONETARY = "es_ES.UTF-8", LC_ADDRESS = "es_ES.UTF-8", LC_TELEPHONE = "es_ES.UTF-8", LC_NAME = "es_ES.UTF-8", LC_MEASUREMENT = "es_ES.UTF-8", LC_IDENTIFICATION = "es_ES.UTF-8", LC_NUMERIC = "es_ES.UTF-8", LC_PAPER = "es_ES.UTF-8", LANG = "es_ES.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory Selecting previously unselected package telegram. (Reading database ... 286519 files and directories currently installed.) Preparing to unpack .../telegram_0.9.50-0ubuntu0_amd64.deb ... Unpacking telegram (0.9.50-0ubuntu0) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gnome-menus (3.10.1-0ubuntu2) ... Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for mime-support (3.54ubuntu1.1) ... Setting up telegram (0.9.50-0ubuntu0) ... Telegram/ Telegram/Updater

@Lonami

This comment has been minimized.

Show comment
Hide comment
@Lonami

Lonami Jun 28, 2016

Contributor

Not working here either. It's strange, because in other operative systems (Linux Mint 17.3 Rosa featuring XFCE desktop) I could type on the chat input with those characters, but not on the photos. I had to use Alt+Tab.

Now under Xubuntu 16.04 with the latest Telegram version as of now (0.9.56) is still not working, anywhere. My keyboard is Generic PC 105 keys (intl), Spanish (Windows keys)

Contributor

Lonami commented Jun 28, 2016

Not working here either. It's strange, because in other operative systems (Linux Mint 17.3 Rosa featuring XFCE desktop) I could type on the chat input with those characters, but not on the photos. I had to use Alt+Tab.

Now under Xubuntu 16.04 with the latest Telegram version as of now (0.9.56) is still not working, anywhere. My keyboard is Generic PC 105 keys (intl), Spanish (Windows keys)

@john-preston

This comment has been minimized.

Show comment
Hide comment
@john-preston

john-preston Jun 28, 2016

Member

@XyLoNaMiyX Can you try in other systems (where the chat input was working, but not the photo caption input) does photo caption input now work?

Member

john-preston commented Jun 28, 2016

@XyLoNaMiyX Can you try in other systems (where the chat input was working, but not the photo caption input) does photo caption input now work?

@douglasrizzo

This comment has been minimized.

Show comment
Hide comment
@douglasrizzo

douglasrizzo Sep 16, 2016

I found out that the workaround proposed by @narcelio on #1041 (comment) works for me.

douglasrizzo commented Sep 16, 2016

I found out that the workaround proposed by @narcelio on #1041 (comment) works for me.

@brwolfgang

This comment has been minimized.

Show comment
Hide comment
@brwolfgang

brwolfgang Sep 16, 2016

@douglasrizzo works here too, I can now leave the web version alone, thanks

brwolfgang commented Sep 16, 2016

@douglasrizzo works here too, I can now leave the web version alone, thanks

@rafaelcn

This comment has been minimized.

Show comment
Hide comment
@rafaelcn

rafaelcn Sep 25, 2016

Well, I just changed the desktop that I use (to KDE), since then I have no complaints regarding telegram. Either way, as you said the problem is still not solved on Xubuntu.

Regards,
Rafael Campos Nunes.
rafaelnunes@engineer.com

Le 16 sept. 2016 à 12:23, "Douglas De Rizzo Meneghetti" notifications@github.com a écrit :

@rafaelcn my case is exactly the same as yours.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

rafaelcn commented Sep 25, 2016

Well, I just changed the desktop that I use (to KDE), since then I have no complaints regarding telegram. Either way, as you said the problem is still not solved on Xubuntu.

Regards,
Rafael Campos Nunes.
rafaelnunes@engineer.com

Le 16 sept. 2016 à 12:23, "Douglas De Rizzo Meneghetti" notifications@github.com a écrit :

@rafaelcn my case is exactly the same as yours.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@vs0uz4

This comment has been minimized.

Show comment
Hide comment
@vs0uz4

vs0uz4 Oct 18, 2016

For those who are using distros like Elementary OS, just edit the file telegramdesktop.desktop, and remove the first line of the [Desktop Entry] that setting encoding to file is UTF-8, that way here worked perfectly accents.

After some testing, I found instability in the previously presented solution, which had only remove the key "Encoding". So talking to the my friend @vinicius73 who went through the same problem accent, I took with him the adjustments he made in .desktop, which was to add the environment variable "QT_IM_MODULE" before calling the executable Telegram. Getting the telegramdestop.desktop the way described below, and solving the problem of accents without instability.

Replace "USERNAME" at login your user

[Desktop Entry]
Version=1.0
Name=Telegram Desktop
Comment=Official desktop version of Telegram messaging app
Exec=env QT_IM_MODULE=xim /home/USERNAME/Telegram/Telegram -- %u
Icon=telegram
Terminal=false
StartupWMClass=Telegram
Type=Application
Categories=Network;
MimeType=x-scheme-handler/tg;
X-Desktop-File-Install-Version=0.22

vs0uz4 commented Oct 18, 2016

For those who are using distros like Elementary OS, just edit the file telegramdesktop.desktop, and remove the first line of the [Desktop Entry] that setting encoding to file is UTF-8, that way here worked perfectly accents.

After some testing, I found instability in the previously presented solution, which had only remove the key "Encoding". So talking to the my friend @vinicius73 who went through the same problem accent, I took with him the adjustments he made in .desktop, which was to add the environment variable "QT_IM_MODULE" before calling the executable Telegram. Getting the telegramdestop.desktop the way described below, and solving the problem of accents without instability.

Replace "USERNAME" at login your user

[Desktop Entry]
Version=1.0
Name=Telegram Desktop
Comment=Official desktop version of Telegram messaging app
Exec=env QT_IM_MODULE=xim /home/USERNAME/Telegram/Telegram -- %u
Icon=telegram
Terminal=false
StartupWMClass=Telegram
Type=Application
Categories=Network;
MimeType=x-scheme-handler/tg;
X-Desktop-File-Install-Version=0.22
@luismanolo

This comment has been minimized.

Show comment
Hide comment
@luismanolo

luismanolo Nov 7, 2016

First, sorry about my english... ;-)

Thanks to @vs0uz4 for the solution, but don't work for me.

This is my modification...

create a file in /home/USERNAME/bin/TG.sh with:

#!/bin/bash
QT_IM_MODULE=xim /home/USERNAME/Telegram/Telegram

then: chmod +x /home/USERNAME/bin/TG.sh

And finally change the file: /home/USERNAME/.local/share/applications/telegramdesktop.desktop with:

[Desktop Entry]
Version=1.0
Name=Telegram Desktop
Comment=Official desktop version of Telegram messaging app
Exec=/home/USERNAME/bin/TG.sh
Icon=telegram
Terminal=false
StartupWMClass=Telegram
Type=Application
Categories=Network;
MimeType=x-scheme-handler/tg;
X-Desktop-File-Install-Version=0.22

This work for me.

luismanolo commented Nov 7, 2016

First, sorry about my english... ;-)

Thanks to @vs0uz4 for the solution, but don't work for me.

This is my modification...

create a file in /home/USERNAME/bin/TG.sh with:

#!/bin/bash
QT_IM_MODULE=xim /home/USERNAME/Telegram/Telegram

then: chmod +x /home/USERNAME/bin/TG.sh

And finally change the file: /home/USERNAME/.local/share/applications/telegramdesktop.desktop with:

[Desktop Entry]
Version=1.0
Name=Telegram Desktop
Comment=Official desktop version of Telegram messaging app
Exec=/home/USERNAME/bin/TG.sh
Icon=telegram
Terminal=false
StartupWMClass=Telegram
Type=Application
Categories=Network;
MimeType=x-scheme-handler/tg;
X-Desktop-File-Install-Version=0.22

This work for me.

@Lonami

This comment has been minimized.

Show comment
Hide comment
@Lonami

Lonami Nov 7, 2016

Contributor

Thanks @luismanolo, I was having the issue again and I didn't want to bother with ibus xD

Edit: For those who are not so much into Linux-based distributions, you don't need to actually create the TG.sh file where @luismanolo's comment says. It can even be under the same directory as telegramdesktop.desktop. And you can also replace /home/USERNAME with ~, which is shorter!

Contributor

Lonami commented Nov 7, 2016

Thanks @luismanolo, I was having the issue again and I didn't want to bother with ibus xD

Edit: For those who are not so much into Linux-based distributions, you don't need to actually create the TG.sh file where @luismanolo's comment says. It can even be under the same directory as telegramdesktop.desktop. And you can also replace /home/USERNAME with ~, which is shorter!

@stek29

This comment has been minimized.

Show comment
Hide comment
@stek29

stek29 Nov 7, 2016

Collaborator

@luismanolo @XyLoNaMiyX Why not do Exec=QT_IM_MODULE=xim /home/USERNAME/Telegram/Telegram? or with eval if it won't work.

Collaborator

stek29 commented Nov 7, 2016

@luismanolo @XyLoNaMiyX Why not do Exec=QT_IM_MODULE=xim /home/USERNAME/Telegram/Telegram? or with eval if it won't work.

@Lonami

This comment has been minimized.

Show comment
Hide comment
@Lonami

Lonami Nov 7, 2016

Contributor

@stek29 Exec=QT_IM_MODULE=xim /home/USERNAME/Telegram/Telegram fails. I don't know where to put eval, and with env it didn't work for me either.

Contributor

Lonami commented Nov 7, 2016

@stek29 Exec=QT_IM_MODULE=xim /home/USERNAME/Telegram/Telegram fails. I don't know where to put eval, and with env it didn't work for me either.

@Aokromes

This comment has been minimized.

Show comment
Hide comment
@Aokromes

Aokromes commented Nov 7, 2016

#1041 ?

@stek29

This comment has been minimized.

Show comment
Hide comment
@stek29

stek29 Nov 7, 2016

Collaborator

@XyLoNaMiyX oh, i meant env, huh.

Collaborator

stek29 commented Nov 7, 2016

@XyLoNaMiyX oh, i meant env, huh.

@douglasrizzo

This comment has been minimized.

Show comment
Hide comment
@douglasrizzo

douglasrizzo Nov 7, 2016

When I alter the .desktop file that fires up Telegram (like @XyLoNaMiyX mentions), sometimes it reverts back to its original state. I don't know if it is related to Telegram updates. However, if I create my own .desktop file in some other directory, like ~/.local/autostart, I am able to keep the custom Exec command.

douglasrizzo commented Nov 7, 2016

When I alter the .desktop file that fires up Telegram (like @XyLoNaMiyX mentions), sometimes it reverts back to its original state. I don't know if it is related to Telegram updates. However, if I create my own .desktop file in some other directory, like ~/.local/autostart, I am able to keep the custom Exec command.

@auchri auchri closed this Nov 8, 2016

@auchri auchri added the duplicate label Nov 8, 2016

@realjumy

This comment has been minimized.

Show comment
Hide comment
@realjumy

realjumy Feb 10, 2017

Also having problems with elementaryOS:

$ setxkbmap -query
rules: evdev
model: pc105
layout: es,us
variant: ,
options: grp:alt_shift_toggle

realjumy commented Feb 10, 2017

Also having problems with elementaryOS:

$ setxkbmap -query
rules: evdev
model: pc105
layout: es,us
variant: ,
options: grp:alt_shift_toggle

@luismanolo

This comment has been minimized.

Show comment
Hide comment
@luismanolo

luismanolo Feb 10, 2017

luismanolo commented Feb 10, 2017

@revagomes

This comment has been minimized.

Show comment
Hide comment
@revagomes

revagomes Feb 13, 2017

@realjumy I've fixed that by running $ ibus-setup. But just runing the config this way is not enough because it didn't work after restarting the machine, for example. I'll try some of the other suggestions anyway. but at least there is another workaround.

revagomes commented Feb 13, 2017

@realjumy I've fixed that by running $ ibus-setup. But just runing the config this way is not enough because it didn't work after restarting the machine, for example. I'll try some of the other suggestions anyway. but at least there is another workaround.

@luiarhs

This comment has been minimized.

Show comment
Hide comment
@luiarhs

luiarhs Feb 19, 2017

This works for me on elementary OS 0.3 and 0.4

You should have ibus-unikey installed, if you don't do it with this command:

sudo apt-get install ibus-unikey

Now configure ibus through ibus-setup. To do this, run the command on a terminal and go to the input method tab.

  1. Install your desired input method for IBus.
  2. Run ibus-setup command from terminal.
  3. Select 'Input method' tab and Add your desired input method.
  4. Close 'IBus Setup' and run ibus-daemon -drx in terminal.
  5. And on iBus Preferences unmark Use system keyboard layout

If you want IBus to automatically start with the system, then go to System Settings > Applications > Startup and add ibus-daemon -drx as a custom command or just click on Add Startup App and search iBus.

luiarhs commented Feb 19, 2017

This works for me on elementary OS 0.3 and 0.4

You should have ibus-unikey installed, if you don't do it with this command:

sudo apt-get install ibus-unikey

Now configure ibus through ibus-setup. To do this, run the command on a terminal and go to the input method tab.

  1. Install your desired input method for IBus.
  2. Run ibus-setup command from terminal.
  3. Select 'Input method' tab and Add your desired input method.
  4. Close 'IBus Setup' and run ibus-daemon -drx in terminal.
  5. And on iBus Preferences unmark Use system keyboard layout

If you want IBus to automatically start with the system, then go to System Settings > Applications > Startup and add ibus-daemon -drx as a custom command or just click on Add Startup App and search iBus.

@jesusgn90

This comment has been minimized.

Show comment
Hide comment
@jesusgn90

jesusgn90 Jul 10, 2017

The @luiarhs solution works for me, Ubuntu 16.04, Spanish Spain, 64 bits

jesusgn90 commented Jul 10, 2017

The @luiarhs solution works for me, Ubuntu 16.04, Spanish Spain, 64 bits

@mfrasca

This comment has been minimized.

Show comment
Hide comment
@mfrasca

mfrasca Feb 16, 2018

but why was the issues closed while we only have a workaround?
shouldn't it be closed after it's solved in the distributed software?

mfrasca commented Feb 16, 2018

but why was the issues closed while we only have a workaround?
shouldn't it be closed after it's solved in the distributed software?

@Selhar

This comment has been minimized.

Show comment
Hide comment
@Selhar

Selhar Feb 19, 2018

Had no problems on fedora 25, changed to fedora 27 and had to do the workaround.

Selhar commented Feb 19, 2018

Had no problems on fedora 25, changed to fedora 27 and had to do the workaround.

@mikaelmello

This comment has been minimized.

Show comment
Hide comment
@mikaelmello

mikaelmello May 9, 2018

Happened to me on Elementary OS 0.4.1, @luiarhs solution worked for me.

mikaelmello commented May 9, 2018

Happened to me on Elementary OS 0.4.1, @luiarhs solution worked for me.

@Henriquelay

This comment has been minimized.

Show comment
Hide comment
@Henriquelay

Henriquelay May 13, 2018

Confirmed, @luiarhs working on elementary OS 0.4.1, Telegram 1.2.17

Henriquelay commented May 13, 2018

Confirmed, @luiarhs working on elementary OS 0.4.1, Telegram 1.2.17

@mateusdeap

This comment has been minimized.

Show comment
Hide comment
@mateusdeap

mateusdeap Jun 3, 2018

Tried @luiarhs workaround on Ubuntu MATE 18.04 and Telegram 1.2.17, but it did not work at all.

mateusdeap commented Jun 3, 2018

Tried @luiarhs workaround on Ubuntu MATE 18.04 and Telegram 1.2.17, but it did not work at all.

@mfrasca

This comment has been minimized.

Show comment
Hide comment
@mfrasca

mfrasca Jun 3, 2018

@auchri , you closed this issue as a duplicate, but you didn't mention of which issue this is a duplicate.

mfrasca commented Jun 3, 2018

@auchri , you closed this issue as a duplicate, but you didn't mention of which issue this is a duplicate.

@Lonami

This comment has been minimized.

Show comment
Hide comment
@Lonami

Lonami Jun 3, 2018

Contributor
Contributor

Lonami commented Jun 3, 2018

@mfrasca, @Aokromes mentioned #1041 above.

@vegbrasil

This comment has been minimized.

Show comment
Hide comment
@vegbrasil

vegbrasil Jun 6, 2018

Before 1.3, export QT_IM_MODULE=xim used to work fine (except for ç). After the update, no special characters work, even with the IBus workaround.

Using Linux Mate with English (US, international with dead keys) working fine in every other app.

vegbrasil commented Jun 6, 2018

Before 1.3, export QT_IM_MODULE=xim used to work fine (except for ç). After the update, no special characters work, even with the IBus workaround.

Using Linux Mate with English (US, international with dead keys) working fine in every other app.

@mateusdeap

This comment has been minimized.

Show comment
Hide comment
@mateusdeap

mateusdeap Jun 7, 2018

I have the same setup as @vegbrasil concerning OS (mine being version 18.04, just to be specific) and keyboard. The only way I got it to work was downloading directly from the telegram site. Neither the snap package or the installations available in the ubuntu store or Mate Boutique work.

mateusdeap commented Jun 7, 2018

I have the same setup as @vegbrasil concerning OS (mine being version 18.04, just to be specific) and keyboard. The only way I got it to work was downloading directly from the telegram site. Neither the snap package or the installations available in the ubuntu store or Mate Boutique work.

@mfrasca

This comment has been minimized.

Show comment
Hide comment
@mfrasca

mfrasca Jun 7, 2018

then maybe better invite followup on #1041
adding comments on a closed issue will not have much impact

mfrasca commented Jun 7, 2018

then maybe better invite followup on #1041
adding comments on a closed issue will not have much impact

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment