The patch was required for mysql-workbench up to and including version 6.2.4 as it could not handle gnome-keyring >= 3.14. Upstream code changed and version 6.2.5 should be fine with latest gnome-keyring and it works for me.

First of all: gnome-keyring is just an optional dependency. Do you have it installed? Do you expect to not enter a password or do you just want to get rid of the error message?

So some questions arise:

* You wirte about tunnelled connections. (btw, mysql-workbench can connect via ssh on its own) Does this work with local connections?
* Does this work when connecting to default port 3306?
* Any useful information from logfiles in ~/.mysql/workbench/log/?
* Is XDG_RUNTIME_DIR set correctly?

Since I have the same (or at least a similar) problem and OP does not appear to be very responsive, I take the liberty to answer the questions:

> Do you expect to not enter a password or do you just want to get rid of the error message?

Well, I surely would like to be able to enter a password, but after clicking on "Close" an the given error message it just disappears and nothing happens.

> * You wirte about tunnelled connections. (btw, mysql-workbench can connect via ssh on its own) Does this work with local connections?

I am using a very simple local connection (no custom ports, no encryption, nothing), so I can say: No, it does not work.

> * Does this work when connecting to default port 3306?

Nope, does not work.

* Any useful information from logfiles in ~/.mysql/workbench/log/?

Just the messages from the error-message-pop-up, plus this:

13:42:01 [INF][ base library]: Notification GNFocusChanged is not registered
13:42:01 [INF][ base library]: Notification GNUIFormCreated is not registered
13:42:01 [INF][ base library]: Notification GNUIFormDestroyed is not registered
13:42:01 [ERR][ SqlEditor]: SQL editor could not be connected: Fehler bei der Kommunikation mit dem GNOME-Schlüsselbunddienst
13:42:01 [ERR][ SqlEditor]: Your connection attempt failed for user 'root' from your host to server at localhost:3306:

The german part roughly translates to "Error while communicating with GNOME-keyring-deamon"

> * Is XDG_RUNTIME_DIR set correctly?

Well, that depends. How should it be set?

[hoerbert@Arch ~]$ echo $XDG_RUNTIME_DIR
/run/user/1000

Additional info:

- I'm using Plasma 5
- gnome-keyring is not installed

If I can be of further assistance just let me know.

Looks like MySQL Workbench expects gnome-keyring to be installed. Try to start mysql-workbench with

WB_NO_GNOME_KEYRING=1 mysql-workbench

Does that bring the expected result?

> Try to start mysql-workbench with
>
> WB_NO_GNOME_KEYRING=1 mysql-workbench
>
> Does that bring the expected result?

Yeah, that works. Now, if I try to connect, I am asked for a password again.

So for me this is a suitable workaround.

Can you please test mysql-workbench 6.2.5-2 in [community-testing]?
That version should work with and without gnome-keyring installed.

Hmm…

If I haven't done something completely wrong (I'm a first-timer in using the testing-repos), then this version does not work for me.

I enabled the testing and community-testing repos in /etc/pacman.conf, did a pacman -Syu, aborted the upgrade, because I did not want to install every new package version from testing, and then did a pacman -S mysql-workbench, which upgraded it to Version 6.2.5-2 (as also stated by pacman -Q mysql-workbench). I know, this is a partial upgrade, but as the workbench seems not to need any other packages from the suggested upgrade, I thought this would be OK this time.

But: The error message posted by OP is still there and I'm not able to login to my mysql-server. Additionally, there is a new message at the command line (if started from there):

/usr/bin/mysql-workbench: Zeile 9: type: gnome-keyring-daemon: Nicht gefunden.

("Nicht gefunden" means "not found" in german, "Zeile" means "line" [as you probably know, but others may not])

"WB_NO_GNOME_KEYRING=1 mysql-workbench" still works, the new message on the command line is also there.

Then let's try mysql-workbench 6.2.5-3 now...

That seems to do the trick. The message on the command line is gone, I'm prompted to enter a password and so I'm able to connect to servers again.

I haven't thoroughly tested all of the other functionality, but the first impression is good ;)