Ctrl-C and Ctrl-V do not work

[koluna]

Hello, Dears!

Linux Mint 18.1
Linux intel 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Code::Blocks 16.01, rev. 10760
SDK version 1.29.0

Sometimes, I can see that combinations Ctrl-C and Ctrl-V do not work!
They can work, but later they cannot work, later they can again work.
Turning off the option "Enable scrolling with mousewheel" does not help.
Why does it happen?
Please, help me.

[oBFusCATed]

Don't know why it happens and how, but I see it sometimes, too.
If you find a reliable way to reproduce it I'll be happy to fix it, because it is quite annoying and time wasting.

[blauzahn]

Do you have the keybinder plugin enabled? If so, please disable it and try, whether you
still observe disfunctional Ctrl-C and Ctrl-V.

I started to dig through that plugin because it makes F2 uneffective which I use a lot.
I cleaned up several things (uninitialized vars, ub etc.) but have not found the spot yed.
So for now, I have it disabled.

I use the latest version from trunk on Ubuntu 16.04, wx-3.1.1, gnome3

[oBFusCATed]

I see this on wx28 builds. For wx3.x builds the keybinder is unusable on linux and generally key shortcut handling is seriously broken.

@koluna: What is the wxgtk version C::B has been built against?

[koluna]

I see this on wx28 builds. For wx3.x builds the keybinder is unusable on linux and generally key shortcut handling is seriously broken.

@koluna: What is the wxgtk version C::B has been built against?

I am sorry for my English...
Do you like that I tell you the wx version?
How can I know which version I have for my C::B?
The information is from "About" dialog: wx2.8.12.

[koluna]

Do you have the keybinder plugin enabled? If so, please disable it and try, whether you
still observe disfunctional Ctrl-C and Ctrl-V.

I started to dig through that plugin because it makes F2 uneffective which I use a lot.
I cleaned up several things (uninitialized vars, ub etc.) but have not found the spot yed.
So for now, I have it disabled.

I use the latest version from trunk on Ubuntu 16.04, wx-3.1.1, gnome3

I will check it.
But I do not know where I can see the information about keybinder starting.
Thanks.

[blauzahn]

But I do not know where I can see the information about keybinder starting.

Menu|Plugins|Manage plugins...

look for Keyboard shortcuts (libkeybinder.so)

That is the place where you can disable it.

...or start cb from the commandline and observe the logging

[oBFusCATed]

How can I know which version I have for my C::B?
The information is from "About" dialog: wx2.8.12.

The info in the About dialog is enough.
So you have the same problem as me.
If you can find a way to reliably reproduce it I'll be happy to fix it.

[koluna]

But I do not know where I can see the information about keybinder starting.

Menu|Plugins|Manage plugins...

Oh my God! I have not understood You. I had looked for it in my Linux menu...
I have checked: the keybinder does not installed for my C::B.

[koluna]

If you can find a way to reliably reproduce it I'll be happy to fix it.

Ok, if I find out it, I wil tell You.

[koluna]

I see that is an old problem... am I right?
How does it bind with version?

[oBFusCATed]

What do you mean by "bind with version"?

[koluna]

What do you mean by "bind with version"?

Does it depend on software revision?
When did this bug turn up?

[oBFusCATed]

No idea, it is not a new bug...probably some of the scintilla updates has caused it... but without a way to reproduce it we cannot do much.