On Sun, Nov 15, 2015 at 06:07:00PM +0100, Magnus Therning wrote:
On Sun, Nov 15, 2015 at 04:58:27PM +0000, Ben Oliver wrote:
On 15 Nov 2015 4:56 pm, "Magnus Therning" <magnus@therning.org> wrote:
I've just updated a sligtly neglected machine I have (not upgraded since mid-September). Thanks to the [ARA][1] I managed to upgrade it in weekly steps. It all seemed to work fine, and indeed it boots just fine. There's only one little thing that's broken: the mouse buttons don't work.
Yes, it's really only the mouse buttons that don't work. I can move the pointer using the mouse. I can scroll using the scroll wheel.
Starting `xev` I thought I'd have a look at what actually happens:
1. Start `xev`. 2. Move the pointer into the window -> the various events scroll by in the terminal. 3. Press the left mouse button -> no event printed in the terminal. 4. Move the pointer in the window -> no events are printed in the terminal. 5. Change focus to another window using Ctrl-Tab, change back -> movements in the `xev` window once again generate events.
I've tried searching for a solution, but I can't find anything resembling this.
What could be causing this behaviour, and how do I fix it?
Not to be *that* guy, but have you tried another mouse?
Nope, because I don't have access to another mouse here right now.
The mouse worked just fine when I logged in on the system and began the upgrade, so I really did expect it to work fine afterwards too.
I just managed to track down a second mouse, and can confirm that this behaviour occurs with both USB mice, one Microsoft and one HP, and that it occurs both if I connect it via the PS/2 adapter or directly into a USB port. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus There does not now, nor will there ever, exist a programming language in which it is the least bit hard to write bad programs. -- Flon's Axiom