Daniel Stone wrote: > On Tue, Jan 24, 2006 at 07:40:09AM +0100, Harald Dunkel wrote: > >>Sorry, but this is not a dup. #347681 talks about typos >>in xorg.conf, i.e. something that can be fixed by somebody >>with write permission to this file. >> >>This bug (#347681) is about something that can _not_ be >>fixed by editing xorg.conf. On the next reboot you might >>get /dev/input/event(n+1), and your machine gets locked >>again. You can't influence this. Its apita. >> >>So please keep these problem reports separate. > > > The hardlock is a valid bug, the rest isn't. Ordering of input devices is not > guaranteed. > I don't want to care about the order of /dev/input/event*, either. But obviously the new evdev can't handle a changed sequence at all. The old one could, i.e. the update broke a working feature. Thats a bug. And it is serious or grave, since it randomly locks up the machine (twice this morning!). Typos in the evdev entry lock up my machine, too, but this is something I have influence upon. So we have 2 separate bugs due to different severity. I would recommend to put the old evdev back. It could distinguish the input ports by deeply looking, and it did not die about typos. Regards Harri
Attachment:
signature.asc
Description: OpenPGP digital signature