Re: Suspend-to-RAM--resume: keyboard problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday 22 March 2010, Serguei Miridonov wrote:
> Hello,
> 
> I have the following problem: after several days of up time with
> 2-3 suspend-to-RAM--resume cycles every day some keys stop
> working. The problem appears to be in X server: I can switch user
> in KDE and start a new X server where keyboard works as expected.
> I can even save key mapping with xmodmap and then partially
> restore keyboard functionality in the X session with broken keys.
> 
> I have filed a bug but there is no any confirmation from developers
> or other users:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=574666
> 
> Any idea?
> 
> Serguei.

OK, I have just found that this has nothing to do with suspend-resume. 
The same problem with keyboard happens right after 10 switch-to-text-
console and back cycles (Ctrl-Alt-F2 and then Alt-F1: repeat 10 
times).

Is there anything to check in order to find the reason? How can I 
check keyboard mapping and other keyboard settings by something other 
than xmodmap?

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux