Hello:

I am doing my first F17 install on i686 Xfce and, for the most part,
everything is coming up nicely. However, I am noticing that sometimes
the keyboard becomes unresponsive. I can't seem to find a reason, it
just happens. My first sense was that it was a hardware problem.


However, one time I decided to let the session time out so that when I
had moved the mouse, I got the "re-enter passwd" dialog box to get back
to my session. As could be expected, I couldn't type my password in. So
I tried selecting new user login and, lo and behold, if I clicked on
myself, it let me enter a password. However, it then immediately went
back to the "re-enter passwd" from the session time out and the keyboard
was dead.


Net result is I find it hard to believe that the hardware is the
problem. But I can't figure out what would be locking up the keyboard so
that it would appear dead. I also note that I had multiple windows open
plus firefox and the keyboard wouldn't work in any of them, so it isn't
shell based. One time I ran a tail of /var/log/messages and nothing
showed up in it once the keyboard died and it did give me other standard
messages when I waited about a half hour to new messages to be flushed
to the file.


Any ideas about where to start? Everything I spotted online didn't seem
to relate ... and I am having a hard time figuring out what a good set
of search terms for this problem is.


Thanks in advance,
Paul
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 10/10/2012 05:43 PM, Paul Allen Newell wrote:

Any ideas about where to start? Everything I spotted online didn't seem
to relate ... and I am having a hard time figuring out what a good set
of search terms for this problem is.


Try opening a terminal and running top in it. Then, when this happens
you can look at the terminal and see if something's hogging the cpu.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 10/11/2012 08:43 AM, Paul Allen Newell wrote:
> Hello:
>
> I am doing my first F17 install on i686 Xfce and, for the most part, everything is coming up nicely. However, I am noticing that sometimes the keyboard becomes unresponsive. I can't seem to find a reason, it just happens. My first sense was that it was a hardware problem.
>
> However, one time I decided to let the session time out so that when I had moved the mouse, I got the "re-enter passwd" dialog box to get back to my session. As could be expected, I couldn't type my password in. So I tried selecting new user login and, lo and behold, if I clicked on myself, it let me enter a password. However, it then immediately went back to the "re-enter passwd" from the session time out and the keyboard was dead.
>
> Net result is I find it hard to believe that the hardware is the problem. But I can't figure out what would be locking up the keyboard so that it would appear dead. I also note that I had multiple windows open plus firefox and the keyboard wouldn't work in any of them, so it isn't shell based. One time I ran a tail of /var/log/messages and nothing showed up in it once the keyboard died and it did give me other standard messages when I waited about a half hour to new messages to be flushed to the file.
>
> Any ideas about where to start? Everything I spotted online didn't seem to relate ... and I am having a hard time figuring out what a good set of search terms for this problem is.
>

You fail to mention what type of keyboard you have. PS2, USB, Wireless USB, Bluetooth?

I have a Wireless USB that becomes non-responsive from time to time. Unplug/plug receiver clears the problem.


--
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -- Rick Cook, The Wizardry Compiled
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 10/10/2012 05:53 PM, Joe Zeff wrote:

On 10/10/2012 05:43 PM, Paul Allen Newell wrote:

Any ideas about where to start? Everything I spotted online didn't seem
to relate ... and I am having a hard time figuring out what a good set
of search terms for this problem is.


Try opening a terminal and running top in it. Then, when this happens
you can look at the terminal and see if something's hogging the cpu.

Joe:

Thanks for prompt reply.

I ran that test earlier but saw pretty much no cpu activity so I didn't
get the sense I was pegging out at 100%. Forgot to mention in my
original email, sorry


The mouse and its buttons are totally responsive during this time ...
its just the keyboard. I even tried unplugging and plugging back in.


I can ssh into the machine from another box and have no problems after
the keyboard has locked up for the keyboard of that machine. This has
become my "fallback" so I can try to get things stable before I restart
the system. I just realized that I haven't tried using the logout dialog
to kill that user and then seeing if I can come back in fresh ... next
test when the failure happens


Paul

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 10/10/2012 05:58 PM, Ed Greshko wrote:


You fail to mention what type of keyboard you have. PS2, USB, Wireless USB, Bluetooth?

I have a Wireless USB that becomes non-responsive from time to time. Unplug/plug receiver clears the problem.




Ed:

Thanks for response

PS2, wired.

Given the fact that I was able to type once I selected New login on the
"locked screen" dialog and, at the splash for which user to log in as,
the keyboard works, I figured the keyboard was not the problem.


Paul

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 10/10/2012 05:58 PM, Paul Allen Newell wrote:


I ran that test earlier but saw pretty much no cpu activity so I didn't
get the sense I was pegging out at 100%. Forgot to mention in my
original email, sorry


That's OK. If nothing else, we've eliminated a possibility.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

On 10/10/2012 05:58 PM, Paul Allen Newell wrote:
I just realized that I haven't tried using the logout dialog to kill
that user and then seeing if I can come back in fresh ... next test
when the failure happens


Paul


Just died again and I was able to try this

Using logout dialog to end the session, it allowed me to come back as a
new user and keyboard was working. Remembered my layout from when I
logged out (little good that does me)


Paul

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org