🐛 Report a Problem
Report a Problem
Good bug reports get fixed. Read through the checklist below, then email us — the more detail you include, the faster this gets resolved.
Gnorman Says
"It doesn't work" tells me nothing. "It crashes when I double-click a row in a view with no primary key on macOS 15.3 running MySQL 8.0.36 over SSH" — now we're talking.
Required Information
Every bug report should include all of the following:
- SQL Gnome version
- macOS version
- MySQL or MariaDB version
- Connection type: direct or SSH tunnel
- Exact steps to reproduce from a clean state
- Expected result
- Actual result
- Exact error message, if any
Screenshots or short screen recordings are useful for UI issues, but they should supplement reproduction steps — not replace them.
Context That Helps
These aren't always required, but they often speed things up significantly:
- Whether the issue happens only on first connect, or on every attempt.
- Whether it affects one table, one database, or all connections.
- Whether the server is local, remote, behind a VPN, or accessed through SSH.
- Which area is affected: Content, Structure, Query, import/export, or licensing.
- Whether the problem disappears after the first action.
SQL & Schema Issues
For issues related to queries, table structure, or row editing, also include:
- Database name
- Table or view name
- SQL statement, if relevant
- Whether the table has a primary key or unique index
- Whether the object is a base table or a view
Performance Issues
For slow or unresponsive behavior, include:
- Approximate row count of the table
- Whether the delay is limited to the first load
- Whether reopening the same table is fast afterward
- Console timing logs, if available
Exact reproduction steps are far more useful than descriptions like "slow" or "sometimes fails." If it only happens sometimes, describe the conditions under which it does and doesn't occur.
Ready to send your report?
Include all the relevant info above and we'll get back to you.