LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 09-24-2013, 05:12 AM   #1
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 146Reputation: 146
[BUG] Qt programs get no keyboard input


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.

Last edited by guanx; 10-02-2013 at 09:29 AM.
 
Old 09-24-2013, 09:37 PM   #2
NoStressHQ
Member
 
Registered: Apr 2010
Location: Lausanne - Switzerland ( Bordeaux - France / Montreal - QC - Canada)
Distribution: Slackware Leet - 32/64bit
Posts: 276

Rep: Reputation: 93
Which WM to you use ? It sounds like an input focus problem.

(Also versions of Slackware, used WM and X11 would help...)
 
Old 09-25-2013, 01:52 AM   #3
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Original Poster
Rep: Reputation: 146Reputation: 146
The slackware version is the "Fri Sep 20 00:38:57 UTC 2013" snapshot of -current.
The DE is KDE and the WM is kwin.
 
Old 09-25-2013, 09:19 AM   #4
NoStressHQ
Member
 
Registered: Apr 2010
Location: Lausanne - Switzerland ( Bordeaux - France / Montreal - QC - Canada)
Distribution: Slackware Leet - 32/64bit
Posts: 276

Rep: Reputation: 93
Quote:
Originally Posted by guanx View Post
The slackware version is the "Fri Sep 20 00:38:57 UTC 2013" snapshot of -current.
The DE is KDE and the WM is kwin.
Well you don't name the versions of KDE neither WM (ie: I don't have current)...

You don't say which full version of slackware you're using (32 ? 64bit? )

Giving a date requires the one to help you reading the changelog... Give us some hint or you will struggle to get any help...

And for what I see, the version of X11 and KWin is crucial (it's up to them to handle input focus...).
 
Old 09-25-2013, 09:30 AM   #5
jon lee
Member
 
Registered: Jul 2013
Posts: 81

Rep: Reputation: Disabled
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.
 
Old 09-25-2013, 12:11 PM   #6
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Original Poster
Rep: Reputation: 146Reputation: 146
Quote:
Originally Posted by NoStressHQ View Post
(ie: I don't have current)...
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 View Post
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.

Last edited by guanx; 09-25-2013 at 12:12 PM.
 
Old 09-25-2013, 12:14 PM   #7
NoStressHQ
Member
 
Registered: Apr 2010
Location: Lausanne - Switzerland ( Bordeaux - France / Montreal - QC - Canada)
Distribution: Slackware Leet - 32/64bit
Posts: 276

Rep: Reputation: 93
Finding solution is all about "narrowing the problem"
 
Old 09-25-2013, 12:18 PM   #8
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Original Poster
Rep: Reputation: 146Reputation: 146
I know a solution is to revert to the "Thu Sep 19 06:48:59 UTC 2013" snapshot. Unfortunately I don't have it anymore ...
 
Old 09-30-2013, 09:51 AM   #9
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Original Poster
Rep: Reputation: 146Reputation: 146
How I found a way to reproduce this bug easily.
  • Open konsole
  • Start something in konsole, e.g. okular
  • Move okular to the upper left corner of screen
  • Close okular
  • 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.
 
Old 09-30-2013, 11:06 AM   #10
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Original Poster
Rep: Reputation: 146Reputation: 146
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.
 
Old 10-14-2013, 04:49 AM   #11
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Original Poster
Rep: Reputation: 146Reputation: 146
Changed "~/.kde/Autostart/scim.sh" from
Code:
#!/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.

Last edited by guanx; 10-14-2013 at 12:14 PM.
 
Old 10-25-2013, 05:23 AM   #12
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Original Poster
Rep: Reputation: 146Reputation: 146
Solved:
http://www.linuxquestions.org/questi...qt-4175482102/
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Read keyboard status (not: wait for keyboard input). stf92 Programming 14 07-03-2011 05:55 PM
xf86-input-keyboard and xf86-input-mouse masked CollieJim Gentoo 4 11-09-2009 09:57 PM
Repeated "input: AT Translated Set 2 keyboard as /class/input/input" messages AcerKev Mandriva 2 09-16-2007 08:35 AM
Chinese Input Programs???? tricky_linux Linux - Software 68 05-31-2005 10:27 AM
my mouse input is takes as keyboard input in BASH e1000 Slackware 5 12-08-2003 03:00 PM


All times are GMT -5. The time now is 03:27 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration