Transparency UI broken for new layer added by georeferencer #64545
Description
What is the bug or the crash?
When I try to change transparency settings in a Layer created by georeferencing, the table editor does not allow to set/change tolerance value.
Closing / reopening the Property dialog heals the problem
Steps to reproduce the issue
- start qgis
- menue: Settings / new profile
- close first window w/ previous profile
- 'new project from wgs 84'
- menue: Layer/ Georeferencer
- load raster
- add two match points (manually known lat / lon)
- check transformations settings - keep "load in project"
- click green triangle to start georeferencing
- switch to main window (keep georef open)
- right click on the new raster layer / Properties / Transparency
- hit green + to add a new line to "Transparent Pixel List"
- try to enter values, eg 255 / 255 / 255 / 20
I can successfully enter values in the color columns, but not in the Tolerance column.
The look&feel in the table edit UI seems weird beyond the third field.
When I close / reopen the Properties dialog, the bug disappears.
Now the table editor behaves normally.
I can set Tolerance value as intended.
Versions
| QGIS version | 3.40.6-Bratislava |
| QGIS code branch | Release 3.40 |
| Libraries | |
| Qt version | 5.15.15 |
| Python version | 3.13.3 (Compiled) 3.13.5 (Running) |
| GDAL version | 3.10.3 |
| PROJ version | 9.6.0 |
| EPSG Registry database version | v12.004 (2025-03-02) |
| GEOS version | 3.13.1-CAPI-1.19.2 |
| SQLite version | 3.46.1 |
| PostgreSQL client version | 17.4 (Debian 17.4-2) |
| SpatiaLite version | 5.1.0 |
| QWT version | 6.1.4 |
| QScintilla2 version | 2.14.1 |
| OS version | Debian GNU/Linux 13 (trixie) |
| Active Python plugins | |
| MetaSearch | 0.3.6 |
| db_manager | 0.1.20 |
| grassprovider | 2.12.99 |
| processing | 2.12.99 |
Supported QGIS version
- I'm running a supported QGIS version according to the roadmap.
New profile
- I tried with a new QGIS profile
Additional context
Reopening the Properties dialog appears to be a reliable workaround.
Nothing else appears to be broken even in projects where the bug happened dozens of times.
No reason to panic.