Bug#750018: mysql-workbench hangs on any attempt to connect to a database.

2014-05-31 Thread sherif
Package: mysql-workbench
Version: 6.1.4+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

If I start mysql-workbench, it seems to start OK, but as soon as I try to do
anything it completely locks up (unresponsive). The lock up seems to be
triggered by ANY attempt to connect to a database, making the application
unusable.

This fault has only recently appeared (until about a week ago it worked
normally).  I assume therefore that some dependency has changed and causes a
crash.

I have tried starting from the command line with mysql-workbench --log-
level=debug3 , but even that shows no meaningful output (just Logger set to
level 'debug3'. '011' Ready. ** Message: /usr/share/mysql-
workbench/extras).




-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages mysql-workbench depends on:
ii  libatkmm-1.6-1   2.22.7-2
ii  libc62.18-7
ii  libcairo21.12.16-2
ii  libctemplate22.2-4
ii  libgcc1  1:4.9.0-4
ii  libgdk-pixbuf2.0-0   2.30.7-1
ii  libgl1-mesa-glx [libgl1] 10.1.2-1
ii  libglib2.0-0 2.40.0-3
ii  libglibmm-2.4-1c2a   2.40.0-1
ii  libgnome-keyring03.4.1-1
ii  libgtk2.0-0  2.24.23-1
ii  libgtkmm-2.4-1c2a1:2.24.4-1
ii  liblua5.1-0  5.1.5-5
ii  libmysqlclient18 5.5.37-1
ii  libmysqlcppconn7 1.1.3-5
ii  libodbc1 2.3.1-3
ii  libpango-1.0-0   1.36.3-1
ii  libpangocairo-1.0-0  1.36.3-1
ii  libpangomm-1.4-1 2.34.0-1
ii  libpcre3 1:8.31-5
ii  libpcrecpp0  1:8.31-5
ii  libpython2.7 2.7.7~rc1-1
ii  libsigc++-2.0-0c2a   2.2.11-3
ii  libstdc++6   4.9.0-4
ii  libtinyxml2.6.2  2.6.2-2
ii  libuuid1 2.20.1-5.7
ii  libvsqlitepp30.3.13-1
ii  libx11-6 2:1.6.2-2
ii  libxml2  2.9.1+dfsg1-3
ii  libzip2  0.11.2-1
ii  mysql-client-5.5 [virtual-mysql-client]  5.5.37-1
ii  mysql-workbench-data 6.1.4+dfsg-2
ii  python-mysql.connector   1.1.6-1
ii  python-paramiko  1.14.0-1
ii  python-pexpect   3.2-1
ii  python-pyodbc3.0.6-2
ii  python-pysqlite2 2.6.3-3
ii  python2.72.7.7~rc1-1
pn  python:any   none

Versions of packages mysql-workbench recommends:
ii  mysql-utilities 1.3.5-2
ii  ttf-bitstream-vera  1.10-8

Versions of packages mysql-workbench suggests:
ii  gnome-keyring  3.8.2-2+b1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#750018: mysql-workbench hangs on any attempt to connect to a database.

2014-05-31 Thread Dmitry Smirnov
On Sat, 31 May 2014 18:34:50 sherif wrote:
 Severity: grave

Please do not panic and use correct severity as documented in:

https://www.debian.org/Bugs/Developer#severities


 If I start mysql-workbench, it seems to start OK, but as soon as I try to do
 anything it completely locks up (unresponsive). The lock up seems to be
 triggered by ANY attempt to connect to a database, making the application
 unusable.
 
 This fault has only recently appeared (until about a week ago it worked
 normally).  I assume therefore that some dependency has changed and causes a
 crash.

I'm unable to confirm your findings on up-to-date testing. Please have a 
look at recently installed packages in /var/log/apt/history.log and try to 
isolate the responsible package. Try to confirm the problem by downgrading it.

Please try newer mysql-workbench from unstable as well. Is it affected?

Also it may be helpful to ensure integrity of installed packages with 
debsums.

-- 
Cheers,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B


signature.asc
Description: This is a digitally signed message part.