Typed text is deleted
Nothing happens
Operating system:
Kubuntu 14.04
Version of Telegram Desktop:
0.9.56
@perk11 Is this still an issue? I do not experience this on KDE.
Still have this on KDE5 (Kubuntu 16.04) with Telegram 0.10.1
What locale are you using? (command locale)
LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8
Having the same problem on two different machines running Arch Linux (x86_64) with Openbox
Same issue with 1.1.18 on BunsenLabs (Debian 7) with Openbox
I remember having this issue on Arch with xfce and Mac ISO keyboard layout, with en_US.UTF-8 layout.
Same here on ArchLinux with KDE. Telegram version 1.1.15.
Don't have this issue (Mint cinnamon).
Still happens in Kubuntu 18.04, both when Caps Lock is used for keyboard layout switching and when it's not.
Still happens in Gentoo and Calculate Linux, Telegram version 1.4.7 and earlier.
Still happens in openSUSE Tumbleweed with KDE
Backspace when in Caps Lock works well in the distro supplied version of Telegram 1.5.11 on (K)ubuntu. Can you try?
I suspect this Caps Lock issue is another problem caused by not using the official QT from the system but a slightly patched one. https://github.com/telegramdesktop/tdesktop/issues/1815
Backspace when in Caps Lock works well in the distro supplied version of Telegram 1.5.11 on (K)ubuntu. Can you try?
Half a year since my last comment. Recent Tumbleweed (new installation, btw), same issue.
Instead of moaning it would be better to confirm if the issue is indeed related to https://github.com/telegramdesktop/tdesktop/issues/1815 or not. Unfortunately afaik there is no Telegram distro version for Suse (yet). Check this comment, it says there is an OpenSuse patch for Telegram: https://github.com/telegramdesktop/tdesktop/issues/1815#issuecomment-432642485
Fedora (RPMFusion) latest version 1.8.1 still have this problem too.
Fedora (RPMFusion) latest version 1.8.1 still have this problem too.
Are you sure you are using the distro repository version, because that seems to be still at 1.6.7-2.fc30 according to https://pkgs.org/download/telegram. If you downloaded and extracted Telegram from their website, then it comes with its own QT which is causing all this trouble with Caps, compose keys and intl. language input like fctix, nimf, etc.
@mxa yes, please see http://koji.rpmfusion.org/koji/packageinfo?packageID=492
@mxa yes, please see http://koji.rpmfusion.org/koji/packageinfo?packageID=492
Has this version been patched to use the system QT? Or does it come including the Telegram-QT?
Has this version been patched to use the system QT? Or does it come including the Telegram-QT?
According to ldd, it uses system Qt libs:
$ ldd /usr/bin/telegram-desktop | grep Qt
libQt5Network.so.5 => /lib64/libQt5Network.so.5 (0x00007f1be3a00000)
libQt5Widgets.so.5 => /lib64/libQt5Widgets.so.5 (0x00007f1be3360000)
libQt5Gui.so.5 => /lib64/libQt5Gui.so.5 (0x00007f1be2e28000)
libQt5DBus.so.5 => /lib64/libQt5DBus.so.5 (0x00007f1be2d8c000)
libQt5Core.so.5 => /lib64/libQt5Core.so.5 (0x00007f1be286e000)
I did some investigating, there are an ancient Qt bug that prevents from being backspace working if caps lock is layout switcher and actual caps lock is shift + caps lock
https://bugreports.qt.io/browse/QTBUG-49771
The only solution is to not using caps lock as a layout switcher.
Can't reproduce this bug with Telegram 2.0.1 on Kubuntu.
I'm glad to hear it, but I can reproduce this issue with 100% success if I set caps lock as a key for layout switching and enable caps lock with shift+caps lock
I'm glad to hear it, but I can reproduce this issue with 100% success if I set caps lock as a key for layout switching and enable caps lock with shift+caps lock
Ah, I use the caps lock key as compose key and enable caps lock by pressing both shift keys simultaneously.
@Aokromes can you reopen this since the fix was reverted?