Bug #110297 Radio button in 'Server Logs' tab in 'Instance' section in Workbench duplicating
Submitted: 8 Mar 2023 1:38 Modified: 8 Apr 2023 14:01
Reporter: ABDULLAH SHERIFF Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:8.0.32 OS:MacOS (unknown)
Assigned to: MySQL Verification Team CPU Architecture:x86
Tags: WBBugReporter

[8 Mar 2023 1:38] ABDULLAH SHERIFF
Description:
----[For better reports, please attach the log file after submitting. You can find it in /Users/sheriffabdullah/Library/ApplicationSupport/MySQL/Workbench/log/wb.log]/Users/sheriffabdullah/Downloads/wb.log

How to repeat:
Go to MySQL Workbench.
Open a Server.
On the left pane, under the 'Instance' section, click on 'Server Logs'.
Among the 2 radio buttons 'All' & 'InnoDB', click on 'All'.

[Note:
In my computer, it says 
'Error creating log reader: [Errno 13] Permission denied: '/usr/local/mysql/data/mysqld.local.err' 
below these 2 options.]

Click on the 'Try again' button.

Now, you will see that the 2 radio buttons have duplicated. 
It did, on MySQL Workbench on MacBook Pro 2021 with M1 chip.

Suggested fix:
I'm not an app developer myself. All the best.
[8 Mar 2023 8:04] MySQL Verification Team
Hello ABDULLAH SHERIFF,

Thank you for the bug report.
Could you please provide screenshot of the issue?
Also, Please let us know the OS you are using. The log file says
OS detection failed, skipping OS support check. OS string: 'unknown'

Regards,
Ashwini Patil
[8 Mar 2023 10:49] ABDULLAH SHERIFF
OS Version: MacOS Ventura 13.1 (22C65)
[8 Mar 2023 14:01] MySQL Verification Team
Hi Mr. Abdullah,

This is actually not a bug in the WorkBench.

macOS has privilege system , like any other Unix. Hence, you should set up all the *nix directory/ file privileges to  the user that started WorkBench.

If you have other problems with WorkBench, please let us know .......
[9 Apr 2023 1:00] Bugs System
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".