Bug 2454886 - Query Tool crashes with React error #130 in pgAdmin 9.14 (regression from 9.13)
Summary: Query Tool crashes with React error #130 in pgAdmin 9.14 (regression from 9.13)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pgadmin4
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sandro Mani
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-03 17:55 UTC by Mikhail
Modified: 2026-04-25 01:44 UTC (History)
1 user (show)

Fixed In Version: pgadmin4-9.14-3.fc42 pgadmin4-9.14-3.fc43 pgadmin4-9.14-3.fc44
Clone Of:
Environment:
Last Closed: 2026-04-23 00:56:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github pgadmin-org pgadmin4 issues 9816 0 None open Query Tool crashes with React error #130 in pgAdmin 9.14 (regression from 9.13) 2026-04-03 17:57:46 UTC

Description Mikhail 2026-04-03 17:55:31 UTC
## Describe the bug

Opening the Query Tool in pgAdmin 4 v9.14 immediately crashes with a blank white screen and React error #130 in the browser console:

```
Uncaught Error: Minified React error #130; visit https://react.dev/errors/130?args[]=undefined&args[]=
for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
```

Error #130 means "Element type is invalid: expected a string or a class/function but got: undefined" — a React component resolves to `undefined` during render.

**Downgrading to pgAdmin 9.13 immediately fixes the issue.**

## To Reproduce

1. Install pgadmin4 9.14
2. Launch pgAdmin, connect to any PostgreSQL server
3. Open the Query Tool (right-click database → Query Tool, or toolbar icon)
4. **Result**: blank white screen, React error #130 in browser console

This is 100% reproducible. Tested with:
- Clean `~/.pgadmin/` (fresh database, no prior state)
- `LLM_ENABLED = False` in config_local.py — same crash
- Both via QtWebEngine (pgadmin4-qt) and via a regular browser (Firefox, Chrome) with the standalone Flask server
- Two independent machines with identical software

### Confirming the regression

5. `sudo dnf downgrade pgadmin4 pgadmin4-qt` (back to 9.13)
6. Open the Query Tool
7. **Result**: works correctly

## Secondary symptom

If the user had Query Tool tabs open when they last used 9.13, the `Browser/Layout` value in the `setting` table of `pgadmin4.db` references those tabs. After upgrading to 9.14, pgAdmin crashes **on startup** (not just when manually opening the Query Tool), because layout restoration attempts to render the Query Tool component. This makes the app appear completely broken with no obvious workaround. Deleting `Browser/Layout` from the `setting` table restores the main UI, but the Query Tool remains broken.

## Environment

- **pgAdmin version**: 9.14-1.fc45 (crashes) / 9.13-1.fc45 (works)
- **Package type**: RPM, Fedora 45 (Rawhide), x86_64
- **Runtime**: pgadmin4-qt (unofficial Qt runtime) and standalone Flask + browser (Firefox/Chrome)
- **Qt WebEngine**: 6.10.2 (irrelevant — crash reproduces in regular browsers too)
- **Reproduced on**: 2 independent machines with identical software

## Browser console stack trace (Chrome DevTools, server mode)

```
Uncaught Error: Minified React error #130
    at Wr (vendor_react.js?ver=91400:2:63273)
    at m  (vendor_react.js?ver=91400:2:74129)
    at    vendor_react.js?ver=91400:2:76288
    at ls (vendor_react.js?ver=91400:2:114688)
    at dc (vendor_react.js?ver=91400:2:152088)
    at uc (vendor_react.js?ver=91400:2:151936)
    at sc (vendor_react.js?ver=91400:2:151728)
    at Xo (vendor_react.js?ver=91400:2:147527)
    at Bc (vendor_react.js?ver=91400:2:163195)
    at Lc (vendor_react.js?ver=91400:2:161664)
```

`ver=91400` corresponds to pgAdmin 9.14.00 internal version.

## pgadmin4-qt console output

```
Starting pgAdmin 4. Please navigate to http://127.0.0.1:34977 in your browser.
2026-04-03 20:11:31,352: WARNING	werkzeug:	Werkzeug appears to be used in a production deployment.
 * Serving Flask app 'pgadmin'
 * Debug mode: off
js: Uncaught Error: Minified React error #130; visit https://react.dev/errors/130?args[]=undefined&args[]=
for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
```

Comment 1 Fedora Update System 2026-04-09 22:32:32 UTC
FEDORA-2026-a3ae80e6ef (pgadmin4-9.14-2.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-a3ae80e6ef

Comment 2 Fedora Update System 2026-04-09 22:32:32 UTC
FEDORA-2026-9f900e2a1d (pgadmin4-9.14-2.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-9f900e2a1d

Comment 3 Fedora Update System 2026-04-09 22:32:37 UTC
FEDORA-2026-f968d6f296 (pgadmin4-9.14-2.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-f968d6f296

Comment 4 Fedora Update System 2026-04-10 01:33:20 UTC
FEDORA-2026-a3ae80e6ef has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-a3ae80e6ef`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-a3ae80e6ef

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-04-10 01:56:05 UTC
FEDORA-2026-f968d6f296 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-f968d6f296`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f968d6f296

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-04-10 02:19:22 UTC
FEDORA-2026-9f900e2a1d has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-9f900e2a1d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-9f900e2a1d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2026-04-15 00:52:40 UTC
FEDORA-2026-e9ecdd44c4 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-e9ecdd44c4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-e9ecdd44c4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2026-04-15 01:09:43 UTC
FEDORA-2026-34c2bf6df4 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-34c2bf6df4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-34c2bf6df4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2026-04-15 01:32:33 UTC
FEDORA-2026-b4633cbe23 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-b4633cbe23`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-b4633cbe23

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2026-04-23 00:56:28 UTC
FEDORA-2026-b4633cbe23 (pgadmin4-9.14-3.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2026-04-23 01:10:42 UTC
FEDORA-2026-e9ecdd44c4 (pgadmin4-9.14-3.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2026-04-25 01:44:40 UTC
FEDORA-2026-34c2bf6df4 (pgadmin4-9.14-3.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.