MySQL Bugs: #52866: Keyring daemon unavailable

Bug #52866	Keyring daemon unavailable
Submitted:	15 Apr 2010 20:10	Modified:	27 May 2010 10:05
Reporter:	Danny Engelbarts	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.18	OS:	Linux (Kubuntu 10.4 x86_64)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any
Tags:	gnome keyring, kde

Description:
WB_NO_GNOME_KEYRING=1 does not disable gnome keyring, it is therefore impossible to connect without an active keyring daemon

How to repeat:
disable keyring daemon, open workbench and try to connect.

Suggested fix:
Since i use the KDE desktop i do not have an active keyring daemon. Besides that i do not wish to use it, i find it perfectly acceptable to enter a password when first establishing a connection in a given session. I would expect the WB_NO_GNOME_KEYRING=1 setting to offer that possibility but it does not ...

Many thanks for writing a bug report. Verified as described.

What effect do you get? I've killed the GNOME keyring daemon in my Ubuntu desktop and it works ok.

I cannot connect to the database;
[code]
Cannot Connect to Database Server
Your connection attempt failed for user 'markant' from your host to server at 127.0.0.1:3306:
  Canceled by user

Please:
1 Check that mysql is running on server 127.0.0.1
2 Check that mysql is running on port 3306 (note: 3306 is the default, but this can be changed)
3 Check the markant has rights to connect to 127.0.0.1 from your address (mysql rights define what clients can connect to the server and from which machines) 
4 Make sure you are both providing a password if needed and using the correct password for 127.0.0.1 connecting from the host address you're connecting from
[/code]

If i start the gnome-keyring-daemon from the command prompt and try to connect again from WB i can enter my password and open the connection.

Confirm the error in my Kubuntu 4.10 x86_32. You have to start to hand the gnome-keyring-daemon from the command prompt and you can work with ssh connection.

Confirmed for me as well.  KDE = no gnome-keyring-daemon...

Hi,

 I'm using Kubuntu 10.04 and mysql workbench 5.2.21.

 I'm unable to use the product since I don't have gnome-keyring-deamon.

 I've no issue using plaintext/obfuscated storage for password as this it's for dev purpose.

 I don't understand why there's no alternative to gnome-keyring for password storage

Thomas.

In facte gnome-keyring-daemon is installed on my system, 

I've just run it

thomas@daisybox:~$ gnome-keyring-daemon
GNOME_KEYRING_CONTROL=/tmp/keyring-OXLWza
SSH_AUTH_SOCK=/tmp/keyring-OXLWza/ssh
GNOME_KEYRING_PID=25080

and I was able to use mysqlworkbench

if not installed, just install it, with, I guess, 
sudo aptitude install gnome-keyring

Same problem. Kubuntu 10.04. When I installed gnome-keyring-daemon and try to connect I get the error message "Error communicating with gnome-keyring-daemon". No idea what's wrong with it, don't use gnome keyring for anything else and have no desire to either. I don't need a high level of security on my database and would just like to be able to use a plain text password. Please fix as its making workbench unusable.

I've seen reports that WB_NO_GNOME_KEYRING does solve this problem.
Note that you need to set it in the same environment as workbench, ie: from a terminal window
export WB_NO_GNOME_KEYRING=1 and then start WB from there.

Fixed.

I have modified the mysql-workbench script to export WB_NO_GNOME_KEYRING=1. Indeed this does solve the problem!

happens to me on Kubuntu 10.04 x32
I edited /usr/bin/mysql-workbench and added the line
export WB_NO_GNOME_KEYRING=1
and worked for me, but, it still display the button [Store in Keychian], and after I add the password it will ask me every time a connection needed. 
Also, in the top of /usr/bin/mysql-workbench file there's the following lines:
# Uncomment the following line if you're having trouble with gnome-keyring lockups.
# This will cause passwords to be stored only temporarily for the session.
#WB_NO_GNOME_KEYRING=1

Uncommenting won't achieve the expected behavior!

thank you

fix confirmed in repository

Bug #54010 has been marked as duplicate of this one

An entry has been added to the 5.2.22 changelog:

Setting WB_NO_GNOME_KEYRING=1 on Kubuntu did not appear to disable the Gnome keyring, it was therefore impossible to connect without an active keyring daemon.

Marked bug #53991 as duplicate of this