User forums > Help

Keyboard shortcuts not working on Debian

<< < (2/4) > >>

dp_alvarez:
Thank you very much for the fix Pecan! Unfortunately I can't get CB the latest version from SVN to run. It compiles fine, but when I try to run it I get the following error: "codeblocks: symbol lookup error: codeblocks: undefined symbol: cbEVT_APP_CMDLINE".
I'm on Debian Jessie x64, anyone has a clue on what could be causing this?

oBFusCATed:
Probably you're mixing different installation.
My guess is that you have libcodeblocks.so in a standard location and you've installed another copy in another location.

dp_alvarez:
That is right, didn't notice package codeblocks was separate from libcodeblocks.
The main issue is fixed, but there still is a slight inconvenience: When the focus is on the editor keybindings to open logs or the manager don't open them. They are closed if already opened, and if I press a hotkey to change the focus it works, but that is kind of inconvenient.

Thanks again for the fix Pecan! Hope this can be fixed too when possible  ;D

Pecan:

--- Quote from: dp_alvarez on August 29, 2015, 08:06:49 am ---That is right, didn't notice package codeblocks was separate from libcodeblocks.
The main issue is fixed, but there still is a slight inconvenience: When the focus is on the editor keybindings to open logs or the manager don't open them. They are closed if already opened, and if I press a hotkey to change the focus it works, but that is kind of inconvenient.

Thanks again for the fix Pecan! Hope this can be fixed too when possible  ;D

--- End quote ---

Please describe exact steps to cause the problem.

dp_alvarez:
This happened with the latest version from the SVN in a (mostly) clean Debian Jessie.
-Start with a clean codeblocks profile
-Create a new project
-Close the logs windows
-While editing any file in the project, press F2 (the default hotkey to the logs window)
-If the focus is on the editor (it should be, as you were editing a file) it does nothing but it should have opened the logs

If you repeat the same steps but leave the logs window open before editing a file F2 does work and closes the logs window as it should, but if you try to press it again to open the window it does not work anymore.
The same happens with the Shift-F2 hotkey, even if I bind it to another hotkey in keybinder.

Navigation

[0] Message Index

[#] Next page

[*] Previous page