-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when in DB Manager, trying to browse a PostgreSQL DB #28583
Comments
Author Name: Giovanni Manghi (@gioman) Any db on any server? I cannot replicate here on both Linux and Windows.
|
Author Name: Frode Wiseth Jørgensen (@frodewj) Local Postgre v9.6 on Windows 10. |
Author Name: Giovanni Manghi (@gioman) Frode Wiseth Jørgensen wrote:
so to e clear:
but if you only add the shapefile in (1) then it does not crash? |
Author Name: Frode Wiseth Jørgensen (@frodewj) Correct |
Author Name: Giovanni Manghi (@gioman) Frode Wiseth Jørgensen wrote:
provide the wmts url and the shapefile (even better a project with the necessary data), thanks. |
Author Name: Giovanni Manghi (@gioman) Frode Wiseth Jørgensen wrote:
also try on a new/clean profile. |
Author Name: Frode Wiseth Jørgensen (@frodewj) Example shape file and a project with a wmts layer
|
Author Name: Giovanni Manghi (@gioman) I cannot really replicate in any way, on both Linux or Windows. |
Author Name: Frode Wiseth Jørgensen (@frodewj) Thanks for the effort, new/clean profile fixed it. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Frode Wiseth Jørgensen (@frodewj)
Original Redmine Issue: 20763
Affected QGIS version: 3.4.2
Redmine category:db_manager
User Feedback
Crash when in DB Manager, trying to browse a PostgreSQL DB
Report Details
Crash ID: e61981e0d953eba111ea0db98b5ac3c95a10dca1
Stack Trace
QGIS Info
QGIS Version: 3.4.2-Madeira
QGIS code revision: 22034aa
Compiled against Qt: 5.11.2
Running against Qt: 5.11.2
Compiled against GDAL: 2.3.2
Running against GDAL: 2.3.2
System Info
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 10.0.17134
The text was updated successfully, but these errors were encountered: