Bug 5159

Summary:	Keyboard doesn't work everywhere after launching telegram desktop client
Product:	Fedora	Reporter:	Ashutosh Sharma <ashu-development.cyclical>
Component:	telegram-desktop	Assignee:	Vitaly <vitaly>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	P1
Version:	f29
Hardware:	x86_64
OS:	GNU/Linux
namespace:
Attachments:	on-screen keyboard not working properly log file as requested

Description Ashutosh Sharma 2019-02-04 11:20:57 CET

It is a strange issue, what happens is that when I launch telegram desktop, keyboard stops working while entering local passcode and I have to kill telegram but for some reason some other applications such as KeePassXC doesn't work after that, also, on-screen keyboard doesn't work properly (it launches and appears when I focus on input fields but not all keys work.) Keyboard is fine and it works on most of the applications but it doesn't work in GNOME itself, e.g., if do ALT + F2 and open CLI, I am unable to type anything in it I have to use mouse to close it.

Comment 1 Ashutosh Sharma 2019-02-04 11:24:44 CET

Created attachment 2010 [details]
on-screen keyboard not working properly

Comment 2 Vitaly 2019-02-04 11:27:07 CET

> on-screen keyboard not working properly

Then this is not a Telegram Desktop's bug.

Comment 3 Ashutosh Sharma 2019-02-04 11:33:42 CET

(In reply to Vitaly Zaitsev from comment #2)
> > on-screen keyboard not working properly
> 
> Then this is not a Telegram Desktop's bug.

Please read my entire report, I have mentioned that this only happens after I launch telegram client.

Comment 4 Vitaly 2019-02-04 11:38:53 CET

> Please read my entire report, I have mentioned that this only happens after I launch telegram client.

Then I need full journalctl report after this bug. I think the problem is located in libinput library.

Comment 5 Ashutosh Sharma 2019-02-04 12:21:26 CET

Created attachment 2011 [details]
log file as requested

Comment 6 Vitaly 2019-02-04 12:28:56 CET

1. I see lots of SELinux errors in log.
2. I see corrupted RPM database.
3. I see gnome-shell crash and errors like this:

> Feb 04 16:31:16 ashu gnome-shell[2413]: Error processing key on IM: Timeout was reached

You need to fix RPM database first, then resolve SELinux and gnome-shell errors.

Comment 7 Ashutosh Sharma 2019-02-04 12:49:15 CET

There is one particular error which has repeated multiple times when keyboard stopped working:

`Error processing key on IM: Timeout was reached`

And there is an open issue on GitLab with similar error message: https://gitlab.gnome.org/GNOME/mutter/issues/454

do you think it is related to mutter?(In reply to Vitaly Zaitsev from comment #6)
> 1. I see lots of SELinux errors in log.
> 2. I see corrupted RPM database.
> 3. I see gnome-shell crash and errors like this:
> 
> > Feb 04 16:31:16 ashu gnome-shell[2413]: Error processing key on IM: Timeout was reached
> 
> You need to fix RPM database first, then resolve SELinux and gnome-shell
> errors.

1. It is a reported issue: https://bugzilla.redhat.com/show_bug.cgi?id=1648680
2. I think it is related to 1
3. Thanks for pointing to this particular error - I've found these bugs and think my issue is related to ibus: https://bugzilla.redhat.com/show_bug.cgi?id=1671286 & https://gitlab.gnome.org/GNOME/mutter/issues/454

Thanks for your time and sorry for any inconvenience.