You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

Debian系统下MySQL Workbench保存/读取EER图时崩溃求助

Fix MySQL Workbench 6.3.10 Crash on Save/Load EER Diagram in Debian buster/sid

I’ve dealt with exactly this issue on Debian buster/sid before. The crash with the std::runtime_error about invalid locale names happens because MySQL Workbench 6.3.10 (a fairly old version) relies on specific locale configurations that aren’t properly set up in your system. Here’s how to fix it step by step:

Step 1: Check Your Current Locale Configuration

First, run this command to see what locales are active and available:

locale

Look for entries like en_US.UTF-8 — if you don’t see this (or it shows LC_ALL as empty/unset), that’s likely the root of the problem.

Step 2: Generate the Required Locale

If the en_US.UTF-8 locale isn’t present on your system, generate it with:

sudo locale-gen en_US.UTF-8

This creates the necessary locale files that Workbench needs to handle text encoding operations.

Step 3: Test with a Temporary Locale Override

To verify the fix immediately, launch MySQL Workbench with the LC_ALL environment variable forced to the valid locale:

LC_ALL=en_US.UTF-8 mysql-workbench

Try saving or loading your EER diagram now — it should no longer crash.

Step 4: Make the Fix Permanent

If the temporary fix works, you can set this locale globally so you don’t have to run the special command every time:

  1. Open the system locale configuration file with your preferred editor:
    sudo nano /etc/default/locale
    
  2. Replace or add these lines to the file:
    LC_ALL=en_US.UTF-8
    LANG=en_US.UTF-8
    
  3. Save the file (press Ctrl+O in nano, then Enter) and exit (Ctrl+X).
  4. Reload the locale settings without rebooting:
    source /etc/default/locale
    
    Or reboot your system to ensure all processes pick up the new settings.

Why This Works

MySQL Workbench 6.3.10 has strict locale requirements for handling text in EER diagrams (like table names, comments, and metadata). Debian buster/sid doesn’t always have en_US.UTF-8 enabled by default, and the app throws an unhandled error when it can’t find a valid locale to use. By forcing a valid UTF-8 locale, you eliminate this missing dependency and let the app handle text operations correctly.

内容的提问来源于stack exchange,提问作者Yehuda

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.22 09:37:49