Bug 14621 - mysql-workbench doesn't connect to mariadb
Summary: mysql-workbench doesn't connect to mariadb
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Juan Luis Baptiste
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-20 18:43 CET by Thomas Spuhler
Modified: 2015-02-23 18:33 CET (History)
1 user (show)

See Also:
Source RPM: mysql-workbench-6.1.4-1.mga5.src.rpm
CVE:
Status comment:


Attachments
backtrace (84.07 KB, text/plain)
2014-11-20 18:44 CET, Thomas Spuhler
Details
screenshot (93.77 KB, image/jpeg)
2014-11-20 18:45 CET, Thomas Spuhler
Details

Description Thomas Spuhler 2014-11-20 18:43:31 CET
Description of problem:
mysql-workbench doesn't connect to mariadb

Version-Release number of selected component (if applicable):
mysql-workbench-6.1.4-1.mga5

How reproducible:
Every time

Steps to Reproduce:
1. see screenshots
2. see attached backtrace for error *** Error in `/usr/bin/mysql-workbench-bin': corrupted double-linked list: 0x00007fde34004f80 ***



Reproducible: 

Steps to Reproduce:
Comment 1 Thomas Spuhler 2014-11-20 18:44:36 CET
Created attachment 5623 [details]
backtrace

error backtrace
Comment 2 Thomas Spuhler 2014-11-20 18:45:51 CET
Created attachment 5624 [details]
screenshot
David Walser 2014-11-20 19:54:19 CET

Assignee: bugsquad => juan.baptiste

Comment 3 Thomas Spuhler 2014-12-30 20:29:27 CET
The error is still present after fixing mariadb.
I recall seeing this before in maybe mga3 and it was resolved before the release.
Thomas Spuhler 2014-12-30 20:29:43 CET

CC: (none) => thomas

Comment 4 Thomas Spuhler 2015-02-22 19:04:27 CET
We need at least version 6.2.3. to connect with the new mariadb-10.0.x
I am trying to package version 6.2.4

Status: NEW => ASSIGNED

Comment 5 Thomas Spuhler 2015-02-23 04:43:47 CET
- upgraded in SVN to version 6.2.4
- asked for freeze push
Comment 6 Thomas Spuhler 2015-02-23 18:33:44 CET
I fixed this bug and will close it as resolved.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.