Mysql-workbench 5.2.33GA is available http://wb.mysql.com/?p=1043 Could we have a newer version? Thnx. Reproducible: Steps to Reproduce:
I pushed 5.2.33b
Status: NEW => RESOLVEDCC: (none) => balcaen.johnResolution: (none) => FIXED
New version .34 is out wich fixes lots of bugs. Could we have a update? Thnx.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Version 5.2.35 available now, but no maintainer
CC: (none) => marja11
Adding a note that 5.2.34 fixed several crash bugs when run under KDE due to issues with how GTK+ themes were being handled. As I can reliably crash this application by simply trying to import a SQL file, I have raised severity to major as the functionality of the tool is heavily impacted.
CC: (none) => motokochanSeverity: normal => major
(In reply to comment #4) > Adding a note that 5.2.34 fixed several crash bugs when run under KDE due to > issues with how GTK+ themes were being handled. > > As I can reliably crash this application by simply trying to import a SQL file, > I have raised severity to major as the functionality of the tool is heavily > impacted. @ Michael I'm confused as to how to interpret what you say. Do you mean it crashes when using mysql-workbench 5.2.34-2.mga2 ? That is the version we have in cauldron, now. Or are the crashes in mga 1, with version 5.2.33b-1.mga1 ?
Keywords: (none) => NEEDINFOComponent: New RPM package request => RPM PackagesSummary: Mysql-workbench new version available => Mysql-workbench crashesSource RPM: (none) => mysql-workbench 5.2.34-2.mga2 mysql-workbench 5.2.33b-1.mga1
5.2.33b in mga1. I missed that this was targeted toward Cauldron. Should I start a new bug?
(In reply to comment #6) > 5.2.33b in mga1. I missed that this was targeted toward Cauldron. Should I > start a new bug? The same bug in a different version of Mageia should indeed go into a seperate bug report. But maybe it is already there, I don't have time now to read what this bug is exactly about: https://bugs.mageia.org/show_bug.cgi?id=2761 It is about the same version of mysql-workbench. Setting this cauldron bug to resolved fixed status
Keywords: NEEDINFO => (none)Status: REOPENED => RESOLVEDResolution: (none) => FIXEDSource RPM: mysql-workbench 5.2.34-2.mga2 mysql-workbench 5.2.33b-1.mga1 => mysql-workbench 5.2.34-2.mga2