mouse is not working after upgrading to hardy

Bug #183869 reported by Mathias Kende
4
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Hello,

I upgraded to Hardy two days ago. And among many I found one serious bug that have not been reported to my knowledge : after upgrading my mouse was not working anymore. I tried with a normal PS/2 mouse and with a logitech USB mouse and neither did work.

I read that the new Xorg could find mouse on its own so I commented out all the "InputDevice" in xorg.conf and, after rebooting the X server, my mouse was working again.

here is the output of uname -a :
Linux MATHIAS-ENS 2.6.24-4-generic #1 SMP Mon Jan 14 18:19:11 UTC 2008 x86_64 GNU/Linux

If you need more information, please let me know.

Tags: gutsy2hardy
Revision history for this message
Mathias Kende (mathias-kende) wrote :

Here is my xorg.conf file

Revision history for this message
Lambros Lambrou (lambros) wrote :

I have also run into this problem, after upgrading to Hardy from a fresh installation of Gutsy (64-bit). The mouse is completely unresponsive.

Interesting to know that getting rid of the "InputDevice" sections cures the problem - I will give that a try.

FYI, here is part of my Xorg.0.log file:

(**) Option "Protocol" "10 xserver-xorg/config/inputdevice/mouse/protocol doesn't exist"
(EE) Configured Mouse: Unknown protocol "10 xserver-xorg/config/inputdevice/mouse/protocol doesn't exist"
(EE) PreInit failed for input device "Configured Mouse"
(II) UnloadModule: "mouse"
Atom 4, CARD32 4, unsigned long 8

Revision history for this message
Saivann Carignan (oxmosys) wrote :

This makes a lot of sense since the new Xorg release is almost all automatic and does not use static values in /etc/X11/xorg.conf . Since it is confirmed by two people and that it can have a pretty bad impact on a large portion of ubuntu users, I set the Importance to High.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Lambros: your bug is fixed and not related.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.