Bug #110786 Check for Update
Submitted: 24 Apr 2023 16:48 Modified: 4 Jul 2023 13:53
Reporter: Harry Towner Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.33, 8.0.34, 8.0.36 OS:MacOS (13.3.3)
Assigned to: Marcin Marek CPU Architecture:ARM

[24 Apr 2023 16:48] Harry Towner
Description:
When selecting Check for Updates under the Help menu tab a message appears stating:

Error
Unhandled exception:
'CheckForUpdateThread' object has no attribute 'isAlive'
Check the log for more details.

How to repeat:
If you select Check for Updates again, no pop-up window appears. In order to check again, you must quit SQL Workbench and execute again. Again the same issue happens (error and then if checked again - nothing)
[26 Apr 2023 17:14] Levan Kekelidze
I can confirm this issue happens.
MacBook Pro 13'', Apple Silicon M1, macOS Ventura 13.3.1

Similar to the issue with the previous version of MySQL Workbench 8.0.32 the only workaround is to AGAIN downgrade to the version 8.0.31.

I naively thought that these crashes will be fixed in this new version 8.0.33 as it was promised on the following bug report page, but note - here we go again:
https://bugs.mysql.com/bug.php?id=109671

The only difference, is that now I can at least execute queries without crashes.  MySQL Workbench "confidently" crashes each time I quite the application (⌘Q).
[19 Jul 2023 12:03] MySQL Verification Team
Bug #111788 marked as duplicate of this one.
[19 Jul 2023 12:15] Levan Kekelidze
UPDATE

Updated MySQL Workbench from version 8.0.33 to the just released version 8.0.34 - the issue is still present.
[25 Jul 2023 11:37] MySQL Verification Team
Bug #111874 marked as duplicate of this one.
[31 Jul 2023 13:01] MySQL Verification Team
Bug #111752 marked as duplicate of this one.
[5 Oct 2023 11:16] MySQL Verification Team
Bug #112623 marked as duplicate of this one.
[26 Oct 2023 7:35] MySQL Verification Team
Bug #112821 marked as duplicate of this one.
[2 Nov 2023 13:06] MySQL Verification Team
Bug #112938 marked as duplicate of this one.
[15 Nov 2023 11:02] MySQL Verification Team
Bug #113073 marked as duplicate of this one.
[21 Nov 2023 12:19] MySQL Verification Team
Bug #113158 marked as duplicate of this one.
[23 Nov 2023 21:42] Michael Muryn
I had the same issue in version 8.0.12 that I installed in 2018.

I thought the update was maybe broken because it was an old version.  So I installed 8.0.34 and I got the same error.

Notes:
- Reinstalling over my old installation did not seem to lose my settings (at least connection settings)
- It looks like even in my old version I get the same error message and identified cause in the log.  Maybe old code that point to a resource that is no more existing.
[27 Jan 23:30] Ken Grammer
I am on version 8.0.32 and having this same issue.
[29 Jan 5:09] B L
This also appears on 8.0.36. Running on MPB M2 Max (Sonoma 14.3)
[19 Mar 16:20] Matthew Deleon
I can confirm this is still an issue on Windows 2022 Data Centre 21H2 on MySQL Workbench 8.0.36 Community (3737333 CE 64 bit)
[21 Mar 1:36] Damian Suess
Issue is happening for me as well on v8.0.36 build 3737333 CE (64 bit) Community
Microsoft Windows [Version 10.0.19045.4170]
[5 Apr 6:37] Jay Mehta
I can confirm this still happens in Windows 11 Pro OS Build 22631.3374

MySQL Workbench version: 8.0.34 build 3263449 CE
[29 Apr 12:55] MySQL Verification Team
Bug #114805 marked as duplicate of this one.
[3 May 12:37] Diogo Domanski Diogo
I can confirm this also happens in Ubuntu 24.04

MySQL Workbench version: 8.0.36 build 3737333 CE (64 bits)
[21 May 11:50] MySQL Verification Team
Bug #115067 marked as duplicate of this one.