[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#423090: xserver-xorg-input-evdev: selecting evdev for keyboard driver crashes



Dne pátek 11 květen 2007 03:25 Brice Goglin napsal(a):
> severity 423090 important
> thank you
>
>
> Please don't use very very high severity without a good reason. Obviously,
> a crash of the X server does not break the whole system. A crash of the X
> server is generally considered "important".
> See http://www.debian.org/Bugs/Developer#severities
>
OK
> > When selecting evdev for keyboard my Xorg crashes and won't start.
>
> It might be related to https://bugs.freedesktop.org/show_bug.cgi?id=5807

Looks same or related to mine.

>
> However, I think I have seen a case where a wrong config of evdev leads
> to a crash of the server. Please check your evdev config for the keyboard.
> The "basic configurations" section of the manpage should help.

Config is OK - I just took it from some inet website and just changed 
vendor/product ids to fit my hw.

>
> > Selecting kbd as driver for keyboard nad evdev for mouse, Xorg starts,
> > but returns wrong keycodes for up key and others. For up key for
> > example returns Print etc.
>
> This looks strange to me. You should be able to use evdev for mouse and
> kbd for keyboard at the same time. I think lots of people are doing so.

I was also thinking this is not problem, but not for my configuration :(

>
> Are you sure that your mouse/evdev Section in xorg.conf is correct?
> If it is wrong, it might be sending random events to the server...
> I am not familiar with evdev config, but I think you need to add
> evBits/relBits/... lines as in the manpage examples.

I don't see any random events in xorg - all buttons works, tilt wheel also 
works and returns 4,5,6,7 scancodes...

>
> > I need evdev driver for mouse, because without it my MX1000 doesn't
> > return 6,7 for tilt wheel.
>
> You might want to look at https://bugs.freedesktop.org/show_bug.cgi?id=5578
> for evdev problems with this mouse.

This is different not related problem

>
> Brice

Michal



Reply to: