[opensuse-factory] [Beta 1]keyboard is broken
Hi, I did a fresh install of Beta 1 on physical machine, which is a Thinkpad T61 box, and installl a NVIDIA 313.18 proprietary driver from their website. Here're some details: KDE: 4.9.97 X11: 1.5.0 Locale: zh_CN.UTF-8 And I found my keyboard is broken: 1. The PrintScreen/Left/Right/Down keys are disfuntional (maybe there're still more, but I didn't try yet), and the Up key becomes PrintScreen. Everytime in a konsole I need to auto input last command, ksnapshot comes out. I set keyboard model in [System Settings] - [Input Device] to T61, then PrintScreen key is back, but the four direction keys are still broken. What's more, the next time I boot, the keyboard model is still T61, but PrintScreen and Up key switch again! 2. The PgUp key turns to be "/", and the PgDn key turns to be a right click All happens in KDE 4.10, in getty and windows they're all functional. So it can't be my physical keyboard. And sadly I can't find anything useful in Xorg.0.log and messages(journalctl), there're even no relevant errors. Can anyone give me some hints how can I debug such problem or find potential causes of such cases so that I can open a bug report for the right guys? Thanks Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I guess this problem is a bug of fcitx's xkb module. It also reproduces on 12.2 with fcitx-4.2.7 from M17N. I noticed yesterday (and tweeted) after updating fcitx but have not filed a report yet. BTW please remove xdg/autostart/fcitx-autostart.desktop when you fix the package. Fcitx always change key map wrongly while its start up even if I uses ibus. CSSlayer, here is output of "setxkbmap --print" on my machine. xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete+japan" }; xkb_symbols { include "pc+jp+inet(evdev)+terminate(ctrl_alt_bksp)+ctrl(nocaps)" }; xkb_geometry { include "pc(pc104)" }; }; Fuminobu TAKEYAMA (2013/01/30 20:27), Marguerite Su wrote:
Hi,
I did a fresh install of Beta 1 on physical machine, which is a Thinkpad T61 box, and installl a NVIDIA 313.18 proprietary driver from their website.
Here're some details:
KDE: 4.9.97 X11: 1.5.0 Locale: zh_CN.UTF-8
And I found my keyboard is broken:
1. The PrintScreen/Left/Right/Down keys are disfuntional (maybe there're still more, but I didn't try yet), and the Up key becomes PrintScreen. Everytime in a konsole I need to auto input last command, ksnapshot comes out.
I set keyboard model in [System Settings] - [Input Device] to T61, then PrintScreen key is back, but the four direction keys are still broken. What's more, the next time I boot, the keyboard model is still T61, but PrintScreen and Up key switch again!
2. The PgUp key turns to be "/", and the PgDn key turns to be a right click
All happens in KDE 4.10, in getty and windows they're all functional. So it can't be my physical keyboard. And sadly I can't find anything useful in Xorg.0.log and messages(journalctl), there're even no relevant errors.
Can anyone give me some hints how can I debug such problem or find potential causes of such cases so that I can open a bug report for the right guys?
Thanks
Marguerite
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Jan 30, 2013 at 7:57 PM, Fuminobu TAKEYAMA <ftake@geeko.jp> wrote:
I guess this problem is a bug of fcitx's xkb module. It also reproduces on 12.2 with fcitx-4.2.7 from M17N.
Nice! A user also said it's fcitx in openSUSE SC group on G+, and I didn't check his fcitx version yet. seems I have to open a bug report for myself...embarrassed
I noticed yesterday (and tweeted) after updating fcitx but have not filed a report yet.
I want to follow you on twitter please..
BTW please remove xdg/autostart/fcitx-autostart.desktop when you fix the package.
seems this one is not for our distribution but for fedora or ubuntu. we use xim.d script written by me...a hidden packaging flaw/conflict, sorry.
Fcitx always change key map wrongly while its start up even if I uses ibus.
CSSlayer, here is output of "setxkbmap --print" on my machine.
xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete+japan" }; xkb_symbols { include "pc+jp+inet(evdev)+terminate(ctrl_alt_bksp)+ctrl(nocaps)" }; xkb_geometry { include "pc(pc104)" }; };
mine: marguerite@linux-sclt /usr/bin : setxkbmap -print xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+us+inet(evdev)+terminate(ctrl_alt_bksp)" }; xkb_geometry { include "thinkpad(60)" }; }; please eliminate it after you get up. Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Jan 30, 2013 at 7:57 PM, Fuminobu TAKEYAMA <ftake@geeko.jp> wrote:
I guess this problem is a bug of fcitx's xkb module. It also reproduces on 12.2 with fcitx-4.2.7 from M17N.
Hi, ftake... This is an openSUSE specific bug triggered by our `%fdupes -s $RPM_BUILD_ROOT/usr/share/X11/xkb` in the spec file of xkeyboard-config package. Other distributions (Chakra/Arch/Ubuntu/Debian/Fedora) didn't use symlink on such rule files, so fcitx guys thought this place is solid, then a 4.2.6 -> 4.2.7 code change lands on water. I'll submit some fixes tomorrow. Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Fuminobu TAKEYAMA -
Marguerite Su