Bug report #17201
QGIS master crashes when trying to expand a spatiaLite layer in the DB manager
| Status: | Closed | ||
|---|---|---|---|
| Priority: | High | ||
| Assignee: | - | ||
| Category: | DB Manager | ||
| Affected QGIS version: | master | Regression?: | Yes | 
| Operating System: | Windows 7 | Easy fix?: | No | 
| Pull Request or Patch supplied: | No | Resolution: | fixed/implemented | 
| Crashes QGIS or corrupts data: | Yes | Copied to github as #: | 25100 | 
Description
User Feedback¶
used the db manager and tried to expand a spatiaLite layer
Report Details¶
Crash ID: ed00957ba88838eccd4053109676694e37a47426
Stack Trace
(_spatialite) PyInit__spatialite (unknown file):(unknown line)
QGIS Info
QGIS Version: 2.99.0-Master
QGIS code revision: 01468d0879
Compiled against Qt: 5.7.1
Running against Qt: 5.7.1
Compiled against GDAL: 2.2.1
Running against GDAL: 2.2.1
System Info
CPU Type: i386
Kernel Type: winnt
Kernel Version: 6.1.7601
History
#1
    
    Updated by Giovanni Manghi about 8 years ago
    - Status changed from Open to Feedback
 - Priority changed from Normal to High
 
Please attach the data that causes the issue.
#2
    
    Updated by Gerhard Spieles about 8 years ago
    - File testspatialite1.zip added
 
Same Problem
Database ist attached
#3
    
    Updated by Gerhard Spieles about 8 years ago
    
    
    #4
    
    Updated by Giovanni Manghi about 8 years ago
    - Regression? changed from No to Yes
 - Status changed from Feedback to Open
 - Subject changed from QGIS crashes when trying to expand a spatiaLite layer in the DB manager to QGIS master crashes when trying to expand a spatiaLite layer in the DB manager
 
#5
    
    Updated by Andreas Kositz about 8 years ago
    - File python_db_spatialite_error.png added
 
Gerhard Spieles wrote:
Same Problem
Database ist attached
The "problem" changed, now QGIS does not crash anymore, it throws an error.
I used the dataset provided and attached a screenshot of the error.
#6
    
    Updated by Andreas Kositz almost 8 years ago
    After using this solution https://gis.stackexchange.com/a/260679/4972
No crash and no errors anymore, seems pretty much fixed.
#7
    
    Updated by Alessandro Pasotti almost 8 years ago
    Can we close this?
#8
    
    Updated by Giovanni Manghi almost 8 years ago
    - Status changed from Open to Feedback
 
#9
    
    Updated by Andreas Kositz almost 8 years ago
    Alessandro Pasotti wrote:
Can we close this?
I would say --> Closed.
I work with that on a daily basis and the bug does not occur anymore.
#10
    
    Updated by Giovanni Manghi almost 8 years ago
    - Resolution set to fixed/implemented
 - Status changed from Feedback to Closed