Hide Forgot
my mouse doesn't move in f15. If I move it, the light inside it wakes up, but it seems X doesn't notice. Interesting part of the X log.. [ 12.386] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE) [ 12.386] (II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes. [ 12.386] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1 [ 12.386] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0 [ 12.386] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000 [ 12.386] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4 [ 12.386] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0) [ 12.386] (II) No input driver/identifier specified (ignoring)
Created attachment 479406 [details] complete X log
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Do you have any configuration file in /etc/X11/xorg.conf.d/? Please, attach them to this bug report as individual uncompressed file attachments using the bugzilla file attachment link above. Also, please, install evtest (from package evtest) and give un output of evtest /dev/input/mouse0 We will review this issue again once you've had a chance to attach this information. Thanks in advance.
This happens during installation, so I don't have anything in xorg.conf etc. The tree is currently uninstallable (and has been for a while) for me, so I can't even manage a text mode install to install evtest.
Could we get at least /var/log/Xorg.0.log and output of dmesg, please?
the log is attached in comment 1.
Created attachment 483802 [details] dmesg
Is this still an issue?(In reply to comment #0) > Interesting part of the X log.. > [ 12.386] (II) config/udev: Adding input device Logitech USB-PS/2 Optical > Mouse (/dev/input/mouse0) > [ 12.386] (II) No input driver/identifier specified (ignoring) This isn't an error, we just ignore mouseX devices since we already hook onto eventX. Is this bug still an issue?
I can't remember which machine I saw this on, but none of the ones I currently use have this issue, so lets call it fixed and move on :)