Cannot save project in Geopackage when using QueryLayer in QGIS for Windows

[immoblecher]

What is the bug or the crash?

When creating a QueryLayer by right-clicking on a Geopackage layer in QGIS browser and "Execute SQL..." or when creating a QueryLayer with DB Manager, QGIS refuses to save the project in the same Geopackage, no matter if the project was saved before or new. The error message is:

_Unable to save project to storage geopackage:F:/Projekte/QGIS/test.gpkg?projectName=testing

Unable to insert or update project (project=geopackage:F:/Projekte/QGIS/test.gpkg?projectName=testing) in the destination table on the database: database is locked_

Tried latest LTR and 3.40.3 on Windows.

IMPORTANT: Works as expected on Ubuntu...no error (not sure why that would be; different locking mechanisms???)

Steps to reproduce the issue

1. Load or create any layer in Geopackage
2. Use 'Execute SQL...' from QGIS Browser to create a query layer from the same layer, or use DB manager to create QueryLayer
3. Save project in same Geopackage
4. Should produce error message

Versions

QGIS version	3.40.3-Bratislava
QGIS code revision	2a274ab7
Libraries
Qt version	5.15.13
Python version	3.12.8
GDAL/OGR version	3.10.1
PROJ version	9.5.1
EPSG Registry database version	v11.022 (2024-11-05)
GEOS version	3.13.0-CAPI-1.19.0
SQLite version	3.46.1
PDAL version	2.8.3
PostgreSQL client version	unknown
SpatiaLite version	5.1.0
QWT version	6.3.0
QScintilla2 version	2.14.1
OS version	Windows Server 2022 Version 2009
Active Python plugins
AppendFeaturesToLayer	2.0.0
changeDataSource	3.1
DataPlotly	4.2.0
db-style-manager	0.8
latlontools	3.7.3
nominatim	1.4.5
pg_raster_import	3.2.0
pluginbuilder3	3.2.1
processing_saga_nextgen	1.0.0
qgis_resource_sharing	1.2.0
quick_map_services	0.20.0
reloader	0.1
searchlayers	3.1.1
SelectByRelationship	0.3.3
SpreadsheetLayers	2.1.2
StyleLoadSave	1.0
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

No response

[immoblecher]

After some testing it seems this only happens with network drives. On local drives there is no problem. Why would that be? Locking network policy? Drive should not matter?

[agiudiceandrea]

@immoblecher, thanks for reporting. Just for clarity: it works as expected on Ubuntu even if the the geopackage file in which the project is stored is on a network drive? Have you actually tried if the issue occurs also using a new QGIS user profile? Do you know if the issue occurred in previous versions of QGIS?

[agiudiceandrea]

It looks similar to a previously reported issue #36832. What do you think @elpaso?

[immoblecher]

@agiudiceandrea , I have tried with a completely new user profile...same issue. On Ubuntu I presently do not connect to a network, but if I would, then probably through NFS or Samba, which is different to Windows network drives. So we wouldn't be able to compare, would we? But I can try with my home server over the weekend an see what happens.

I think this is a bit different to #36832 because "normal" vector layers in the project actually allow saving without problems. Its only when creating SQL QueryLayers where the problem starts.

Regarding previous QGIS versions I wouldn't know, sorry. I still have a 3.22 Flatpak QGIS version on my Ubuntu box, but that would probably not help in this case.