On 10/19/2012 10:56 PM, Ed Greshko wrote:
I've not been paying to much attention to this thread recently.
Time to put the failing keyboard back on the F17 system to verify the problem
still exists?
Ed:
Thanks for the reply. Understand that this isn't a problem that has alot
of bearing
On Mon, 15 Oct 2012 16:20:35 -0700
Paul Allen Newell pnew...@cs.cmu.edu wrote:
This is getting to be way too much fun ...
A different keyboard (the one that came with the HP beast) does not have
any failure problems after a couple of days of testing. The original
keyboard (a MicroSoft
On 10/20/2012 01:50 PM, Paul Allen Newell wrote:
On Mon, 15 Oct 2012 16:20:35 -0700
Paul Allen Newell pnew...@cs.cmu.edu wrote:
This is getting to be way too much fun ...
A different keyboard (the one that came with the HP beast) does not have any
failure problems after a couple of days
DJ Delorie:
Hey developers! hold shift key for 10 seconds is common in many
video games (esp Minecraft). You can't just change the user's
keyboard without warning!
Tim:
It's also common for typing ALL CAPS words when you don't want to use
the caps lock key.
Or batch selecting a group of
On Mon, 15 Oct 2012 16:20:35 -0700
Paul Allen Newell pnew...@cs.cmu.edu wrote:
On 10/15/2012 4:00 PM, Bob Marcan wrote:
It was occured to me on F16 several times.
Killing X restores the keyboard.
Reading this thread tried with holding shift key 20+ seconds restores
too.
It shouldn't be
I've had PS/2 keyboard problems in F17. Two things to try:
1. Hold down a key and see if it starts auto-repeating. In my case, the
first keypress is lost, but auto-repeat keypresses get through.
2. Ctrl-Alt-2 to a text terminal and see if the keyboard works outside
of X. In my case, it
On 10/15/2012 2:51 PM, DJ Delorie wrote:
I've had PS/2 keyboard problems in F17. Two things to try:
1. Hold down a key and see if it starts auto-repeating. In my case, the
first keypress is lost, but auto-repeat keypresses get through.
2. Ctrl-Alt-2 to a text terminal and see if the
You could also try an F16 or F18 Live CD and see if the problem is
F17-specific...
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines:
On 10/15/2012 3:43 PM, DJ Delorie wrote:
You could also try an F16 or F18 Live CD and see if the problem is
F17-specific...
Problem has not occurred on FC5, F9, F12, F14, or F16. It is only
showing up now that I kicked one machine to F17. I will consider trying
F18 Live once its released and
On Mon, 15 Oct 2012 15:46:06 -0700
Paul Allen Newell pnew...@cs.cmu.edu wrote:
On 10/15/2012 3:43 PM, DJ Delorie wrote:
You could also try an F16 or F18 Live CD and see if the problem is
F17-specific...
Problem has not occurred on FC5, F9, F12, F14, or F16. It is only showing up
now
On 10/15/2012 04:46 PM, Paul Allen Newell wrote:
On 10/15/2012 3:43 PM, DJ Delorie wrote:
You could also try an F16 or F18 Live CD and see if the problem is
F17-specific...
Problem has not occurred on FC5, F9, F12, F14, or F16. It is only
showing up now that I kicked one machine to F17. I
On 10/15/2012 4:00 PM, Bob Marcan wrote:
It was occured to me on F16 several times.
Killing X restores the keyboard.
Reading this thread tried with holding shift key 20+ seconds restores
too.
It shouldn't be tied to WM, running Fvwm.
BR, Bob
Bob:
Thanks for reply.
Should I interpret Reading
On 10/15/2012 4:01 PM, JD wrote:
One final, but remote chance - do you have xorg.conf in /etc/X11 or
any of it's sub-dirs?
If yes, delete it or rename it, and reboot - it could be the cause by
loading wrong KB driver.
JD:
Thanks for reply. I took a look and do not see any xorg.conf. That
On Monday, October 15, 2012, Paul Allen Newell wrote:
On 10/15/2012 4:01 PM, JD wrote:
One final, but remote chance - do you have xorg.conf in /etc/X11 or any
of it's sub-dirs?
If yes, delete it or rename it, and reboot - it could be the cause by
loading wrong KB driver.
JD:
Thanks
On 10/15/2012 4:57 PM, Paul Johnson wrote:
Hi!
I am nearly certain this is accidental triggering of SLOW KEYS , a
feature to assist the physically impaired. It gets triggered if you
rest your finger on the shift key for 10 seconds. The kb is not dead,
but slow. Rest finger in shift 10
Paul Johnson pauljoh...@gmail.com writes:
I am nearly certain this is accidental triggering of SLOW KEYS,
That was EXACTLY it for me. Hey developers! hold shift key for 10
seconds is common in many video games (esp Minecraft). You can't just
change the user's keyboard without warning!
On 10/15/2012 07:00 PM, DJ Delorie wrote:
If I find out which program turned that feature on, I'm taking it out
back and shooting it.
I wasn't paying attention earlier, so maybe this was already pointed
out: Open the Universal Access section of GNOME's settings. Select the
Typing tab and
On Mon, 2012-10-15 at 22:00 -0400, DJ Delorie wrote:
Hey developers! hold shift key for 10 seconds is common in many
video games (esp Minecraft). You can't just change the user's
keyboard without warning!
It's also common for typing ALL CAPS words when you don't want to use
the caps lock
On 10/15/2012 7:00 PM, DJ Delorie wrote:
Paul Johnson pauljoh...@gmail.com writes:
I am nearly certain this is accidental triggering of SLOW KEYS,
That was EXACTLY it for me.
Glad to hear your situation is solved ... I am certain I'll be able to
figure mine out and post a SOLVED at some
On Fri, 2012-10-12 at 19:26 -0700, Paul Allen Newell wrote:
somewhere around the 15th minute when I was mousing in one of the dead
shells to scroll my history to make sure I had got everything, I
accidentally brushed a key and, lo and behold, the keyboard was
alive.
Does sound suspiciously
On 10/13/2012 6:25 AM, Tim wrote:
Does sound suspiciously like a broken keyboard.
Tim:
I'll find out that one when I rotate keyboardsper Ed's suggestion. My
gut doesn't feel like its the keyboard given the problem showed up only
when I installed that machine with F17, but I am suspect of
On 10/13/2012 11:56 AM, Paul Allen Newell wrote:
I'll find out that one when I rotate keyboardsper Ed's suggestion. My
gut doesn't feel like its the keyboard given the problem showed up only
when I installed that machine with F17, but I am suspect of the computer
itself. I'm going to bring a
On 10/13/2012 12:20 PM, Joe Zeff wrote:
An excellent idea. Then, once you find that the new machine works
fine[1] you can swap keyboards and see if the issue follows the
keyboard. Just remember, however, if one of them's PS2 and the
other's USB, that in itself might be significant.
On 10/13/2012 12:24 PM, Paul Allen Newell wrote:
All keyboards and all computers are PS2, so I won't have that variable.
And I am already leaning to the problem being on my end, not F17's, now
that I saw the keyboard rise from the dead after 10-15 minutes.
Good! As you say, that's one less
On 10/10/2012 10:28 PM, Paul Allen Newell wrote:
On 10/10/2012 6:35 PM, Kevin Fenzi wrote:
When this happens, can you try holding down the shift key for say
15-20seconds? Do you see a notice then about 'slow keys' being disabled
and it starts working again?
kevin
Kevin:
[...]
This test
On Wed, 2012-10-10 at 19:10 -0700, Joe Zeff wrote:
I was wondering about the PS2 keyboard, but my memory told me that you
had to reboot if it came unplugged. Guess that must be
Windows-specific.
As far as I know, yes, it was a Windows problem that some couldn't
handle a keyboard being
On 10/10/2012 10:44 PM, Paul Allen Newell wrote:
==
The keyboard knows I am getting good help at trying to solve this ... it
behaved like a champ today. If it doesn't act up through the beginning
of next week, I will consider that it is a POM issue caused by something
in my install F17
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
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
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
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
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
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
On Wed, 10 Oct 2012 18:05:07 -0700
Paul Allen Newell pnew...@cs.cmu.edu wrote:
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.
When this
On 10/11/2012 09:05 AM, Paul Allen Newell wrote:
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.
I see. It has
On 10/10/2012 06:43 PM, Ed Greshko wrote:
I see. It has been a long time since I've used a wired PS2 keyboard.
However, when I had a RHELv4 system with a wired PS2 keyboard I noticed that
the keyboard would become non-responsive if it were unplugged/plugged. The X
server would lose
On 10/10/2012 06:35:58 PM, Kevin Fenzi wrote:
On Wed, 10 Oct 2012 18:05:07 -0700
Paul Allen Newell pnew...@cs.cmu.edu wrote:
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
Joe Zeff wrote:
On 10/10/2012 06:43 PM, Ed Greshko wrote:
I see. It has been a long time since I've used a wired PS2
keyboard. However, when I had a RHELv4 system with a wired PS2
keyboard I noticed that the keyboard would become non-responsive if it
were unplugged/plugged. The X
On Wed, 10 Oct 2012 19:30:28 -0700
Geoffrey Leach ge...@hughes.net wrote:
On 10/10/2012 06:35:58 PM, Kevin Fenzi wrote:
On Wed, 10 Oct 2012 18:05:07 -0700
Paul Allen Newell pnew...@cs.cmu.edu wrote:
Given the fact that I was able to type once I selected New login
on the locked
On 10/10/2012 6:35 PM, Kevin Fenzi wrote:
When this happens, can you try holding down the shift key for say
15-20seconds? Do you see a notice then about 'slow keys' being disabled
and it starts working again?
kevin
Kevin:
Of course, it decided to work for a long time so I was unable to try
On 10/10/2012 6:43 PM, Ed Greshko wrote:
I see. It has been a long time since I've used a wired PS2 keyboard.
However, when I had a RHELv4 system with a wired PS2 keyboard I noticed that
the keyboard would become non-responsive if it were unplugged/plugged. The X
server would lose
On 10/10/2012 7:30 PM, Geoffrey Leach wrote:
This would appear to be an instance of a fairly well documented
problem. Bugzilla # 816764. If holding down the shift key does not
work, try toggling Slow Keys in Settings-Accessibility. I've found
that toggle followed by the shift key usually works.
On 10/11/2012 01:32 PM, Paul Allen Newell wrote:
On 10/10/2012 6:43 PM, Ed Greshko wrote:
I see. It has been a long time since I've used a wired PS2 keyboard.
However, when I had a RHELv4 system with a wired PS2 keyboard I noticed that
the keyboard would become non-responsive if it
On 10/10/2012 8:20 PM, Frantisek Hanzlik wrote:
It was discused here somtimes about 27.-28.8., You can search 'dead
keyboard' in list archive. It is probably some X server problem.
Frantisek:
Thanks for info. I've found the post and will check it out once I have
coffee in the morning (my
On 10/10/2012 10:36 PM, Ed Greshko wrote:
OK I should have pointed out that I am speculating you *may* have a wonky
wire or connection which results in a momentary disconnect. I've had several
of these over they years. All caused by cats either gnawing on cables or
ripping them out
45 matches
Mail list logo
