Can't remember exactly *when* this started happening but it DID *used to* work. I'm running Slackware -current / kernel 2.6.17.7. Using a 2-button mouse. Usually, I'd copy/paste the following way:

#1. Select to copy.
#2. Click on both buttons at once to paste.

Now it seems that: select doesn't copy and click-on-both doesn't paste. Has anyone experienced this? Does anyone know a cause/fix? Does anyone recommend a method to find the cause?

is gpm running?

Also I think you may need in the xorg.conf input section

Option "Emulate3Buttons"

has that changed recently?

tobyl

#1. I don't think GPM and X apps have much, if anything, in common. GPM is for cli.

#2. I had mentioned, it used to work, now it doesn't. A line from xorg.conf couldn't have magically disappeared.

Due to some reasons I will not mention I was forced to reinstall Slackware. I've created a -current ISO + CD and installed. The problem is solved. If I'd have to guess, I'd say it was because of a faulty gtkrc file I had created and had been using. So .. problem .. "fixed" .. somehow

Thanks for the replies.

well in defence of kodon, you didn't mention whether the problem occurred in X apps or cli.
in defence of myself, I didn't mention magic. I did not know that you hadn't caused xorg.conf to be changed in a 'non-magic' way, for instance by running xorgconfig.

glad you got it fixed

tobyl

I was blaming/etc. anyone In CLI, via GPM you copy paste by select+right click. In X select+"middle click". This should have been a hint probably but yes, I should have specified X.

really?
gpm at the cli uses the middle to paste here...
which i'd assume would be left+right
emulation on a 4-button mouse

iirc, I think gpm can also be configured to allow pasting between X and CLI on top of the usual feature of being able to copy and paste between virtual consoles. So in everyone's defense, it's good that they asked about gpm since it probably possible for it to play a part in a conflict or contention over the mouse.

I believe that some older versions of gpm used to cause such a conflict iirc. I do believe it was fixed by certain a version though. But still, it's usually best not to rule out such possibilities altogether when troubleshooting, because you just really never know for sure. Also, I've had times when troubleshooting various things, that old bugs have crept back into new code as features were added (I'm sure everyone can relate to that sort of frustration at one time or another )

I don't really use gpm much, but I know I've read somewhere about the above before. Either way, it's one of those things that good to know about since it could possibly save someone from a hair pulling experience that can happen very easily sometimes with Linux.

no, you'll need something like xclip for that