Hi,

Can you provide detailed steps of how to reproduce the error ? after configuring a connection and clicking on "Server Administration" it doesn't do anything.

I have the same error. After configuring a connection and clicking on "Server Administration" it doesn't do anything (only message appears on program status line "Administration plugin not found"). However it must invoke server administration window (or tab) eg. for user management.

May there is missing amdin plugin in /usr/lib/mysql-workbench/plugins/ ?

CC: (none) => hazard157

Latest version 5.2.44 of mysql-workbench is available on cauldron, for me the
issue is fixed, can the bug reporter test too ?

Now administration works OK, as well as any other workbench plugin. Closing the bug.

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

Reopening as this was only fixed on cauldron, is still broken on mga 2, currently working on a fix.

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

Ok, there's an updated version for mga 2 in core/updates_testing that fixes this issue. Reassigning to QA for tests.

Assignee: juan.baptiste => qa-bugs

Could you list srpms and rpm's please Juan.

Thanks.

You forgot to add yourself to CC. Could you see comment 7 please Juan.

Thanks!

CC: (none) => juan.baptiste

Sorry, I thought that I would get automatically added after commenting on the bug ?? here are the packages:

source rpm:

mysql-workbench-5.2.36-3.mga2.src.rpm

binary rpms:

mysql-workbench-5.2.36-3.mga2.x86_64.rpm
mysql-utilities-1.0.0-0.5.2.36.2.mga2.noarch.rpm
mysql-workbench-debug-5.2.36-3.mga2.x86_64.rpm


Althought I just realized that I forgot to add the %subrel, and instead incremented %mkrel while doing my local tests. What should be done here, ask an admin to remove this version so I can push the package again with the correct subrel ? (mkrel 2.1 instead of 3)

That's the best way Juan, or add sysadmin to CC and ask here on the bug, whichever you prefer.

I don't think it adds to to CC automatically if you are currently the assignee btw. There is a setting to disable it adding you automatically too in your personal prefs.

Ok version fixed, new packages on core/updates_testing:

source rpm:

mysql-workbench-5.2.36-2.1.mga2.src.rpm

binary rpms:

mysql-workbench-5.2.36-2.1.mga2.x86_64.rpm
mysql-utilities-1.0.0-0.5.2.36.2.1.mga2.noarch.rpm
mysql-workbench-debug-5.2.36-2.1.mga2.x86_64.rpm

Testing complete on Mageia 2 i586 and x86-64.

Found the skip-networking has to be commented out in /etc/my.cnf.
Then adding and accessing the localhost server is working.

Could someone from the sysadmin team push the srpm
mysql-workbench-5.2.36-2.1.mga2.x86_64.rpm
from Mageia 2 Core Updates Testing to Core Updates.

Advisory: Bugfix update of mysql-workbench now allows adding a server.

https://bugs.mageia.org/show_bug.cgi?id=6718

Keywords: (none) => validated_update
CC: (none) => davidwhodgins, sysadmin-bugs
Whiteboard: (none) => MGA2-64-OK MGA2-32-OK

Update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0230

Status: REOPENED => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED

mmm I think the advisory description is wrong, it says:

"Bugfix update of mysql-workbench now allows adding a server."

And this bug is not about that, is about the admin plugin not loading, but you can connect to any server without problems (but you can't administer it). I think that description is more suitable for bug 5146, which is still open and it's about not being able to connect to a server.

It's usual for the packager to provide the advisory to QA Juan.

Please see https://wiki.mageia.org/en/Updates_policy#Maintainer_.28or_any_interested_packager.29

When the update is pushed, a notification is sent to the updates ML and a page created on the wiki, you could change the wiki page to a more accurate description if you like, for historical correctness.