Bug report #7485
Open Attribute Table causes QGIS to crash (for clipped layer)
|Affected QGIS version:||master||Regression?:||No|
|Operating System:||Ubuntu 12.04||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||16437|
I just clipped a layer of contiguous polygons using qgis's inbuilt 'clip' function.
The result opens fine, but causes a crash when you try to open the attribute table.
The attribute table opens fine for other shapefiles, so guess it's clip's fault.
Would be interested if this problem is replicated in other versions (see attached).
#2 Updated by Matthias Kuhn over 8 years ago
- Status changed from Open to In Progress
Was caused by the second last column which seems to have no name (empty string)
The following patch makes this more stable:
Still, the problem persists, that QgsExpression is unable to handle an empty attribute name.
#4 Updated by Robin Lovelace over 8 years ago
Many thanks to speedy update.
Could not verify that the fix works on latest qgis version on my system, however (supplied by the following repos:
#deb http://qgis.org/ubuntugis-nightly precise main
#deb-src http://qgis.org/ubuntugis-nightly precise main)
Opening the files caused a crash, but this may have because of problems with python-qgis, which occurred while upgrading the system (see terminal report below). Instead I've reverted to qgis 1.8.0-1~precise3, which opens the attributes fine.
"pycentral: pycentral pkginstall: error byte-compiling files (539)
pycentral pkginstall: error byte-compiling files (539)
dpkg: error processing python-qgis-common (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python-qgis:
python-qgis depends on python-qgis-common (= 1.9.0+git20130401+af7d6f8~precise-ubuntugis1); however:
Package python-qgis-common is not configured yet.
dpkg: error processing python-qgis (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates it's a follow-up error from a previous failure.
Errors were encountered while processing: