It causes X to fail on startup. my xorg configuration works with X11R7 running evdev 1.0 but version of 1.1 cause it to crash.
Could you please give your xorg.conf and /var/log/Xorg.0.log? Thank you.
Created attachment 5807 [details] Log that shows bug. In make.conf, all there is in the inputdevice section is: Identifier "Mouse0" Driver "evdev" Option "Device" "/dev/input/event0"
Created attachment 5808 [details] Log that shows error Sorry, that last one was with the nvidia driver loaded. This is with nv.
(In reply to comment #2) > Created an attachment (id=5807) [edit] > Log that shows bug. > > In make.conf, all there is in the inputdevice section is: > > Identifier "Mouse0" > Driver "evdev" > Option "Device" "/dev/input/event0" Your full xorg.conf please.
The contents of /proc/bus/input/devices might also be useful.
Created attachment 5810 [details] Xorg.conf My xorg.conf(.new, right now I'm using the "mouse" driver)
Section "InputDevice" Identifier "Mouse0" Driver "evdev" Option "Device" "/dev/input/event0" EndSection Using nothing but the 'Device' specification is, at best, somewhat unwise, and in this case it seems to be getting the wrong device. Please try the generic mouse entry from the manpage, or alternatively specifying by name or one of the other specifiers.
Created attachment 5811 [details] original bug submitters xorg.con hmmm... seems my bug has gotten away from me here's my xorg.conf. I needed to get a new xorg.0.log so I left my computer compiling 7.1 last night. I'll attach that in a minute.
Sorry, it was trouble on my end. /dev/input/event0 was the keyboard, and /dev/input/event1 (the mouse) was being named /dev/input/mx1000 thanks to udev... It works fine now. The guy who opened this bug might want to look at his udev rules. I tried specifying it using Option "Name", but that didn't work. I: Bus=0003 Vendor=046d Product=c50e Version=2500 N: Name="Logitech USB Receiver" P: Phys=usb-0000:00:02.1-3/input0 Putting in Option "Name" "Logitech USB Receiver" didn't work, but that may well be due to /dev/input/event1 being missing...
(In reply to comment #9) > Sorry, it was trouble on my end. > > /dev/input/event0 was the keyboard, and /dev/input/event1 (the mouse) was being > named /dev/input/mx1000 thanks to udev... Yeah, that's the problem. Remove the broken udev rule and specify by name should work fine. Reopen the bug if that doesn't solve stuff. Zephaniah E. hull.
Created attachment 5812 [details] orignal submitters xorg.0.log this is my log.
HEY this was MY bug... and I know that what I have wasn't pointing to the wrong place so unless you guys want me to open another one because mine got comandeered. I've now got mine attached. and verified that my xorg.conf works with X11R7.0 but not 7.1
(In reply to comment #12) > HEY this was MY bug... and I know that what I have wasn't pointing to the wrong > place so unless you guys want me to open another one because mine got > comandeered. I've now got mine attached. and verified that my xorg.conf works > with X11R7.0 but not 7.1 Oh, er, sorry. Could I get your /proc/bus/input/devices and xorg.conf as well? Thanks.
I: Bus=0003 Vendor=046d Product=c70e Version=4000 N: Name="Logitech Logitech BT Mini-Receiver" P: Phys=usb-0000:00:02.0-4.2/input0 S: Sysfs=/class/input/input0 H: Handlers=kbd event0 B: EV=120003 B: KEY=10000 7 ff800000 7ff febeffdf ffefffff ffffffff fffffffe B: LED=1f I: Bus=0003 Vendor=046d Product=c70a Version=4000 N: Name="Logitech Logitech BT Mini-Receiver" P: Phys=usb-0000:00:02.0-4.3/input0 S: Sysfs=/class/input/input1 H: Handlers=kbd mouse0 event1 B: EV=f B: KEY=c0002 400 0 0 fff0001 f80 78000 6639fa d841d7ad 9e0000 0 0 0 B: REL=1c3 B: ABS=1 0 I attached my xorg.conf and xorg.0.log under "original submitters" they're up there
are you still needing some kind of info from me?
say what info is needed?
hmm... if no response on this within 2 days I'm closing and opening a new bug.
Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status. Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.