I'm unsure if this is a duplicate of #129793. When I boot my machine and X fires up, the keyboard works. After some seconds, the keyboard doesn't work anymore. I use the entrance dm, but I suspect it is related to that, as the keyboard is lost even if I login fast enough and my wm (enlightenment-0.16.7.2 - I know it is outdated, but I had some problems with the newer versions) starts, the keyboard is lost, too. Something seems to steal the keyboard: if I change to console and /etc/init.d/xdm restart, everything works fine. I narrowed it down by changing /etc/init.d/xdm so that it starts right after local, which limits the the time the keyboard is working to essentially zero. emerge --info: Portage 2.1-r1 (!/usr/portage/profiles/default-linux/amd64/2005.0, gcc-3.4.5, glibc-2.3.6-r3, 2.6.15-gentoo-r1 x86_64) ================================================================= System uname: 2.6.15-gentoo-r1 x86_64 AMD Athlon(tm) 64 Processor 2800+ Gentoo Base System version 1.6.15 ccache version 2.3 [enabled] dev-lang/python: 2.3.5-r2 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.3 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r2 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O3 -pipe -fomit-frame-pointer -mfpmath=sse -msse2 -mmmx -m3dnow" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/share/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=athlon64 -O3 -pipe -fomit-frame-pointer -mfpmath=sse -msse2 -mmmx -m3dnow" DISTDIR="/var/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.join.uni-muenster.de/pub/linux/distributions/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo" LANG="de_DE.utf8" LC_ALL="de_DE.utf8" LDFLAGS="-Wl,-O1" LINGUAS="de" MAKEOPTS="-j2" PKGDIR="/var/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/var/portage" PORTDIR_OVERLAY="/usr/local/gentoo-de /usr/local/my_portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac alsa avi bash-completion berkdb bzip2 cdr crypt cups divx4linux dvd dvdr encode escreen fam flac foomaticdb fortran ftp gdbm gif gpm gtk gtk2 imlib java jpeg jpeg2k libg++ libwww mad matroska mikmod mng motif mozsvg mpeg mysql ncurses nls nptl nptlonly ogg oggvorbis openal opengl pam pdflib php phyton png quicktime readline samba sdl slang speex spell ssl svg tcpd theora tiff truetype unicode usb vorbis xml2 xmms xv xvid zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux linguas_de userland_GNU video_cards_nv" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, PORTAGE_RSYNC_EXTRA_OPTS
Do you have any commands in /etc/conf.d/local.start that could be stealing the keyboard? Starting after local means all the other init scripts have already started, so they can't be to blame. If you're using parallel startup (RC_PARALLEL_STARTUP in /etc/conf.d/rc), could you disable it?
(In reply to comment #1) > Do you have any commands in /etc/conf.d/local.start Yes, basically a fortune cookie piped to cowsay :) > that could be stealing the > keyboard? Well, I suppose this is not the reason. I commented it out, same result. > Starting after local means all the other init scripts have already > started, so they can't be to blame. Right, that's the part where my understanding ends. But: I really meant _after_ local, so even local was already done. I.e., I started xdm as the very last (because that is, iirc, the way it worked before update to xorg7). > If you're using parallel startup > (RC_PARALLEL_STARTUP in /etc/conf.d/rc), could you disable it? > I don't do so. Just as another information, I (sadly) use the proprietary nvidia driver. (I'd really like to use nv, but it doesn't seem to work together with my three grafic cards (cannot read V_BIOS - I found lot's of problem reports but no fix).)
(In reply to comment #2) > Just as another information, I (sadly) use the proprietary nvidia > driver. (I'd really like to use nv, but it doesn't seem to work together > with my three grafic cards (cannot read V_BIOS - I found lot's of > problem reports but no fix).) The V_BIOS thing should be fixed as of xorg-server-1.0.2-r7 (the one that was marked stable). It was broken in -r6, if you were previously using modular X on ~arch. Since you're using binary drivers, I'm going to reassign your bug.
I've had issues like this before. It's basically your X starting too soon and one of the console's grabbing the keyboard input. Oddly enough if you type your username [enter] password [enter], you'll be dumped at a console that just logged in. X will restart on vt7 and everything will be fine and dandy. I talked with you about this before Donnie and we debugged the issue and fixed it. I forget what it was. I remember one of the needed steps was I needed to rebuild my initramfs for some reason. But it definitely was not an nvidia-drivers issue.
You could try making sure you have the latest xinit and run etc-update. This will ensure that the xdm init script (provided by xinit) has all the required dependencies.
Please reopen when you confirm you've done as I suggested in the above comment.