Cannot query: Graylog repeating the characters in search box

[ortizleo]

Hello.

Graylog ´s repeating the caracthers that we input in search box, because of it we cannot query correctly. Tested with Firefox, Chrome and Edge, all with cache+history+cookies cleaned.

Graylog 3.3.1 Centos 7

• To reproduce Try query something in search box.

Attached prints show the problem, when I press a single key graylog insert multiple words in the box...

Virtual Keyboard

Keyboard

[dennisoelkers]

Hey @ortizleo,

thanks for reporting this. Is this related to your on screen keyboard? I.e., can you check if using a physical keyboard changes the behavior for you?

[ortizleo]

Hello.

Physical and virtual keyboard....

[valleyman07]

Hello.

he same has happened to me after updating version from 3.2.5 to 3.3.1 and change has also changed the witges' queries symbols. It's possible to make a downgrade to the version i had before?

[ortizleo]

Hello. Any news? We cant query in Graylog 3.3.1... I think that is a critical bug.

[franz82]

Hello, same issue here, Graylog 3.3.0 and Firefox 76.0.1, OS Arch Linux. -f

[valleyman07]

you have planned to remove any patch? is there any chance of doing a downgrade? because no new or defined query works in the dashboard. And my company we need so it works.

[ortizleo]

Please we need a fix. @dennisoelkers

[dennisoelkers]

Since this issue was opened, I tried several times to reproduce it, with different browsers and versions. Unfortunately I was not successful. Does anyone of you see an error in your browser's JS console?

[ortizleo]

Hello.

Here show this in console:

6ace.js:4113 Uncaught Error: Unknown config key: sharedPopups
    at a.exports.get (ace.js:4113)
    at Function.ace.define.c.for (ext-language_tools.js:1811)
    at Array.g (ext-language_tools.js:2085)
    at i.t._signal (ace.js:3876)
    at i.exec (ace.js:11866)
    at r.$callKeyboardHandlers (ace.js:4631)
    at r.onTextInput (ace.js:4646)
    at y.onTextInput (ace.js:13548)
    at A (ace.js:2461)
    at HTMLTextAreaElement.T (ace.js:2482)

Attached another example, here I pressed 12345a on physical keyboard..

[dennisoelkers]

Thanks for the information, @ortizleo! Which plugins (and which versions of them) do you have installed?

[franz82]

@dennisoelkers, some info from my env. I had installed graylog-plugin-telegram-notification-2.3.0.jar before upgrade graylog from v3.2.5-1 to v3.3.0-5 (graylog deb packages). Now I deleted the telegram plugin and... search tab started working again! In fact, I can see a new version of telegram plugin specifically for Graylog 3.3.0 or later. Do you think this can cause the issue? -f

[franz82]

Just a little update: I installed latest telegram plugin (v2.3.1), telegram notifications are working. Search console is still working, too. -f

[ortizleo]

Just a little update: I installed latest telegram plugin (v2.3.1), telegram notifications are working. Search console is still working, too. -f

@franz82 Ok you found it. Updated graylog-plugin-telegram-notification to 2.3.1 and is fixed :).

Good work and thanks!

@valleyman07 Please check if is the same thing for you...

[irgendwr]

This issue is a duplicate of #8183 .

As @ortizleo already discovered: this is fixed in the latest release of TelegramAlert. So the solution is to upgrade the plugin, restart graylog and optionally clear the browsers cache.

The issue is/was an unfortunate side-effect of how graylog's frontend plugin system works. If a plugin's frotend depends on graylog assets, it has to contain them and therefore will also override them which causes issues when these assets are out of sync.

@ortizleo / @dennisoelkers please close this, as it is solved.

[dennisoelkers]

Thanks @franz82, @ortizleo and @irgendwr!

This issue is resolved. Nevertheless we should prevent hard to find issues like this by making our plugin system more robust, which is in my backlog for a while now anyway.