[arch-general] Mouse buttons not working in X
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? /M [1]: https://wiki.archlinux.org/index.php/Arch_Linux_Archive -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Goto labels should be left-aligned in all caps and should include the programmer's name, home phone number, and credit card number. -- Abdul Nizar
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?
/M
[1]: https://wiki.archlinux.org/index.php/Arch_Linux_Archive
-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
Goto labels should be left-aligned in all caps and should include the programmer's name, home phone number, and credit card number. -- Abdul Nizar
Not to be *that* guy, but have you tried another mouse?
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. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Finagle's First Law: To study a subject best, understand it thoroughly before you start.
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
On Sun, 15 Nov 2015 17:56:30 +0100 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.
Standard question lately: was xf86-input-evdev updated when xorg-server was?
On Sun, Nov 15, 2015 at 11:31:27AM -0600, Doug Newgard wrote:
On Sun, 15 Nov 2015 17:56:30 +0100 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.
Standard question lately: was xf86-input-evdev updated when xorg-server was?
If it was updated in the repo, then it was updated on the machine, I very rarely do a selective upgrade and in this case I ran `pacman -Syu` every time. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Failure is not an option. It comes bundled with the software.
On Mon, Nov 16, 2015 at 3:17 PM, Magnus Therning <magnus@therning.org> wrote:
On Sun, Nov 15, 2015 at 11:31:27AM -0600, Doug Newgard wrote:
On Sun, 15 Nov 2015 17:56:30 +0100 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.
Standard question lately: was xf86-input-evdev updated when xorg-server was?
If it was updated in the repo, then it was updated on the machine, I very rarely do a selective upgrade and in this case I ran `pacman -Syu` every time.
And you've obviously also checked to make sure the mirror was synced properly? Not sure if you meant you used ARA all the way to the most current update or are currently using another mirror.
On Mon, Nov 16, 2015 at 04:20:35PM +0800, Oon-Ee Ng wrote:
On Mon, Nov 16, 2015 at 3:17 PM, Magnus Therning <magnus@therning.org> wrote:
On Sun, Nov 15, 2015 at 11:31:27AM -0600, Doug Newgard wrote:
On Sun, 15 Nov 2015 17:56:30 +0100 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.
Standard question lately: was xf86-input-evdev updated when xorg-server was?
If it was updated in the repo, then it was updated on the machine, I very rarely do a selective upgrade and in this case I ran `pacman -Syu` every time.
And you've obviously also checked to make sure the mirror was synced properly? Not sure if you meant you used ARA all the way to the most current update or are currently using another mirror.
For the last update I switched to the ordinary mirrors and reran reflector to get a good list of mirrors. I haven't done anything beyond that. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus But whereas I previously held for Java a cordial dislike borne of having only a cursory notion of how it worked, now my dislike for the language can no longer be called at all "cordial", for familiarity has bred contempt. -- Tom Christiansen
On Mon, 16 Nov 2015 08:17:09 +0100 Magnus Therning <magnus@therning.org> wrote:
Standard question lately: was xf86-input-evdev updated when xorg-server was?
If it was updated in the repo, then it was updated on the machine, I very rarely do a selective upgrade and in this case I ran `pacman -Syu` every time.
That's not an answer...
On Tue, Nov 17, 2015 at 10:38:54AM -0600, Doug Newgard wrote:
On Mon, 16 Nov 2015 08:17:09 +0100 Magnus Therning <magnus@therning.org> wrote:
Standard question lately: was xf86-input-evdev updated when xorg-server was?
If it was updated in the repo, then it was updated on the machine, I very rarely do a selective upgrade and in this case I ran `pacman -Syu` every time.
That's not an answer...
Sure it is, though it may lack in details to be a "good answer". Given that I performed about 8 updates in quick succession, jumping about 1 week each time, and that I currently don't have access to the system it is the best answer I can give you. Clearly this isn't anything anyone else has run into though, so I'll just let this rest until I get back to the system in question and can investigate it further myself. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus The day after tomorrow is the third day of the rest of your life.
On Tue, 17 Nov 2015 18:05:14 +0100 Magnus Therning <magnus@therning.org> wrote:
Clearly this isn't anything anyone else has run into though,
There have been numerous people on the forums and on IRC with mice or keyboards not working, mostly caused by having installed a different version of xf86-input-evdev from the AUR which wasn't updated for the changes in the xorg-server package. Your case is a bit more specific, so it may not be related, but it needs to be checked.
Make sure you're not using [testing]. On Nov 15, 2015 9:56 AM, "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?
/M
[1]: https://wiki.archlinux.org/index.php/Arch_Linux_Archive
-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
Goto labels should be left-aligned in all caps and should include the programmer's name, home phone number, and credit card number. -- Abdul Nizar
participants (5)
-
Ben Oliver
-
Doug Newgard
-
Magnus Therning
-
Oon-Ee Ng
-
William Castro