Hello, Sorry, nothing new. I can't reproduce this bug at all. Anyway, I'm using input-evdev on one computer, so if bug will appear once again I'll inform you.
В Суб, 21/04/2007 в 02:10 +0200, Brice Goglin пишет: > Alexander Vlasov wrote: > >> Could you try xserver-xorg-input-evdev currently in experimental > >> (1:1.1.5-1)? > >> > > > > Sure. I'll try today and write another followup. > > > > > >> Which xserver-xorg-core are your running ? 2:1.1.1-20 ? Do you see any > >> interesting difference in Xorg.0.log when switching from input+kbd to > >> evdev? > >> > > > > xserver-xorg-core: Version: 2:1.1.1-20 > > xserver-xorg: 1:7.1.0-15 > > it's current etch versions, no updates available. > > Xorg.log surely differs, but nothing seems wrong. Anyway, I'll retry > > this later and attach both logs. > > > > > >>> Without entering to vservers enter key also works ok. > >>> > >>> > >> The bug could be caused by vserver then. I know almost nothing about > >> vserver. Is it supposed to be stable? Do you have a way to disable some > >> vserver features to try to locate the problem more precisely? > >> > > > > Seems so. > > No, I see no ways to disable anything console-related. This problem > > exists even during vserver creation with newvserver. > > > > > >> Thanks, > >> Brice > >> > > > > Not at all. I'll retry both input drivers later and I'll try to > > reproduce this bug on i386 arch. > > > > Hi Alexander, > > Did you find out anything new about this problem? Did you have a chance > to try xserver-xorg-input-evdev currently in experimental (should enter > unstable in a few days since xserver-xorg-core 1.3 arrived yesterday)? > > Thanks, > Brice > >
