MySQL Bugs: #98918: "could not be fetched" displayed in object explorer for each type...

Bug #98918	"could not be fetched" displayed in object explorer for each type...
Submitted:	11 Mar 2020 20:59	Modified:	28 May 2020 12:33
Reporter:	R Farris	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S7 (Test Cases)
Version:	8.0.19	OS:	Windows (Microsoft Windows 10 Home)
Assigned to:	MySQL Verification Team	CPU Architecture:	x86
Tags:	WBBugReporter

Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\rscot\AppData\Roaming\MySQL\Workbench\log\wb.log]

The WB displays "Cannot be fetched" next to each object type.

Log says:
16:54:59 [INF][      Workbench]: UI is up
16:54:59 [INF][      Workbench]: Running the application
16:55:01 [ERR][  GRTDispatcher]: exception in grt execute_task, continuing: Exception: Access denied for user 'root'@'localhost' (using password: NO)
16:55:01 [ERR][  GRTDispatcher]: worker: task 'execute sql queries' has failed with error:.Access denied for user 'root'@'localhost' (using password: NO)
16:55:07 [INF][SQL Editor Form]: Opened connection 'Local instance MySQL80' to MySQL Community Server (GPL) version 5.7.26-log
16:55:07 [INF][        WQE.net]: Launching SQL IDE
16:55:08 [INF][        WQE.net]: SQL IDE UI is ready
16:55:08 [ERR][SQL Editor Form]: Error Code: 1143
SELECT command denied to user ''@'%' for column 'CaseID' in table 'dl_sessions'
16:55:08 [ERR][SqlEditorSchemaTree]: SQLException executing Error loading schema content: Error Code: 1143
SELECT command denied to user ''@'%' for column 'CaseID' in table 'dl_sessions'

How to repeat:
This occurs every time.  Dist C was updated and WB is at the latest version.

Also - SELECT command denied to user ''@'%' for column 'CaseID' in table 'dl_sessions'

What does this mean ?  I see no security against this column and have no issue selecting CaseID from the table.

Hello Farris,

Thank you for the bug report.
To investigate further this issue at our end, may I kindly request you to launch workbench under debug mode (-log-level=debug3) and provide unaltered workbench log file(more details about log are explained here - https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html), along with screenshot of the error. Thanks.

Regards,
Ashwini Patil

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".