MySQL Bugs: #87862: MySQL does not work on MacOS High Sierra

Bug #87862	MySQL does not work on MacOS High Sierra
Submitted:	26 Sep 2017 7:27	Modified:	21 Nov 2017 15:00
Reporter:	austin woz	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	6.3.9	OS:	MacOS
Assigned to:		CPU Architecture:	Any

Description:
Since upgrading to High Sierra released today to the public I am no longer able to use Workbench, bummer. 
It opens and I can connect but when I run query I get no results. 

Also if I open the adminstrator part and view open connections I get message about permissions, yet I have all the permissions needed and can get the results with show processes. 

How to repeat:
execute a query

no results

Attachment: high-sierra.png (image/png, text), 1.45 MiB.

Thank you for the bug report.

https://bugs.mysql.com/bug.php?id=86649 marked as duplicate of this one.

+1 for this, same issue, no results show in the results grid even though results were returned.

Same issue and it continuously loops causing me to force quit the application

same bug for this, no results grid

I am facing same issue on Mac OS High Sierra. Please fix this bug ASAP.

+1. Poor form. This was first reported in June.

Same fault.

Same here. Please fix it ASAP, as I can't work without Workbench..

I can't even close the application, I have to force it to close

Seems to connect ok but as noted above no Results Window / seems to hang and have to close App. Bit of an issue if you just want to run a query and export the results as .csv.

For now I have switched over to DBeaver. It at least allows me to be able to execute queries and scripts without having to exclusively rely on running them in a terminal window.

I believe defect #87714 is a duplicate containing a proposed code fix.

I'm also affected here with no results window displaying after a query successfully executes... also on the public release of 10.13 High Sierra... 

Shot in the dark here, but how long does an S1 "Critical" severity typically take to get fixed by MySQL? Anyone know?

I can't even get past the initial screen to make a connection.

Any progress on this ?

+1. Can execute one singe query which succeeds and tells me how many rows were returned, but doesn't show them. Then trying another query just spins, and the application must be forcibly closed.

I have downgraded to version 6.1.7 and it works correctly.

While fix the bug, I can work....

https://bugs.mysql.com/bug.php?id=87891 marked as duplicate of this one.

+1 - Runs the query. No results. Downgraded to 6.1.7. and still seeing the same issues. Help us Oracle. You're our only hope.

Downgrading to 6.1.7 worked for me, I tried the next stable release version 6.2.3 but that didn't work, so from my experimentation 6.1.7 is the most recent version that works.

I tried uninstalling and reinstalling 6.1.7 and now it works. Thanks everyone

if your looking for a workable solution i found "Navicat" to be a reasonable product.  I still prefer workbench when it works, but do really like Navicat's awesome query builder GUI. If only workbench had this feature and worked of course.

I just installed Oracle SQL Developer, and the MySQL JDBC connector. Connected to my databases, looks like it will work:

http://www.oracle.com/technetwork/developer-tools/sql-developer/overview/index.html

https://www.mysql.com/products/connector/

Instructions:

http://www.oracle.com/technetwork/developer-tools/sql-developer/mysql-connection-viewlet-s...

This bug is most likely a repeat of the same issue when MacOS sierra was released, the issue details here. Don't hold your breath, see how long this one took to be fixed. It looks like workbench is no longer in active development. 

https://bugs.mysql.com/bug.php?id=83658

Well, the @MySQLWorkbench Twitter account was kind enough to get back to my plea for help yesterday... but the answer didn't show much urgency which wasn't quite very reassuring - "I'm afraid this will take a few weeks to fix. But we are aware of the problem..."

https://twitter.com/MySQLWorkbench/status/913081672517718016 

Sooooo... don't hold your breath...

https://bugs.mysql.com/bug.php?id=87905 marked as duplicate of this one.

Installed 6.1.7 and it's working (displaying results pane, with actual results) correctly.

https://bugs.mysql.com/bug.php?id=87924 marked as duplicate of this one.

https://bugs.mysql.com/bug.php?id=87931 marked as duplicate of this one.

Really unfortunate - bug appeared LIVE in class during my lecture/demo.  80 students.

80 students, gets them all to subscribe to this bug. Unfortunately workbench is not important to Oracle and doesn't get much development time unless it looks important so those subscribes help

Yes it affects me! I use workbench for work. Pls prioritize this. Thanks so much! :)

Duplicate of Bug #87714

yes, it affects me! Pls fix!

I've downgraded to ver6.0.9 and it seems working.

Affected by this bug on 10.13 (17A405). Connects to DB successfully over SSH, queries appear to run, however, no results appear even though a response is acknowledged and the query is marked complete. After attempting any additional query, app gives bottom status bar as "Query Completed", but Action Output does not show the second query completed, the query tab shows the "working" spinning gear, and the app can only be force-quit as attempting to quit gives error "Cannot close SQL IDE while being busy"

+1

+1

Bob Davenport complied a version of workbench that works.  Check out this bug report...  

https://bugs.mysql.com/bug.php?id=87714

I had the same issue with the official release of High Sierra 10.13 (17A405). Query would appear to run, but the tables never showed up.

I downgraded to 6.1.7 and it seems to work fine with High Sierra.

Will be very pleased when the official MySQL newest version works properly with High Sierra.

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

Exact same problems. This means that MySqlWorkbench is now useless, as I can't see results of queries or do any sort of data edits using the tool.  

Not sure what in the OS update affects things like this, but it would seem to point to poor coding in the application, since I've seen none of my tools have any issues after the update.

Ben Sevier

Also experiencing this issue. No results when I run an initial query, then the application just loops/locks requiring a force close.

I am not expert here but it seems we have number of Bugs that have been marked as a duplicate of this but this Bug #87862 also has a status of Duplicate... I am not sure is that matters or not but I was trying to track down the Bug # with the Active status to see what the status was and I failed. Perhaps someone more skilled can point me at it.  My worry is all related Bugs are now duplicates and none Active so maybe no one will be looking at this - hopefully I have this all wrong!

If people would actually read instead of blindly adding +1 to a bug report that is clearly marked as a duplicate, it would be much more obvious what the bug number is it duplicates.

See my comment from Oct 5th. This bug duplicates bug #87714, which is already marked as fixed.

+1

Bob's fix worked for me. Thanks Bob for the great and easy to implement solution.

Why is #87714 marked as fixed if the solution is to download a version held on someone’s personal hosting. It should be marked as fixed when 6.3.10 is released to public.

When the version 6.3.10 will be ready?
I downgraded to 6.1.7 but this version have many errors and crash in many situations.

patently waiting on 6.3.10 as i still cant use workbench

hasn't been resolved and released to public. waiting on version 6.3.10

In another post, Bob modified workbench and fixed the issue. Works Flawless for me on Mac HighSiera here is the link: https://bugs.mysql.com/bug.php?id=87714

I am well aware that Bob kindly made a fix, but I need an official fix downloadable from this website. I have customer data on my servers I cant use tools from someone personal hosting even if bob appears genuinely nice and helpful. Neither can you, the ICO will take a dim view.

Looks like 6.3.10 was released a few days ago which works with High Sierra. Downloadable from https://dev.mysql.com/downloads/workbench/

The updated mention by Richard Willis-Owen works for me on High Sierra 10.13.1

thank you to the developer

Thanks for the confirmation!

I happened across this report after updating to High Sierra 0.13.3 (17D47) and then not seeing query results. I followed the advice and updated to MySQL Workbench 6.3.10 but not it's not recognizing the connection using id_rsa key. Keeps asking for the password.

I can ssh directly into the server as my user with the key in place without a problem.

Any thoughts?

I will not use MySQL Workbench anymore. It took long time to fix this critical bug.