Ctrl + Shift + G no longer works in eclipse

Question

I am a huge fan of Eclipse hotkeys, Ctrl + Shift + G , which is one of my favorites. However, I recently had to completely throw away my workspace and load a new one in order to switch to a new branch after some kind of merge problem occurred. Either this, or a later check that messed up with some classpath files, seems to have violated my search ability with Ctrl + Shift + G. I always find nothing.

I have several maven projects that are all interconnected, and I thought the problem was originally with maven. However, I cannot even find the methods in the same project or even in the same file using Ctrl + Shift + G.

Can someone suggest a process that I am undertaking to make my eclipse find out about my source code so that it can look for it correctly?

EDIT: I don't know how I missed this before. Eclipse seems to throw a class exception that the class is looking for

org.eclipse.wb.internal.core.utils.dbt.core.project utils 

Before this exception is thrown, I can perform the search as usual, after this exception, the search is interrupted. So the problem is actually the exception, I'm sure. Reboot fixes the situation temporarily. Unfortunately, the exception continues to be thrown after using eclipse for a while. So now I am considering the reason for the exception. I can post the answer here and / or open a new question, depending on how much I can independently investigate the cause of the exception.

Answer 1

Open the Preferences dialog box. (On Windows, select Window> Preferences.)

Select the General> Keys settings page.

Go to the Links command in the workspace. Choose it. If the displayed snap is not Ctrl + Shift + G , you can set it:

• Pressing the desired key combination Ctrl + Shift + G.
• Clicking the Apply or OK button.

Answer 2

I believe your hotkey has been programmed in some way, try reading it

Window → Settings → General → Keys

Mac: Eclipse → Settings → General → Keys

Hope this helps

Answer 3

Just update this problem. As soon as I realized that the exception was the cause of my problem, I examined it in Stack Overflow. I found another question that raised this question, although I am afraid that I have no link now. The suggested answer, however, was to start Eclipse with the --clean option. The problem seems to have disappeared as soon as I did it.

I have replies to other answers as a thank you for the answers. They were good answers, given the information I provided, it was my mistake, I did not know about the complete problem when I posted the question.