Red Hat Bugzilla – Bug 106024
KDGKBLED: Invalid Argument Error reading current flags setting
Last modified: 2007-04-18 12:58:03 EDT
Description of problem:
Error message appears in Shell Konsole whenever shell is opened using Ctrl-T
from Konqueror or from START==>System Tools==>Terminal. The error message
is "KDGKBLED: Invalid Argument Error reading current flags setting. Maybe you
are not on the console?"
Version-Release number of selected component (if applicable):
Red Hat 9, Konsole 1.2(Using KDE 3.1-10 Red Hat)
Happens every time Konsole is opened. Happened after Numlock setting was
changed using START==>Control Center==>Peripherals==>Keyboard==>Change "Numlock
on KDE Startup" to "Turn on". Went back and changed setting to "Leave
unchanged", but problem persists each time Konsole Shell is opened.
Steps to Reproduce:
1. Change Numlock setting using START==>Control
Center==>Peripherals==>Keyboard==>change "Numlock on KDE Startup" to "Turn
2. Open a Terminal using Ctrl-T from Konqueror, or from START==>System
Tools==>Terminal. After Konsole Shell is open, the su command generates the
error and then exit generates the error again.
Actual results: Konsole Shell opens and displays the message:
"KDGKBLED: Invalid Argument Error reading current flags setting. Maybe you are
not on the console?"
Expected results: Konsole Shell should open without this error message.
Additional info: Changing the Numlock also causes an informational error
message about the Sound, but this went away by setting the Numlock back to
default settings using Control Center.
changing to proper component
This bug is reported against old release of Red Hat Linux or Fedora Core
that is no longer supported. Chances are that it has been already fixed in
newer Fedora Core release. If you still experience the problem with
current release of Fedora Core, please update the Version field (you may
need to switch Product to Fedora Core first) in the bug report and put it
back to NEW state.
Red Hat Linux is no longer supported by Red Hat, Inc. If you are still
running Red Hat Linux, you are strongly advised to upgrade to a
current Fedora Core release or Red Hat Enterprise Linux or comparable.
Some information on which option may be right for you is available at
Red Hat apologizes that these issues have not been resolved yet. We do
want to make sure that no important bugs slip through the cracks.
If this issue is still present in a current Fedora Core release, please
open a new bug with the relevant information.
Closing as CANTFIX.