*** This bug is a duplicate of bug 41427 ***
https://bugs.launchpad.net/bugs/41427
I had this issue with my keyboard not working, and I read this bug report and
thought that this was it - but no! Although it gave me some clues.
What happenden to me was that NUMLOCK was turned on (!!!) the
*** This bug is a duplicate of bug 41427 ***
https://bugs.launchpad.net/bugs/41427
** This bug has been marked a duplicate of bug 41427
slow keys can turn on surreptitiously cause confusion.
--
keyboard not working after logging in via gdm due toslow keys feature being
accidentally
Bryce: I suppose it's plausible the slow keys feature was the reason,
although I as I said in the original report, this was related to playing
with upstart/sysvinit. I'm pretty certain I didn't visit the slow keys
dialog box, but at this point, three Ubuntu releases later, I can't
really confirm
I just tried it again, and I think I've found the underlying issue. As I
disabled the option 'Keyboard Preferences' - 'Allow to turn
accessibility features on and off from the keyboard', I had to
reactivate this to test it.
As I now know, the required action is to hold SHIFT for 8 seconds to
my keyboard recently stopped working after logging in. I will check
whether it is an accessibility feature and report back. The keyboard
behavior may be the result of a properly functioning feature, but the
lack of any communication/notification to the user that the feature is
active is
confirming that it was indeed that accessibility features had somehow
been silently enabled. phew!! thanks for your help! this definitely
needs better notification!
--
keyboard not working after logging in via gdm
https://bugs.launchpad.net/bugs/59616
You received this bug notification
Thanks Miguel, Martin, and ethanay for identifying and confirming the
problem is with the slow keys accessibility feature; I've updated the
title. @Juri, if you're still tracking this bug it would be helpful if
you concur with this analysis.
Could someone propose what the next step should be for
I just had the same problem and I can confirm that the slow keys
feature was the reason for this. As the option Allow to turn on
accessibility features on and off from the keyboard was set, I guess I
accidentally enabled it with some obscure key combination (the help
doesn't state which key
I have found the reason for the bug in my machine.
Somehow the slow keys feature of the keyboard was activated. I don't
know how that happened, but that was the reason why disabling the a11y
plugin did work around the problem. Sorry for the noise.
Maybe the rest of the people should recheck
the gnome-control-center task is enough
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Invalid
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
--
keyboard not working after logging
Does disabling the a11y option workaround the issue for other users
having the bug?
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged = Incomplete
--
keyboard not working after logging in via gdm
https://bugs.launchpad.net/bugs/59616
You received this bug notification because
The problem seems related to the a11y plugin. Deactivating it manually
gconftool-2 -s /apps/gnome-settings-daemon/plugins/a11y-keyboard/active
-t bool false
fixes the problem for me. If I reactivate it, the keyboard stops working
again.
HTH.
--
keyboard not working after logging in via gdm
This is happening here too since the latest gnome-settings-daemon
update. In fact, removing gnome-settings-daemon solves the keyboard
problem (dpkg --purge --force-depends gnome-settings-daemon).
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
This is apparently an issue with gnome-settings-daemon, gdm is innocent.
And I have the same problem right now with no clue how to fix it :(((
** Changed in: gnome-control-center (Ubuntu)
Sourcepackagename: gdm = gnome-control-center
Status: New = Triaged
--
keyboard not working after
I also had the same symptoms, under KDE Kubuntu / Gutsy. I could enter my
password at the login screen (kdm?) but by the time the desktop loaded, the
keyboard was non-functional (not even caps-lock toggled the LED), though mouse
was fine.
After lots of trial and error, I narrowed it down to the
I'm having this issue as well, but on Kubuntu Gutsy (32 bit)! I suspect
that it's probably an X thing.
I can also use the keyboard fine for the grub / login / failsafe, but
not at all once I've actually logged in (not even
Ctrl+alt+f1/del/backspace.
Man, it's not easy to debug a problem with no
** Changed in: gdm (Ubuntu)
Importance: Undecided = Low
Status: Needs Info = Unconfirmed
--
keyboard not working after logging in via gdm
https://bugs.launchpad.net/bugs/59616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
This has happened to me on Feisty. It does look like a Gnome issue.
--
keyboard not working after logging in via gdm
https://bugs.launchpad.net/bugs/59616
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I experienced two times the same problem already on my Apple Powerbook.
I could solve it by removing ~/.gconf in my user account, so I do think
it's a gnome problem somewhere.
--
keyboard not working after logging in via gdm
https://bugs.launchpad.net/bugs/59616
You received this bug
Assigning to X Swat people, they surely know some clever questions too.
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) = Ubuntu X SWAT
--
keyboard not working after logging in via gdm
https://launchpad.net/bugs/59616
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I just tried it again, this time I got a different problem:
The system has reached a state where there are no jobs running. A shell
will be spawned so that... etc.
It had got the network connection up, but that was pretty much it. Oh
well, reinstalled sysvinit.
I'm planning on doing a clean
Juri, do you have the issue with an another session or user?
Diego, do you have the issue if you starts gnome-settings-daemon from fluxbox
by example?
--
keyboard not working after logging in via gdm
https://launchpad.net/bugs/59616
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Sorry, I long ago started over with clean preferences.
--
keyboard not working after logging in via gdm
https://launchpad.net/bugs/59616
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I just upgraded to edgy last night/today and my keyboard is no longer
working (at all. no Ctrl+Alt+*, no Num Lock, etc) after I log in through
gdm. It does work in gdm, in gnome fail-safe mode, in fluxbox, and in
gnome for my other user account, but it fails to work in gnome for my
regular user
I should have mentioned that if I later log out of gnome/switch users,
they keyboard starts working again. If I then go back to gnome on my
regular user, it no longer works. etc.
--
keyboard not working after logging in via gdm
https://launchpad.net/bugs/59616
--
ubuntu-bugs mailing list
I've determined that this issue is not related to gdm at all, because it kept
happening when I tried:
As root: /etc/init.d/gdm stop
As user: startx
I also verified that the keyboard does work in gnome for my regular user after
deleting/renaming the following directories:
.gconf, .gconfd,
This could be related to upstart. I have a similar problem, where the
keyboard does not work after the boot process is complete. By logging in
remotely to the computer I shut down GDM and X, and on the VT below
there was a terminal with the text: The system has reached a state
where there are no
Thanks for your bug. If you pick a another session then GNOME (or
Default) from the login screen, do you have the issue too? Looks rather
an xorg issue than a gdm one
** Changed in: gdm (Ubuntu)
Status: Unconfirmed = Needs Info
--
keyboard not working after logging in via gdm
28 matches
Mail list logo
