Your message dated Fri, 14 Sep 2012 14:46:53 +1000 with message-id <[email protected]> and subject line is keyring daemon running? has caused the Debian Bug report #670813, regarding mysql-workbench: error with communicating with Gnome keyring Demon... to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 670813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670813 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mysql-workbench Version: 5.2.38+dfsg-1 Severity: important Tags: upstream Dear Maintainer, With MySQL WorkBench I have trouble accessing mySQL server. WorkBench can't connect to Gnome Keyring Demon for root password. I want to ask you to take a look at it, when you have time... Thank you Andre -- System Information: Debian Release: wheezy/sid Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mysql-workbench depends on: ii libatk1.0-0 2.4.0-2 ii libatkmm-1.6-1 2.22.6-1 ii libc6 2.13-30 ii libcairo2 1.10.2-7 ii libcairomm-1.0-1 1.10.0-1 ii libctemplate0 2.0-1 ii libfontconfig1 2.8.0-3.1 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgl1-mesa-glx [libgl1] 7.11.2-1 ii libglib2.0-0 2.32.0-4 ii libglibmm-2.4-1c2a 2.32.0-1 ii libgnome-keyring0 3.4.0-1 ii libgtk2.0-0 2.24.10-1 ii libgtkmm-2.4-1c2a 1:2.24.2-1 ii liblua5.1-0 5.1.5-1 ii libmysqlclient16 5.1.61-3 ii libpango1.0-0 1.29.4-3+b1 ii libpangomm-1.4-1 2.28.4-1 ii libpcre3 1:8.30-4 ii libpython2.7 2.7.2-8 ii libsigc++-2.0-0c2a 2.2.10-0.1 ii libsqlite3-0 3.7.11-2 ii libstdc++6 4.7.0-3 ii libtinyxml2.6.2 2.6.2-1 ii libuuid1 2.20.1-4 ii libx11-6 2:1.4.4-4 ii libxml2 2.7.8.dfsg-9 ii libzip2 0.10-1 ii mysql-client-5.1 [mysql-client] 5.1.61-3 ii mysql-workbench-data 5.2.38+dfsg-1 ii python 2.7.2-10 ii python-all 2.7.2-10 ii python-mysql.connector 0.3.2-1 ii python-paramiko 1.7.7.1-2 ii python-pexpect 2.4-1 ii python-pysqlite2 2.6.3-2 ii python2.7 2.7.2-8 ii zlib1g 1:1.2.6.dfsg-2 Versions of packages mysql-workbench recommends: ii mysql-utilities 1.0.4-3 ii ttf-bitstream-vera 1.10-8 Versions of packages mysql-workbench suggests: ii gnome-keyring 3.2.2-2 -- no debconf information
--- End Message ---
--- Begin Message ---On KDE or Xfce4 if "mysql-workbench" prints ** Message: Gnome keyring daemon seems to not be available. Stored passwords will be lost once quit to the console, then "gnome-keyring-daemon" may not be running. To start "gnome-keyring-daemon" try: [ -z "$GNOME_KEYRING_CONTROL" ] && export $(gnome-keyring-daemon --start) See also https://live.gnome.org/GnomeKeyring/RunningDaemon ######## mysql-workbench is not responsible for starting and initialising of "gnome-keyring-daemon". ######## If there is a dialog "Error communicating with gnome-keyring-daemon" this probably means that gnome-keyring-daemon can't display its dialog. Typically this behaviour can be observed over SSH connection because gnome-keyring-daemon depends on "dbus" which may not be running. To start "dbus" try: [ -z "$DBUS_SESSION_BUS_ADDRESS" ] && export $(dbus-launch) Later you might need to terminate dangling "dbus" using kill ${DBUS_SESSION_BUS_PID} otherwise it won't be terminated when you close SSH session. Please note that "dbus" must be started before "gnome-keyring-daemon". ######## mysql-workbench is not responsible for starting and initialising of "dbus". ######## Regards, Dmitry.
--- End Message ---
