Mouse buttons clicking twice in Slackware 12.1
Recently upgraded from 12.0 to 12.1 following the steps outlines in UPGRADE.TXT and CHANGES_AND_HINTS.TXT and so far so good except for the USB mouse in KDE. For some odd reason whenever I click once, whether it be the left button or the right, it's treated as as though I've double clicked. I've tried removing .kde and starting KDE as new, but no change. Even the wheel, which is supposed to paste the contents of a copy/cut acts as though I've clicked twice. Does anyone know why this is happening?
I've tried blacklisting the psmouse module and allowing it to load, but that didn't help. I've also manually loaded and unloaded this particular module, but no change. HELP! |
Looks like I've narrowed it down to my xorg.conf file being the culprit, but I have no clue what could be wrong since it was working fine in Slackware 12.0. Here's my conf file.
Code:
Section "Module" |
I don't think you need to blacklist psmouse. Instead, you might just need to change the protocol used in /etc/modprobe.d/psmouse
Quote:
Last resort, check these things: /etc/udev make sure there are no .new or .bak or .orig files anywhere while you are at it, in case you forgot to remove 75-network-devices.rules and 75-optical-devices.rules you can do that now Quote:
|
Quote:
Perhaps try Code:
Option "Protocol" "Auto" Don't forget to check how your mouse works in a console (no X!) |
The thing with psmouse is I don't see it loaded at the moment when I do a lsmod | grep psmouse. If I exit KDE, modprobe it and go back into KDE there's absolutely no change...
This is not happening at the console. The weird thing is my notebook's touchpad does the same thing as my USB mouse! I say I've narrowed it down to the xorg.conf because I loaded a very generic xorg.conf and the mouse works with no problems. Attempts at duplicating only the mouse section does not fix this... As for my udev directory everything in there looks ok. |
Quote:
What do you mean by how my mouse works in a console? |
Quote:
Quote:
You said when you click on something it double clicks. In the console with GPM activated this would cause you to highlight a word (one click is a character highlight). A middle click would paste what is highlighted once, where a double middle click would paste twice. I think you get it now... If there is no problem without X, then it is probably your xorg.conf. If that is the case, try the auto option I mentioned for one of your mice (your touchpad). Also, try only having one of them in there. I just checked my laptop and I only have one InputDevice listed for mice. I use auto for my protocol and I can easily use my touchpad or USB mouse without problems. |
I don't know that this will affect your specific problem (the double mouse click), but if `lsmod | grep psmouse` returns nothing, you've set something up improperly. I notice you upgraded from 12.0 to 12.1. In 12.0, the psmouse module was blacklisted by default and then later loaded using /etc/rc.d/rc.modules*. In 12.1, it is no longer blacklisted by default, and instead the options for loading the psmouse module are specified in /etc/modprobe.d/psmouse. Therefore, the line loading psmouse in /etc/rc.modules-2.6.24.5-smp is COMMENTED OUT, as it should be.
You should make sure that you are using the generic-smp-2.6.24.5-smp kernel, that rc.modules-2.6.24.5-smp is being loaded at boot time (it won't appear in `dmesg` or in any other logs -- you'll have to watch as your computer boots up. It should say something like "Running rc.modules-2.6.24.5-smp"), and that you only have one blacklist file in /etc/modprobe.d (and it should be the one from 12.1). If your psmouse module is not being loaded by default, it's likely that you have two blacklist files in /etc/modprobe.d. You should have overwritten the old (/etc/modprobe.d/blacklist) file with the new (/etc/modprobe.d/blacklist.new) file. Make sure that you do NOT have a backup of the 12.0 blacklist file in that directory, or else BOTH will be checked and since psmouse is blacklisted in 12.0's blacklist file, it will not be loaded. You should also make sure that /etc/modprobe.d/psmouse exists. Quote:
I am not sure if that will affect your problem or not, but it seems something is awry anyway and should be fixed regardless. |
Thanks guys for your suggestions and help. It looks like I've narrowed down my issue to the following two arguments:
Option "SendCoreEvents" "true" "CorePointer" Apparently giving IntelliMouse the "CorePointer" option and the touchpad the other fixes the issue. |
All times are GMT -5. The time now is 02:33 AM. |