mysql-workbench and Gnome keyring daemon problem

Question

when launching mysql-workbench I have the following warning:

[12:13:49] coil@coil:~$ sudo mysql-workbench &
[12:14:03] coil@coil:~$ ** Message: Gnome keyring daemon seems to not be available. Stored passwords will be lost once quit
[12:14:05] coil@coil:~$ Ready

Is there a way to fix this issue? Indeed, my passwords never get saved.

What Ubuntu version/release it this on? Cuz ... http://bugs.mysql.com/bug.php?id=61170 — Rinzwind, Nov 28 '14 at 14:45
Sorry guys, I'll try all you suggested me soon. Thanks for the help. ;) — COil, Dec 25 '14 at 22:10

dmvslv · Accepted Answer · 2015-01-23T05:36:36.863

31

The bug has been fixed in MySQL Workbench 6.2.5 / 6.3.0 releases. http://bugs.mysql.com/bug.php?id=74771

A possible workaround was to add this code to the top of file /usr/bin/mysql-workbench

export GNOME_KEYRING_CONTROL=1

This fix work on my ubuntu 14.04 with MySQL Workbench community 6.2.4 from deb http://repo.mysql.com/apt/ubuntu/ trusty workbench-6.2

edited Jan 23 '15 at 05:36

answered Jan 23 '15 at 05:28

dmvslv

426
3
5

Thanks for linking the issue and providing the workaround - this is the cleanest approach! – conceptdeluxe May 19 '15 at 20:25
3

Using V6.3.6 error still persists – Matiss Aug 09 '16 at 08:17

Lalit Mehra · Answer 2 · 2016-12-25T05:08:00.377

15

There's a neat way I found, try this out.

Step 1: After installation unlock the workbench icon from launcher.

Step 2: press the super(window) button on your machine and search for workbench.

Step 3: Open workbench from the search results.

Step 4: Once open, lock the workbench icon to the launcher.

Voila !!! The keyring problem disappears.

edited Dec 25 '16 at 05:08

answered Sep 02 '15 at 06:17

Lalit Mehra

251
2
5

2

Thanks.. Much Cleaner way to resolve this issue. Thanks a ton. :) – Anil Chahal Apr 28 '16 at 03:34
1

Works but an explanation would be nice... – snorbi Dec 23 '16 at 09:09
1

Wow! I just realized that I always was launching workbench from dash (start menu) but not from launchbar. And now today after few years of using workbench launched it by clicking on launcher and got that problem! – Dimitry K May 09 '17 at 14:12

score 9 · Answer 3 · answered Dec 08 '14 at 15:36

9

This answer is a variation on the guest1000's solution, but I don't have enough rep to create a comment.

Anyway, adding the following to ~/.bashrc also works and seems cleaner to me:

export GNOME_KEYRING_CONTROL=$(ls -d /run/user/1000/keyring-*)

answered Dec 08 '14 at 15:36

Jovean

91
2

score 6 · Answer 4 · edited Jan 22 '15 at 13:38

6

Add this code to the top of file /usr/bin/mysql-workbench

if ls /run/user/`id -u`/keyring-* 1> /dev/null 2>&1; then
    gnome-keyring-daemon > /dev/null
fi

export GNOME_KEYRING_CONTROL=$(ls -d /run/user/`id -u`/keyring-* | head -n 1)

It's not clean solution, but it works. No need of running workbench from terminal.

edited Jan 22 '15 at 13:38

Evandro Silva

9,472
6
35
44

answered Jan 22 '15 at 13:28

rooobertek

161
2

score 5 · Answer 5 · answered Mar 01 '16 at 06:18

5

I did as follows i am using Workbench 6.3

sudo gedit /usr/bin/mysql-workbench

Just remove the comment

@line 5

WB_NO_GNOME_KEYRING=1

answered Mar 01 '16 at 06:18

suresh

171
1
6

score 3 · Answer 6 · edited Sep 27 '20 at 15:46

3

I am using Ubuntu 18.04. The simplest way I found is

Go to Ubuntu software center.
Search for MySQL workbench community.
Click on permission
Enable Read, add .... to on

edited Sep 27 '20 at 15:46

Zanna

69,223
56
216
327

answered May 11 '20 at 18:54

Amrit Sah

31
1

Thanks worked for me – Fahim Jun 07 '20 at 22:34
This is the most correct solution for snap users. – Peter Chaula Oct 07 '20 at 05:55

score 2 · Answer 7 · answered Dec 04 '14 at 14:30

mysql-workbench is looking for the GNOME_KEYRING_CONTROL environment variable. If you are the only one using your computer, that variable should have a value similar to /run/user/1000/keyring-XXXXXX.

I had a similar problem with mysql-workbench package downloaded from dev.mysql.com (because MariaDB and Ubuntu's mysql-workbench package are incompatible) and a simple custom shortcut with the following launch command fixed the problem:

GNOME_KEYRING_CONTROL=$(ls -d /run/user/1000/keyring-*) /usr/bin/mysql-workbench

no need to do as long as this. just type mysql-workbench from terminal — akikara, Dec 17 '14 at 20:39

score 2 · Answer 8 · answered Dec 17 '14 at 20:37

2

The most stupid issue ever seen!

if you start your mysql-workbech by launcher this error comes out.

But if you start your mysql workbench from terminal keyring problem disappears.

Any ideas why this is happening? I was using version 6.0 and upgraded to 6.2.4 nothing changed. The workaround answer for this issue is Go terminal and start stupid workbench by Oracle...

answered Dec 17 '14 at 20:37

akikara

787
1
12
28

I am having this issue and its 2017 – Jamie Hutber Dec 11 '17 at 11:53

score 0 · Answer 9 · edited Aug 10 '20 at 13:16

0

Ubuntu 20.04 LTS

I just:

Removed mysql-workbench.
Downloaded mysql-workbench deb package from the official mysql page.
Installed it with dpkg and it solved my problem.

I guess the problem was that I installed mysql-workbech with snap.

edited Aug 10 '20 at 13:16

ThunderBird

1,915
13
19
31

answered Aug 07 '20 at 17:16

Japhet Mata Arellanes

11

I would be very surprised if you had encountered the very same problem from 2014. – guntbert Aug 07 '20 at 20:05
The snap works, the issue is with permissions. Have a look at Amrit's [answer](https://askubuntu.com/a/1238350/554832) – Peter Chaula Oct 07 '20 at 05:56

mysql-workbench and Gnome keyring daemon problem

9 Answers9