Hello, when i am running Fedora Core 4 with a custom kernel, i get the following errors when logging in as an ordinary user:
Keymap 0: Permission denied Keymap 1: Permission denied Keymap 2: Permission denied KDSKBENT: Operation not permitted loadkeys: could not deallocate keymap 3
Logging in as a root is ok.
Why am i getting these errors? What modules must be compiled in the kernel to get rid of these?
Best regards, Petr Danecek
On Fri, Jun 30, 2006 at 11:33:28AM +0200, Petr Danecek wrote:
Hello, when i am running Fedora Core 4 with a custom kernel, i get the following errors when logging in as an ordinary user:
Keymap 0: Permission denied Keymap 1: Permission denied Keymap 2: Permission denied KDSKBENT: Operation not permitted loadkeys: could not deallocate keymap 3
Logging in as a root is ok.
Why am i getting these errors? What modules must be compiled in the kernel to get rid of these?
Your kbd package needs updating.
Dave
Hi,
Your kbd package needs updating.
Dave
thank you for your response. May I ask you for a little more informative answer? Even if the kbd package needs updating (i will check this right away), everything works fine with the default Fedora kernel. I do not understand why updating from kernel 2.6.11-1.1369_FC4-i686 to linux-2.6.15.7 should result in such a strange behaviour?? Petr
On Fri, Jun 30, 2006 at 09:23:10PM +0200, Petr Danecek wrote:
Hi,
Your kbd package needs updating.
Davethank you for your response. May I ask you for a little more informative answer? Even if the kbd package needs updating (i will check this right away), everything works fine with the default Fedora kernel. I do not understand why updating from kernel 2.6.11-1.1369_FC4-i686 to linux-2.6.15.7 should result in such a strange behaviour??
Because the behaviour changed in 2.6.15. It was a security issue iirc, where a user could program a key to do something after they had logged out. 2.6.15 closed that hole, but broke userspace. Hence, an updated kbd that did things differently was needed.
Dave
Dear Dave, thank you for your advice and explanation. Updating kbd package helped. Petr
On Fri, 2006-06-30 at 15:28 -0400, Dave Jones wrote:
On Fri, Jun 30, 2006 at 09:23:10PM +0200, Petr Danecek wrote:
Hi,
Your kbd package needs updating.
Davethank you for your response. May I ask you for a little more informative answer? Even if the kbd package needs updating (i will check this right away), everything works fine with the default Fedora kernel. I do not understand why updating from kernel 2.6.11-1.1369_FC4-i686 to linux-2.6.15.7 should result in such a strange behaviour??
Because the behaviour changed in 2.6.15. It was a security issue iirc, where a user could program a key to do something after they had logged out. 2.6.15 closed that hole, but broke userspace. Hence, an updated kbd that did things differently was needed.
Dave
-
Dave Jones -
Petr Danecek