My Kubuntu box seems to have developed a strange problem. When I log in via KDM, it gets to the 'Restoring Session' part of start up then the mouse cursor will freeze. If I restart X, the mouse cursor will work again until I log in again! The only way to remedy it is to completey restart the computer. I would say the mouse cursor locks up every 3-5 boot ups.
I've seen other issues like yours, but it turned out to be unrelated to the mouse -- it was a video driver issue in one case, and a chipset driver in another. What are your specs?
Okay guys, I still haven't found a fix for this bizarre behaviour. :x: What program or system service has the power to freeze the mouse cursor? Just to recap, everything else works, the keyboard works, just not the mouse! If I restart X, my mouse comes back to life again. Only when I log in does my mouse freeze up.
It's not a Microsoft mouse is it? In any case try a different mouse, preferably USB, and see if you have the same problem. If a USB mouse fixes it, your motherboard may have a glitchy PS2 implementation.
Nah, I'm pretty sure it's a problem with my Kubuntu configuration. Nevermind, i'll do a quick search on Google. It'd be ashame to re-install Kubuntu just because of this silly mouse problem. As i've said, it works 7/10 times a restart
Things seem to have got worse - the mouse doesn't work at all when I log in now, no matter how many times I restart the computer :x: :x: :x: :x: :x: This is so retarted because I am gonna have to re-install Kubuntu. :swear: This is the sequence of events: 1) Turn on computer and boot into the KDE log in screen (mouse is working at this point) 2) Enter my Username and password and press enter (mouse is still working) 3) The Kubuntu/KDE loading screen appears and the icons slowly light up one by one (mouse is working) 4) Then it gets to the 'Restoring Session' icon and my mouse freezes. 5) KDE fully boots up and my mouse is dead. 6) I log out using the keyboard and go back to the log in screen. My mouse comes back to life! WTF! okay, what actually happens at the 'Restoring Session' part of the login process? Obviously my session has become corrupted some how? Can I delete my session and start a new one? UPDATE: I've finally got in after about 10 attempts. It seems to work if I toggle between the 'Default Session' and the 'KDE Session'. I'm going to have a look in the Kubuntu control centre and see if I can reset my session.
Just because the mouse works well sometimes doesn't mean it's not a glitchy mouse or PS2 port. KDE actually polls for the mouse during the peripherals phase, so that could definately have something to do with it. Like I said, if you have another mouse laying around (preferrably of a different brand) I'd give that a try and see if you have the same problems. If worse comes to worse, a USB mouse is a good trade-up anyway since it has a much higher polling rate than PS2, which is just a round serial port with less pins.
I think i've fixed the problem I manually saved a new session and since I've been using it, everythings been OK. So it looks like my old session became corrupt somehow
An update to the situation: I ended up deleting my .kde directory and starting a brand new KDE session altogether. I lost all of my personal KDE settings, but I'd rather that then have to re-install Kubuntu completely. Anyways, as I was slowly customising KDE, I found the cause of the problem... LIRC. Yup, when I clicked on LIRC my mouse froze. So it was LIRC all along that was causing the problems. It actually makes perfect sense, and I am thinking that there must be a compatibility problem with my Hauppauge remote control and my mouse. Perhaps the 'Event' mapping has changed or something. I've disabled Lirc for the time being, until I find a fix
Just to bring this story to a close - I've found the cause of the Lirc freeze. I have a Saitek joypad which I share around my computers. When I plug it into the computer with Lirc on, the joypad takes the event number of the remote control. This forces the remote control to take on a new event number. So basically, Lirc was trying to use my joypad as the remote control, and just crashed the computer. So I've reconfigured the event number in Lirc to match the new event number of the remote, and bingo! It works
