[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-12-20 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376966

Christoph Feck  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |DOWNSTREAM
 Status|NEEDSINFO   |RESOLVED

--- Comment #24 from Christoph Feck  ---
Please report it to the bug tracker of the application or service that blocks
the keyboard input. We cannot magically get input when something else prevents
that.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-11-23 Thread Silver Salonen
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #23 from Silver Salonen  ---
I don't know now... to me it has really boiled down to Keyring blocking the
input. Is there something that can be done about it from KDE/Plasma side?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-11-23 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376966

Christoph Feck  changed:

   What|Removed |Added

 CC||mtm...@gmail.com

--- Comment #22 from Christoph Feck  ---
*** Bug 384891 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-19 Thread Theo
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #21 from Theo  ---
(In reply to Silver Salonen from comment #20)
> keyboard input does not work until I haven't inserted password for
> Keyring.
Same for me when I start Skype any time during a KDE session. The Gnome Keyring
prompt seem to block all keyboard input for anything but itself. If I remember
correctly, this also happened with the graphical password prompt for the SSH
agent (x11-ssh-askpass by Jim Knoble) that used to ask for my passphrase at the
start of the session.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-16 Thread Silver Salonen
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #20 from Silver Salonen  ---
One additional weird nuance - on startup both KWallet and Gnome Keyring are
asking for input (the latter because of Skype). Even if KWallet is focused then
keyboard input does not work until I haven't inserted password for Keyring.
Also it seems that keyboard input does not work within the whole environment,
eg. Alt+Tab, Alt+F2, Launcher menu search. After I submit anything into Keyring
dialog, keyboard input starts working for both Plasma and KWallet dialog.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-16 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=376966

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #19 from Nate Graham  ---
Great, sounds like this may be fixed now! Is anyone else still able to
reproduce with Plasma 5.11.0?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-16 Thread Theo
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #18 from Theo  ---
(In reply to Nate Graham from comment #16)
> Anything left to investigate here? Can we close the bug?
IBus is no longer killed by switching to TTY after I updated to Plasma 5.11.0
on my openSUSE Tumbleweed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-16 Thread Silver Salonen
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #17 from Silver Salonen  ---
To my mind it's somewhat clear that it is related to ibus, but is it really
clear how?

As I understand on one case ibus crashes and this causes keyboard input issues,
but on another case (mine) the issue is solved when this solves issues.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-15 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=376966

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

--- Comment #16 from Nate Graham  ---
Anything left to investigate here? Can we close the bug?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-12 Thread Silver Salonen
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #15 from Silver Salonen  ---
Sorry, I'm giving inconsistent information :/
I did full upgrade of all my software (did not re-install ibus) and restarted
my computer, and now keyboard input works also for KWallet right after login.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-12 Thread Silver Salonen
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #14 from Silver Salonen  ---
For me it doesn't indeed change a thing - I removed everything related to ibus
and after logging out and in again the state is exactly the same. Ie. input in
KWallet input request does not work, but to some other applications input
works. This has somehow improved since some time (as I reported at some point,
input in KRunner dialog or in launcher menu didn't work, but now it does), but
I have no idea with what and when exactly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-12 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #13 from Christoph Feck  ---
So let's recap: This issue is related to IBus. Does uninstalling it resolve the
issue? I doubt Plasma has any influence on input.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-08 Thread Theo
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #12 from Theo  ---
(In reply to Theo from comment #6)
> This happens often
> after my system has been stalled when running out of memory. Once my system
> is responding again, the IBus daemon for the desktop user is gone.
For the record, apparently IBus is indeed killed when switching to TTY. I
wasn't aware of this when I wrote that comment.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-03 Thread Silver Salonen
https://bugs.kde.org/show_bug.cgi?id=376966

Silver Salonen  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #11 from Silver Salonen  ---
Okay, I cheered to soon. For me ibus-daemon doesn't actually crash - it's
running fine after I log into Plasma5. When I don't have it running then input
just doesn't work in even more applications. But killing or restarting it
doesn't make everything work still :(

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-02 Thread Silver Salonen
https://bugs.kde.org/show_bug.cgi?id=376966

Silver Salonen  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #10 from Silver Salonen  ---
Ok, I'll mark it as duplicate then.

*** This bug has been marked as a duplicate of bug 379930 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-01 Thread Patrick Rudolph
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #9 from Patrick Rudolph  ---
Turns out the ibus behaviour on tty change is already fixed here:
https://bugs.kde.org/show_bug.cgi?id=379930

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-01 Thread Patrick Rudolph
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #8 from Patrick Rudolph  ---
I can confirm that running ibus-daemon --xim -d as user fixes the problem.
I had to place it inside a while loop to restart it automatically every time I
switch ttys as the ibus daemon crashes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-01 Thread Silver Salonen
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #7 from Silver Salonen  ---
Wow, that totally fixes the problem for me!

Thank you very much Theo!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-10-01 Thread Theo
https://bugs.kde.org/show_bug.cgi?id=376966

Theo  changed:

   What|Removed |Added

 CC||alpha0...@yahoo.de

--- Comment #6 from Theo  ---
I have this problem on openSUSE Tumbleweed, KDE Plasma 5.10.5. Keystrokes are
registered only sporadically in all KDE applications as described in
https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1633721 (that
bug seems to be about input fields only, though). This happens often after my
system has been stalled when running out of memory. Once my system is
responding again, the IBus daemon for the desktop user is gone. Running
'ibus-daemon --xim -d' as user fixes the keyboard input problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-05-10 Thread Patrick Rudolph
https://bugs.kde.org/show_bug.cgi?id=376966

Patrick Rudolph  changed:

   What|Removed |Added

 CC||patrick.rudolph@br-automati
   ||on.com

--- Comment #5 from Patrick Rudolph  ---
The problem was observed on 5.8.6 with the following two applications:

* Konsole application
* Alt + F2 launcher

All other applications accepted keyboard input.
There's no information whether or not the application was autolaunched by KDE.

Closing the Konsole application and starting a new one fixed the problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-03-15 Thread Roman Prots'
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #4 from Roman Prots'  ---
Similar behavior from my side.
When konsole starts right after login automatically I can't type into it. If
closing it and opening again it works.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-03-15 Thread Silver Salonen
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #3 from Silver Salonen  ---
One interesting nuance I've noticed lately is that after logging in KWallet
password prompt input works only a while - if I enter my password within 5
seconds or so then it works, but after that not anymore. Also, it sometimes
happens in Konsole that input works in the newly opened window for some time,
but then stops working. I then need to open a new window.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-03-15 Thread Roman Prots'
https://bugs.kde.org/show_bug.cgi?id=376966

--- Comment #2 from Roman Prots'  ---
Might be related: https://bbs.archlinux.org/viewtopic.php?id=216797

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 376966] Keyboard input does not work for some applications

2017-03-15 Thread Roman Prots'
https://bugs.kde.org/show_bug.cgi?id=376966

Roman Prots'  changed:

   What|Removed |Added

 CC||rpr...@gmail.com

--- Comment #1 from Roman Prots'  ---
Problem gets reproduced on 5.8.5 version.

-- 
You are receiving this mail because:
You are watching all bug changes.