Bug#349586: evdev locks my machine

2006-01-29 Thread Harald Dunkel
Hi Juergen, Juergen Kreileder wrote: > > You probably gave a non-existant sysfs path to the command (see /sys). > Yes, that was a typo. udevinfo should print some error message, like "no such entry in database". I did not try your suggested udev config change, though. I am back to the old mous

Bug#349586: evdev locks my machine

2006-01-29 Thread Juergen Kreileder
Harald Dunkel <[EMAIL PROTECTED]> writes: > Juergen Kreileder wrote: >> >> , >> | ACTION=="add", \ >> | KERNEL=="event*", \ >> | SUBSYSTEM=="input", \ >> | SYSFS{manufacturer}=="Logitech", \ >> | SYSFS{product}=="USB Receiver", \ >> | NAME="input/mx1000" >> ` >> >> for my MX1000.

Bug#349586: evdev locks my machine

2006-01-26 Thread Harald Dunkel
Hi Juergen, Juergen Kreileder wrote: > > , > | ACTION=="add", \ > | KERNEL=="event*", \ > | SUBSYSTEM=="input", \ > | SYSFS{manufacturer}=="Logitech", \ > | SYSFS{product}=="USB Receiver", \ > | NAME="input/mx1000" > ` > > for my MX1000. > This looks very good, but ... > You

Bug#349586: evdev locks my machine

2006-01-25 Thread Michel Dänzer
On Wed, 2006-01-25 at 07:39 +0100, Harald Dunkel wrote: > Daniel Stone wrote: > > On Tue, Jan 24, 2006 at 07:40:09AM +0100, Harald Dunkel wrote: > > > 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 seve

Bug#349586: evdev locks my machine

2006-01-24 Thread Harald Dunkel
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 _n

Bug#349586: evdev locks my machine

2006-01-24 Thread Juergen Kreileder
Harald Dunkel <[EMAIL PROTECTED]> writes: > On the next reboot you might get /dev/input/event(n+1), Write an udev rule for the device. I'm using , | ACTION=="add", \ | KERNEL=="event*", \ | SUBSYSTEM=="input", \ | SYSFS{manufacturer}=="Logitech", \ | SYSFS{product}=="USB Receiver",

Bug#349586: evdev locks my machine

2006-01-23 Thread Daniel Stone
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

Bug#349586: evdev locks my machine

2006-01-23 Thread Harald Dunkel
Jeremy Nickurak wrote: > On Mon, 2006-01-23 at 22:25 +0100, Harald Dunkel wrote: > >>If I start X without fixing xorg.conf, then my machine >>gets stuck completely. All I can do is to press the reset >>button. > > > Dupe of #347681, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347681 > Sor

Bug#349586: evdev locks my machine

2006-01-23 Thread Jeremy Nickurak
On Mon, 2006-01-23 at 22:25 +0100, Harald Dunkel wrote: > If I start X without fixing xorg.conf, then my machine > gets stuck completely. All I can do is to press the reset > button. Dupe of #347681, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347681 -- To UNSUBSCRIBE, email to [EMAIL PROT

Bug#349586: evdev locks my machine

2006-01-23 Thread Harald Dunkel
Package: xserver-xorg Version: 6.9.0.dfsg.1-4 severity: serious I don't know how to reproduce it, but sometimes after the next boot my mouse seems to be connected to /dev/input/event2 instead of the /dev/input/event1 configured in xorg.conf (or vice versa). If I start X without fixing xorg.conf,