Bug #63657 MySQL Workbench can't store connection passwords

Submitted: 7 Dec 2011 19:57 Modified: 19 Dec 2011 20:41
Reporter: Manana Dan Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.31, 5.2.36 OS:Linux (Opensuse 11.4)
Assigned to: CPU Architecture:Any
Tags: gnome-keyring, password

[7 Dec 2011 19:57] Manana Dan 
Description:
MySQL Workbench won't store passwords although gnome-keyring is installed and up and running. Every other application can store passwords. Seahorse can access passwords so deamon is running

As i see someone reported same bug(#61627) but it`s closed for no reason

How to repeat:
1. establish connection to server and check to store password
2. close workbench and reopen
3. open existing connection and it will ask for password again
[8 Dec 2011 1:01] MySQL Verification Team 
Could you please upgrade to version 5.2.36. Thanks.
[9 Dec 2011 14:23] Manana Dan 
In 5.2.36 problem still persist
[13 Dec 2011 19:31] Manana Dan 
What`s i can do next?
[14 Dec 2011 13:21] MySQL Verification Team 
Not repeatable on Ubuntu 11.04.
[15 Dec 2011 16:25] Alfredo Kojima 
Do you use gnome? If not, can you describe the exact steps you use to start gnome-keyring and then workbench? Are they started in the same terminal?
[16 Dec 2011 9:37] Manana Dan 
It`s on opensuse 11.4 , on Centos 6 it was working, but here it`s not showing any error even when running from terminal, i`m using gnome and for sure gnome-keyring is started & working (other applications ie. Network Manager is working with it with no problems)
[19 Dec 2011 20:41] Rafael Antonio Bedoy Torres 
Hello,

I'm afraid that we're not supporting Opensuse anymore, can you please try using one of the OS's supported 
http://www.mysql.com/support/supportedplatforms/workbench.html

Thanks
[19 Sep 2012 22:30] James Gentes 
I see this problem on Windows 7

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.041 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.