SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After the "Fri Sep 20 00:38:57 UTC 2013" update I sometimes (suddenly) cannot type any letters in Qt based applications. Not only KDE apps but also Qt apps not using KDE.
Switching to another GUI window and then back makes input possible again. For apps with multiple tabs, such as konsole, I could also switch to another tab and back, then the problem is also gone.
Because I have no longer the packages before this update, I cannot easily test which package caused the problem.
Both kde-4.11.0 and kde-4.11.1 have had some bugs. Plasma is buggy in both versions. 4.11.1 had a double click taskbar bug (that was fixed in the latest git of kde-runtime)... so they've been playing with input code.
Sorry, I didn't know that. It was KDE 4.10.5 / kwin 4.10.5. And I repeat it was the "Fri Sep 20 00:38:57 UTC 2013" snapshot of slackware-current lest someone jumping directly to here missed the information in the original post.
It was not slackware64-current.
Quote:
Originally Posted by NoStressHQ
Giving a date requires the one to help you reading the changelog... Give us some hint or you will struggle to get any help...
I think the ChangeLog gives more information than if I list all my software versions because the change on that specific date mentioned above narrows the problem down to very few packages.
Now cannot type anything in konsole but mouse works.
Switch to any other window, or switch to another tab in the same konsole, then switch back, keyboard works again
I am sure I got this problem after the "Fri Sep 20 00:38:57 UTC 2013" update but I didn't keep a snapshot of slackware-current before that. So I cannot fix it by reverting the changes by the "Fri Sep 20 00:38:57 UTC 2013" update.
Another way to reproduce it is to receive a message from skype (skype then pops up a message window in the lower-right corner of the screen). Then after the message disappears, I lose keyboard input to my foreground Qt window.
Mouse input works perfectly fine at the same time. Only keyboard input is lost.
#!/bin/sh
if [ -x /usr/bin/scim ]; then
/usr/bin/scim -d &
fi
to
Code:
#!/bin/sh
if [ -x /usr/bin/scim ]; then
(sleep 30; /usr/bin/scim -d) &
fi
Until now this problem did not appear again. Looks like starting scim too early when KDE is restoring last session causes problems.
This workaround is too ugly, and the problem did not appear until the X updates on 20.Sep.2013, so I will not mark this thread as solved at present.
.
EDIT: No. The problem re-appeared after some time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
