Bug 190435 - keyboard model does not seems to be set on login
Summary: keyboard model does not seems to be set on login
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keyboard_layout (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Andriy Rysin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-23 12:10 UTC by Nadav Kavalerchik
Modified: 2010-05-12 20:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nadav Kavalerchik 2009-04-23 12:10:47 UTC
Version:           unknown (using 4.2.2 (KDE 4.2.2), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.29-1-amd64

i set keyboard model to hpdv5 and when i press Apply button it works fine
but after a fresh reboot and a new login into kde it does not seem to take
any effect. (it is not set).
if i change somthing (no matter what) and press the Apply button it works fine
(again) but not on its own.
if i use the konsole to issue "setxkbmap -model hpdv5" it works fine too.

i guess the setxkbmap settings from the keyboard layout preferences does not
get issued on kde login ?
Comment 1 Ben Cooksley 2009-04-30 09:24:54 UTC
Reassigning bug
Comment 2 Michael Jansen 2009-05-19 23:52:05 UTC
Hi Andriy

Is it ok to assign those bugs about kcm_keyboard_layout to you?
Comment 3 Andriy Rysin 2009-05-20 00:27:00 UTC
Michael, yes I guess it's mine.

Nadav, do you also use layouts? Are they also not set?
Comment 4 Nadav Kavalerchik 2009-05-20 01:22:00 UTC
i use english (us) and hebrew (il)
switching between them works fine.

but i know the model is not set by trying to use the "End" key on my number "1" keypad keyboard which does not work until i issue "setxkbmap -model hpdv5".

when i open the Keyboard layout settings dialog,
here is what i see in the "command:" text box:
setxkbmap -model hpdv5 -layout us,il -variant ,
Comment 5 Andriy Rysin 2009-05-20 03:37:12 UTC
the keyboard model and layouts are set at the same time so if layouts work ok after login, it means that something is overriding your key maps

do you have any xmodmap files in you home or /etc directories?
Comment 6 Nadav Kavalerchik 2009-05-20 09:45:15 UTC
i used to have only
xmodmap -e "keycode 115 = Meta_L"
xmodmap -e "keycode 174 = XF86AudioLowerVolume"
xmodmap -e "keycode 176 = XF86AudioRaiseVolume"
xmodmap -e "keycode 160 = XF86AudioMute"

in the .kde4/Autostart/setp.sh file that gets executed on kde's startup.

i added :
setxkbmap -model hpdv5
but it does not seem to have any affect. (funny)

plus, here are the errors from .session-errors file in my user's folder:

<unknown program name>(4460)/ kdemain: Xlib XKB extension major= 1  minor= 0
kcminit(4438) KxkbConfig::load: Use kxkb true
kcminit(4438) KxkbConfig::load: Indicator only false
kcminit(4438) KxkbConfig::load: Model: "hpdv5"
kcminit(4438) KxkbConfig::load:  added layout "us"
kcminit(4438) KxkbConfig::load:  added layout "il"
kcminit(4438) KxkbConfig::load: Layout owner mode "Global"
kcminit(4438) KxkbConfig::load: Xkb options: ("grp_led:caps", "lv3:ralt_alt", "altwin:meta_win", "grp:alt_shift_toggle")
kdeinit4: preparing to launch /usr/bin/kxkb
kaccess(4460) kdemain: X server XKB extension major= 1  minor= 0
kdeinit4: preparing to launch /usr/bin/kmixctrl
kdeinit4: preparing to launch /usr/bin/krunner
kxkb(4469) XKBExtension::init: XKB inited
kxkb(4469) X11Helper::registerForNewDeviceEvent: Registered for new device events from XInput, class 114
kxkb(4469) KxkbConfig::load: Use kxkb true
kxkb(4469) KxkbConfig::load: Indicator only false
kxkb(4469) KxkbConfig::load: Model: "hpdv5"
kxkb(4469) KxkbConfig::load:  added layout "us"
kxkb(4469) KxkbConfig::load:  added layout "il"
kxkb(4469) KxkbConfig::load: Layout owner mode "Global"
kxkb(4469) KxkbConfig::load: Xkb options: ("grp_led:caps", "lv3:ralt_alt", "altwin:meta_win", "grp:alt_shift_toggle")
Nepomuk server already running.
kxkb(4469) XKlavierAdaptor::loadXkbConfig: Setting LC_ALL for libxklavier:  "en_US.UTF-8"
kxkb(4469) XKlavierAdaptor::loadXkbConfig: Xklavier initialized
kxkb(4469) XKlavierAdaptor::loadXkbConfig: 83 total layouts 165 models
kxkb(4469) XKBExtension::setLayoutGroups: executing "/usr/bin/setxkbmap -model hpdv5 -layout us,il -variant , -option -option grp_led:caps,lv3:ralt_alt,altwin:meta_win,grp:alt_shift_toggle"
kxkb(4469) KxkbCore::initKDEShortcut: kde shortcut "Ctrl+Alt+K"
kxkb(4469) LayoutMap::getCurrentLayoutQueue: Created queue for  "global"  size:  2
kxkb(4469) LayoutMap::setCurrentLayout: map: Storing layout:  0  for  "global"
kxkb(4469) KxkbCore::initTray: initing tray, visible: true
kmixctrl(4467) Mixer::openIfValid: Mixer::open() detected master:  "PCM:0"
kmixctrl(4467) Mixer::getGlobalMasterMD: Mixer::masterCardDevice() returns 0 (no globalMaster)
kmixctrl(4467) Mixer::setGlobalMaster: Mixer::setGlobalMaster() card= "ALSA::HDA_Intel:1"  control= "PCM:0"
kwin: X Error (error: BadDamage [DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x12001d2)
kxkb(4469) KxkbWidget::setCurrentLayout: setting text:  "us"
QCoreApplication::postEvent: Unexpected null receiver
kxkb(4469) KxkbCore::x11EventFilter: got event: layouts changed
kxkb(4469) KxkbCore::updateGroupsFromServer: updating groups from server
kxkb(4469) XKlavierAdaptor::getGroupNames:  layout nm: "us" variant: ""
kxkb(4469) XKlavierAdaptor::getGroupNames:  layout nm: "il" variant: ""
kxkb(4469) XKlavierAdaptor::getGroupNames:  option: grp_led:caps
kxkb(4469) XKlavierAdaptor::getGroupNames:  option: lv3:ralt_alt
kxkb(4469) XKlavierAdaptor::getGroupNames:  option: altwin:meta_win
kxkb(4469) XKlavierAdaptor::getGroupNames:  option: grp:alt_shift_toggle
kxkb(4469) KxkbCore::updateGroupsFromServer:  active group 0
kxkb(4469) KxkbCore::updateGroupsFromServer:  no change in layouts
kxkb(4469) LayoutMap::setCurrentLayout: map: Storing layout:  0  for  "global"
kxkb(4469) KxkbWidget::setCurrentLayout: setting text:  "us"
Comment 7 Andriy Rysin 2009-05-22 03:47:13 UTC
there's no errors in your log, everything is working fine, and as you pointed the script from Autostart does not hlep, so the only explanation I have is that something is overriding your keyboard bindings, xmodmap is actaully run on every kxkb init (including when you hit Apply button) so it should not be the issue, but you may try to temporarily renmae all xmodmap config files you have
if that does not help you'll have to fine the program which messes with your keys...
Comment 8 Nadav Kavalerchik 2009-05-22 08:42:14 UTC
thanks :-) i will look into it.
Comment 9 Andriy Rysin 2010-05-12 02:29:57 UTC
Is it still a problem?
Comment 10 Nadav Kavalerchik 2010-05-12 20:47:24 UTC
solved. (not sure on which upgrade) 
kde 4.4.3 (debian sid)