Bug 714378 - F15 physical keyboard stops working, plasma-keyboard does still work, must restart xorg
Summary: F15 physical keyboard stops working, plasma-keyboard does still work, must re...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdelibs
Version: 15
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-18 18:13 UTC by Reartes Guillermo
Modified: 2012-06-03 00:50 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-03 00:50:09 UTC
Type: ---


Attachments (Terms of Use)
dmesg with debug (123.13 KB, application/octet-stream)
2011-06-18 18:13 UTC, Reartes Guillermo
no flags Details
Xorg.0.log.old from the time of the issue (38.06 KB, text/plain)
2011-06-18 18:19 UTC, Reartes Guillermo
no flags Details

Description Reartes Guillermo 2011-06-18 18:13:39 UTC
Created attachment 505401 [details]
dmesg with debug

Description of problem:

I was using kate, firefox (several tabs and windows), opera (several tabs), amarok, etc. 

It happened when i was typing in kate, switching back and forth firefox (cut & paste) and maybe opera. 

Instantly i noticed that the keyboard stopped responding. Thankfully, due my 
past experience with (in F13):

* Bug 645610 - xorg keyboard stops working, must reboot or restart xorg

I had setup the kde plasma-keyboard widget, so i checked dmesg and Xorg.0.log and no error was issued. 

I closed all programs and the keyboard did not return. 

I had to exit KDE and re-login again. CAPS LOCK did not work when the keyboard was "absent". It is strange that it did not happen during all the heavy use during F15 alpha & beta. 


I opened another bug-report due to:
 * a lot of hardware changes were made during that bug-report (example, nouveau > nvidia > radeon), so that bug-report is in some sense polluted and the software versions all all different. 

 * i used this system since F15 alpha was 'pre-released', the only recent addition is a sata_sil24 pcie controller.

 * i cannot belive it had returned, but there is one important catch: i started using my /home filesystem only when F15 was released and not with F15a/F15b, so there might be some offending config in /home. If  that is the case, it will explain the 'return of the bug'. 

This is the first time it happened since i installed F15 release.
It only happened while in KDE. (it also applies to bug 645610).



Version-Release number of selected component (if applicable):
kernel 2.6.38.8-32.fc15.x86_64

kdelibs.x86_64                   6:4.6.3-5.fc15          @updates          
kdelibs-common.x86_64            6:4.6.3-5.fc15          @updates          
kdelibs-debuginfo.x86_64         6:4.6.3-5.fc15          @updates-debuginfo

xorg-x11-drv-ati.x86_64 6.14.1-1.20110504gita6d2dba6.fc15 @koji-override-0/$releasever

xorg-x11-server-Xorg.x86_64   1.10.2-1.fc15    @updates


How reproducible:
* happens sometimes

Steps to Reproduce:
1. open al lot of programs (KDE)
2. at least kate, firefox, konsole
3. it may/may not happen.
  
Actual results:
* unable to type with the physical keyboard. the plasma-keyboard keeps working.
* the problem is worse when i have opened a lot of files and being forced to close them all is really annoying.

Expected results:

Additional info:
KDE DE enabled (OpenGL)
Video: VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon HD 5670] [1002:68d8] , using open source driver radeon (KMS).

Comment 1 Reartes Guillermo 2011-06-18 18:19:10 UTC
Created attachment 505402 [details]
Xorg.0.log.old from the time of the issue

Comment 2 Reartes Guillermo 2011-06-18 19:59:07 UTC
The /home filesystem was created in 03/08/2009, so it was created under Slackware 12.1, which uses KDE 3.5.x. Then i installed Slackware64 13.0 which was released in 03/09/2009 and uses KDE 4.2.x, at that moment i did delete the KDE3 config.

Then i installed Slackware64 13.1 (stangely, the release anouncement does not appear in both the page and in the anouncement mailing list...). I used it shortly and them installed F13 and then F15, a week after it was released.

$ pwd
/home/guille

$ ls -ld .kde* 
drwx------. 6 guille guille 4096 Jul  3  2010 .kde
drwxr-xr-x. 4 guille guille 4096 Feb 21  2010 .kde4
-rw-------. 1 guille guille  546 Sep  4  2010 .kderc
drwxr-xr-x. 3 guille guille 4096 Oct 27  2010 .kdevduchain

$ ls -l .kde/
total 16
drwxr-xr-x.  2 guille guille 4096 Aug 28  2009 Autostart
lrwxrwxrwx.  1 guille guille   24 Aug 28  2009 cache-ulquiorra -> /var/tmp/kdecache-guille
lrwxrwxrwx.  1 guille guille   24 Jul  3  2010 cache-ulquiorra.espada -> /var/tmp/kdecache-guille
drwxr-xr-x.  2 guille guille 4096 Aug 29  2009 env
drwx------. 10 guille guille 4096 Aug 29  2009 share
drwxr-xr-x.  2 guille guille 4096 Aug 29  2009 shutdown
lrwxrwxrwx.  1 guille guille   19 Aug 28  2009 socket-ulquiorra -> /tmp/ksocket-guille
lrwxrwxrwx.  1 guille guille   19 Jul  3  2010 socket-ulquiorra.espada -> /tmp/ksocket-guille
lrwxrwxrwx.  1 guille guille   15 Aug 28  2009 tmp-ulquiorra -> /tmp/kde-guille
lrwxrwxrwx.  1 guille guille   15 Jul  3  2010 tmp-ulquiorra.espada -> /tmp/kde-guille

$ ls -l .kde4/
total 8
drwxr-xr-x. 2 guille guille 4096 Feb 21  2010 Autostart
lrwxrwxrwx. 1 guille guille   24 Feb 21  2010 cache-ulquiorra -> /var/tmp/kdecache-guille
drwx------. 5 guille guille 4096 Feb 21  2010 share
lrwxrwxrwx. 1 guille guille   19 Feb 21  2010 socket-ulquiorra -> /tmp/ksocket-guille
lrwxrwxrwx. 1 guille guille   15 Feb 21  2010 tmp-ulquiorra -> /tmp/kde-guille

There are some files older than the filesystem, i do not remember if i had restored it when i migrated from a single partition to a raid1 /home. I did remember that i deleted the kde3 config stuff, but is it normal to have both .kde and .kde4 directories? what is kdevduchain?

Comment 3 Reartes Guillermo 2012-06-02 21:06:55 UTC
I switched to F17 recently and i never encountered the issue since the last comment, so that is a good thing.

Please close this bugreport.


Note You need to log in before you can comment on or make changes to this bug.