Summary: | Extremely annoying sticky keys in X.org behavior libxtst | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefan de Konink <stefan> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | stefan |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://bugs.freedesktop.org/show_bug.cgi?id=25480 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
My xorg
Xorg.0.log |
Description
Stefan de Konink
2009-11-08 22:56:49 UTC
Probably your configuration error. What are your input configuration settings ? Not changed since installation: Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "stylus" "SendCoreEvents" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbLayout" "dvorak" EndSection Section "InputDevice" Identifier "stylus" Driver "wacom" Option "Device" "/dev/input/tablet-volito" # USB ONLY Option "Type" "stylus" Option "USB" "on" # USB ONLY Option "Capacity" "5" Option "PressCurve" "0,5,95,100" # Option "Twinview" "horizontal" Option "ScreenNo" "0" Option "Threshold" "10" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection So it's probably overdue for a change/update. On minor note: 'dvorak' is a variant, not a layout. What's your xorg-server ? If that's your full xorg-conf (next time - attach), you're probably using hal for xorg input settings, so you need to set up things correctly there. It's quite simple, actually. (In reply to comment #3) > So it's probably overdue for a change/update. > > On minor note: 'dvorak' is a variant, not a layout. Changed, doesn't have any influence what so ever. After one day, the bug was still present last night. > What's your xorg-server ? X.Org X Server 1.7.1 Release Date: 2009-10-23 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.30-gentoo-r1 x86_64 Current Operating System: Linux nemesis 2.6.30-gentoo-r1 #2 SMP PREEMPT Sat Aug 15 16:34:20 CEST 2009 x86_64 Kernel command line: Build Date: 05 November 2009 06:56:00PM Created attachment 209918 [details]
My xorg
Does paludis have an output, that provides as much environment info as portage does ? Anyway, while bugzilla is not a support forum... - what x11-drivers you've got installed ? - attach your xorg.log - did you read the upgrade guides (to 1.5, specifically) ? I rather would calling 'sudden' stickykey behavior while not having it enabled at all a feature. Hence a 'bug'. * x11-drivers/xf86-input-keyboard [R 1.4.0] <target> * x11-drivers/xf86-input-mouse [R 1.5.0] <target> * x11-drivers/xf86-input-evdev [R 2.3.0] <target> I have upgraded to 1.5 a /long/ time ago. This behavior started this week. I find it difficult to see the relation. ACCEPT_KEYWORDS=amd64 CBUILD=x86_64-pc-linux-gnu CFLAGS=-march=athlon64 -O2 -pipe -msse3 CHOST=x86_64-pc-linux-gnu CONFIG_PROTECT= CONFIG_PROTECT_MASK= CPPFLAGS= CTARGET= CXXFLAGS=-march=athlon64 -O2 -pipe -msse3 DISTDIR=/usr/portage/distfiles FEATURES= FFLAGS= GENTOO_MIRRORS= INSTALL_MASK= LANG= LC_ALL=C LDFLAGS=-Wl,-O1 LINGUAS=nl MAKEOPTS= PORTAGE_COMPRESS= PORTAGE_COMPRESS_FLAGS= PORTAGE_CONFIGROOT= PORTAGE_RSYNC_EXTRA_OPTS= PORTAGE_RSYNC_OPTS= PORTAGE_TMPDIR=/var/tmp/paludis PORTDIR=/usr/portage PORTDIR_OVERLAY= SYNC= USE=amd64 alsa_cards_bt87x alsa_cards_ca0106 alsa_cards_hda-intel alsa_cards_intel8x0 alsa_pcm_plugins_adpcm alsa_pcm_plugins_alaw alsa_pcm_plugins_asym alsa_pcm_plugins_copy alsa_pcm_plugins_dmix alsa_pcm_plugins_dshare alsa_pcm_plugins_dsnoop alsa_pcm_plugins_empty alsa_pcm_plugins_extplug alsa_pcm_plugins_file alsa_pcm_plugins_hooks alsa_pcm_plugins_iec958 alsa_pcm_plugins_ioplug alsa_pcm_plugins_ladspa alsa_pcm_plugins_lfloat alsa_pcm_plugins_linear alsa_pcm_plugins_meter alsa_pcm_plugins_mmap_emul alsa_pcm_plugins_mulaw alsa_pcm_plugins_multi alsa_pcm_plugins_null alsa_pcm_plugins_plug alsa_pcm_plugins_rate alsa_pcm_plugins_route alsa_pcm_plugins_share alsa_pcm_plugins_shm alsa_pcm_plugins_softvol apache2_modules_actions apache2_modules_alias apache2_modules_auth_basic apache2_modules_authn_alias apache2_modules_authn_anon apache2_modules_authn_dbm apache2_modules_authn_default apache2_modules_authn_file apache2_modules_authz_dbm apache2_modules_authz_default apache2_modules_authz_groupfile apache2_modules_authz_host apache2_modules_authz_owner apache2_modules_authz_user apache2_modules_autoindex apache2_modules_cache apache2_modules_dav apache2_modules_dav_fs apache2_modules_dav_lock apache2_modules_deflate apache2_modules_dir apache2_modules_disk_cache apache2_modules_env apache2_modules_expires apache2_modules_ext_filter apache2_modules_file_cache apache2_modules_filter apache2_modules_headers apache2_modules_include apache2_modules_info apache2_modules_log_config apache2_modules_logio apache2_modules_mem_cache apache2_modules_mime apache2_modules_mime_magic apache2_modules_negotiation apache2_modules_rewrite apache2_modules_setenvif apache2_modules_speling apache2_modules_status apache2_modules_unique_id apache2_modules_userdir apache2_modules_usertrack apache2_modules_vhost_alias cameras_nikon cameras_ptp2 elibc_glibc input_devices_evdev input_devices_hyperpen input_devices_keyboard input_devices_mouse input_devices_wacom kernel_linux lcd_devices_bayrad lcd_devices_cfontz lcd_devices_cfontz633 lcd_devices_glk lcd_devices_hd44780 lcd_devices_lb216 lcd_devices_lcdm001 lcd_devices_mtxorb lcd_devices_ncurses lcd_devices_text linguas_nl userland_GNU video_cards_none video_cards_nouveau video_cards_nv video_cards_nvidia video_cards_v4l amd64 Created attachment 209932 [details]
Xorg.0.log
According to the log, you didn't change it - Option "xkb_layout" "dvorak" I'm not completely sure, but I think recent xorg server simply became more strict about what it accepts. As 'dvorak' is not a layout... Could you clean up your xorg.conf a bit - comment out those lines that lead to "Module doesn't exist" lines ? (though strange dri and dri2 are among them - though that may be because of nvidia) You may also notice, that wacom wasn't rebuilt. Note, that now it's not x11-drivers/linuxwacom, but x11-drivers/xf86-input-wacom. Will do; regarding to the dvorak part. I found that I still have an 10-x11-input.fdi <?xml version="1.0" encoding="utf-8"?> <deviceinfo version="0.2"> <match key="info.capabilities" contains="input.keys"> <merge key="input.xkb.layout" type="string">dvorak</merge> </match> </deviceinfo> So I changed it there to variant too. While it probably doesn't really hurt, change those keys to the new style, i.e. from input.xkb.layout to input.x11_options.XkbLayout. Also try using the evdev driver instead of the old keyboard one. It's a miracle it managed to work for so long. Thanks (In reply to comment #12) > Also try using the evdev driver instead of the old keyboard one. It's a miracle > it managed to work for so long. evdev checked too... still gives me the pain. Upgraded to 2.6.32; Section "InputDevice" Identifier "Keyboard0" Driver "evdev" Option "XkbVariant" "dvorak" Option "Device" "/dev/input/by-path/platform-i8042-serio-kbd" EndSection ...still it is bugging me Found this is not uncommon: http://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg85076.html Most likely the same issue in Ubuntu; https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/213669 Could you try booting with acpi=off and see if that has any effect? Some people with the stuck key symptom seem to be having acpi issues that somehow mess up key release events http://bugzilla.kernel.org/show_bug.cgi?id=9147 (In reply to comment #17) > Could you try booting with acpi=off and see if that has any effect? Some people > with the stuck key symptom seem to be having acpi issues that somehow mess up > key release events > http://bugzilla.kernel.org/show_bug.cgi?id=9147 With acpi=off my SATA disks are not recognised... Well that's no fun. How about building in the ACPI modules, which helped one of the commentors on the kernel bug? i8042.noacpi=1 I'm going to try that first, the interesting thing is that I know the keyboard module itself has some very strange wows too. For example using the Xen hypervisor and 64GB of memory that module alone kills an entire boot sequence. This bug is related to libXtst, when uninstalled everything works. |