QGIS Issue Tracking: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-04-24T14:29:48ZQGIS Issue Tracking
Redmine QGIS Application - Bug report #21921 (Feedback): 3.6.2 crashes on attempring to edit bad topologyhttps://issues.qgis.org/issues/219212019-04-24T14:29:48Zmuscatelle -muscatelle@foo.bar
<p>Attempted to edit a postgis layer which had worked without problem in previous versions, and QGIS crashed.<br />Started QGIS from the command line, created a new project and added only the problem layer - QGIS crashes on attempting an edit.<br />Error message is shown below:</p>
<p>:~$ qgis<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087<br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />Warning: GEOS exception: TopologyException: side location conflict at 408926.39374496252 -3921010.8875752087 <br />QGIS died on signal 11Could not attach to process. If your uid matches the uid of the target <br />process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try <br />again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf <br />ptrace: Operation not permitted. <br />No thread selected<br />No stack.<br />gdb returned 0<br />Aborted (core dumped)</p>
<p>setup:</p>
<p>QGIS version<br />3.6.2-Noosa<br />QGIS code revision<br />656500e<br />Compiled against Qt<br />5.9.5<br />Running against Qt<br />5.9.5<br />Compiled against GDAL/OGR<br />2.2.3<br />Running against GDAL/OGR<br />2.2.3<br />Compiled against GEOS<br />3.6.2-CAPI-1.10.2<br />Running against GEOS<br />3.6.2-CAPI-1.10.2 4d2925d6<br />PostgreSQL Client Version<br />10.7 (Ubuntu 10.7-0ubuntu0.18.04.1)<br />SpatiaLite Version<br />4.3.0a<br />QWT Version<br />6.1.3<br />QScintilla2 Version<br />2.10.2<br />PROJ.4 Version<br />493</p> QGIS Application - Bug report #21836 (Open): Copy/Paste fails in Postgis layer null value in col...https://issues.qgis.org/issues/218362019-04-11T13:14:04ZCATER Normandie
<p>When copy/past features from Shapefile layer to Postgis layer, an error occure "null value in column "gid" violates not-null constraint". Creating new feature work as expected.</p>
<p>Work well in QGIS 3.2 with same data.</p>
<p>Error occure with or without transaction group.</p>
<p>Don't know if something related with bug report <a class="issue tracker-1 status-1 priority-5 priority-" href="https://issues.qgis.org/issues/21788" title="Copy/Paste fails from one layer to another when layer has NOT NULL constraints and transaction gr... (Open)">#21788</a></p> QGIS Application - Bug report #21741 (Open): "Check geometries" tool does not fixes errors (overl...https://issues.qgis.org/issues/217412019-04-03T08:34:03ZAlberto Gravagrava.alberto@teletu.it
<p>Hi all!<br />I've some problems with the native plugin CHECK GEOMETRIES.<br />1 set the options for the geometry checking (I have a polygon layer and 've tried with multiple combination of options)<br />2 run the plugin (I've tried both creating a new layer and modifying the input layer)<br />3 the plugin finds the errors<br />4 run the repair proces (I've tried both using default option and asking correction method)<br />5 the plugin runs and tells that the errors are solved.</p>
<p>If I check the "solved" file it gives me tha same errors as before anche i close the plugin using 'close' botton o 'X' it close qgis whitout error message.</p>
<p>Leave attached a testing polyon layer.</p>
<p>thank you all!</p> QGIS Application - Bug report #21664 (Feedback): 3D view crashes QGIShttps://issues.qgis.org/issues/216642019-03-24T20:14:52ZKerstyn Perrettkerstynperrett@gmail.com
<a name="User-Feedback"></a>
<h2 >User Feedback<a href="#User-Feedback" class="wiki-anchor">¶</a></h2>
<p>Crashes when I try to open 3D map view</p>
<a name="Report-Details"></a>
<h2 >Report Details<a href="#Report-Details" class="wiki-anchor">¶</a></h2>
<p><strong>Crash ID</strong>: 7349d704daa2c61262730d89bd55bf88edd12297</p>
<p><strong>Stack Trace</strong><br /><pre>
QgsCoordinateTransform::transformBoundingBox :
QgsMapRendererJob::reprojectToLayerExtent :
QgsMapRendererJob::prepareJobs :
QgsMapRendererCustomPainterJob::start :
QgsMapRendererSequentialJob::start :
QgsTerrainGenerator::typeToString :
QgsTerrainGenerator::typeToString :
QgsFlatTerrainGenerator::createChunkLoader :
QgsWindow3DEngine::trUtf8 :
QgsWindow3DEngine::trUtf8 :
Qgs3DMapScene::updateScene :
Qgs3DMapScene::createTerrainDeferred :
QTimer::timeout :
QObject::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QEventDispatcherWin32::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QCoreApplicationPrivate::sendPostedEvents :
qt_plugin_query_metadata :
QEventDispatcherWin32::processEvents :
CallWindowProcW :
DispatchMessageW :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main :
BaseThreadInitThunk :
RtlUserThreadStart :
</pre></p>
<p><strong>QGIS Info</strong><br />QGIS Version: 3.4.5-Madeira<br />QGIS code revision: <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/89ee6f6e2334c1350c78a845ca36a46fe14bf012" title="Release of 3.4.5">89ee6f6e23</a><br />Compiled against Qt: 5.11.2<br />Running against Qt: 5.11.2<br />Compiled against GDAL: 2.4.0<br />Running against GDAL: 2.4.0</p>
<p><strong>System Info</strong><br />CPU Type: x86_64<br />Kernel Type: winnt<br />Kernel Version: 10.0.17134</p> QGIS Application - Bug report #20593 (Open): Action Toggle Editing called from QPushButton starts...https://issues.qgis.org/issues/205932018-11-22T13:38:27ZRaul Sangonzalodevelopment@cornwallconsultants.co.uk
<p>When <em>qgis.utils.iface.actionToggleEditing().trigger()</em> is called from a QPushButton on a form to enable/disable editing it causes to loop.</p>
<p>1. Press QPushButton. First time it enables or disables the Editing Mode of that layer.<br />2. Press again, it runs it twice (as if it was pressed twice), so you get to the same point.<br />3. Press again, it runs 4 times. Again, 8 times, etc.</p>
<p>We discovered it actually does the same thing with startEditing(). It keeps looping exponentially every time you press it (checked with printing statements). You can also see it's enable/disabling on the QGIS interface!</p>
<p>On 3.2 it worked fine, so we think this is a glitch from this version.</p> QGIS Application - Bug report #20433 (Open): "Merge Selected Feature" do not works correctly with...https://issues.qgis.org/issues/204332018-11-09T22:22:31ZJan Lippmann
<p>"Take Attributes from selected feature" takes not the value from the selected feature.</p>
<p><img src="https://issues.qgis.org/attachments/download/13723/feature_merge_hidden_id_2.gif" alt="" /></p> QGIS Application - Bug report #20367 (Open): "avoid intesection" cannot be enabled without activa...https://issues.qgis.org/issues/203672018-11-05T13:46:20ZAntonio Viscomiantoviscomi@gmail.com
<p><strong>New description:</strong></p>
<p>Subject says it all. This is NOT the case in 2.18.</p>
<p><strong>Old description:</strong></p>
<p>Hi all,<br />I noticed this bug:<br />- activate advanced snapping configuration enabling "Avoid Intersection" option on two layers;<br />- then I deactivate snap on one of two layers (but "Avoid Intersection" flag was not syncronized with layer flag);<br />- I tried to create a new polygon in my feature, but editing came out with error (geometry is collapsed);<br />- then I deactivated "Avoid Intersection" from unflagged layer;<br />- I created the new geometry and all works fine.</p>
<p>I attach a screencast that show this</p> QGIS Application - Bug report #20071 (Open): "Show feature count" on a rule based renderer gives ...https://issues.qgis.org/issues/200712018-10-10T13:47:18ZHarrissou Santanna
<p>This is a revival of <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/13999" title=""Show feature count" on a rule based gives wrong result for the "ELSE" statement. (Closed)">#13999</a>.<br />In the attached screenshots, I use the Else shortcut in one case and the full rule in the other. counted features are not the same:</p>
<p>1/ The "Route secondaire" level "instead of displaying 0" <a class="issue tracker-1 status-1 priority-5 priority-" href="https://issues.qgis.org/issues/20070" title="In rule based renderer, "Show feature count" returns 0 if no symbol is activated (Open)">#20070</a>, would return 296389 in one case (correct!) and, 304445 with the Else rule (corresponding to the whole layer).</p>
<p>2/ At the bottom of the rules, the <em>Autres</em> nature subclass should return 213037 features as of</p>
<p><code>select count(nature) from layer where importance not in ('1','2') and nature not in ('Bac auto', 'Escalier','Piste cyclable','Sentier','Chemin')</code></p>
but it instead returns the same value shown at its upper level:
<ul>
<li>296389 features which is the result of <code>select count(nature) from layer where importance not in ('1','2')</code></li>
<li>or 304445 features with the Else rule used for "Route secondaire".</li>
</ul> QGIS Application - Feature request #19609 (Open): Add color ramp item with tick and number label ...https://issues.qgis.org/issues/196092018-08-13T14:40:02ZZhe Fang1315479326@qq.com
<p>As shown in the picture attached, we usually use a color ramp rather than a legend to label a raster DEM layer, so we need a color ramp item that users get a certain gradient symbol based on the selected raster layer. Then users design its aspect(vertical or horizontal), width, height, interval of ticks, number of ticks, and font of number label.</p> QGIS Application - Bug report #19299 (Open): "Attribute Table" rows open randomly ordered? https://issues.qgis.org/issues/192992018-06-29T00:36:02ZLoren Amelangloren@pacific.net
<p>I've pretty much concluded the "Attribute Table" rows are randomly ordered unless you intentionally sort them - even if the actual shapefile is required to be in a specific order! Can this be?</p>
<p>The default order is not a problem of sorting numbers stored as text in the wrong numerical order. Typically 20 or 30 rows from near the top are relocated near the bottom, and almost all rows are randomized over a distance of maybe 10, as in 257, 251, 263, 262, 259, 266... If there is a pattern I don't see it.</p>
<p>If this is not a bug, could it be a feature request? When I view a shapefile I have created in a specific order, I'd like to see it displayed in that order!</p> QGIS Application - Feature request #18771 (Open): 1:n relations: new entries in child layer when...https://issues.qgis.org/issues/187712018-04-19T13:12:13ZGiovanni Manghigiovanni.manghi@gmail.com
<p><a class="external" href="https://docs.qgis.org/2.18/en/docs/user_manual/working_with_vector/attribute_table.html#id25">https://docs.qgis.org/2.18/en/docs/user_manual/working_with_vector/attribute_table.html#id25</a></p>
<p>If the child layer is a geometryless table then the actual (2.18/3) implementation has no problems.</p>
<p>The example referenced in the manual is about a scenario where the child is a table <strong>with</strong> geometries, so when the manual says</p>
<p>"The "+" button will add a new feature to the airport layer. And it will assign the new airport to the current region by default." this will effectively add a row in the child table but without the appropriate geometry, because in the relation form the possibility to digitize geometries for new child entries is not implemented.</p>
<p>This leave the data in a inconsistent state and is cause of confusion and data corruption. An similar example bases on geometry postgis tables shows that when saving edits for a new record in the child table, this new record is completely discarded with no message/warning/error whatsoever by QGIS.</p> QGIS Application - Bug report #17315 (Feedback): 3D Viewer: QGIS Crash when activating 3D Map vie...https://issues.qgis.org/issues/173152017-10-22T06:14:34ZLuca Casagrande
<p>QGIS cc96f51e62 Installed with OSGeo4W64</p>
<ul>
<li>Load test data (but any other data didn't work for me)</li>
<li>Start the New 3D Map View</li>
<li>Enable 3D renderer in the Layer Styling Panel</li>
</ul>
<p>The crash report window will open without any contents.<br />QGIS Main window does not respond.</p> QGIS Redmine (QGIS bug tracker) - Support #9741 (Open): SSH key upload and management is missinghttps://issues.qgis.org/issues/97412014-03-07T08:45:21ZAlex Mandeltech@wildintellect.com
<p>At some point the ability to manage keys for a user vanished. So new users can't upload their ssh key and existing users can't modify theirs. This mean new plugin authors can't store their code on hub, which has been requested. <a class="external" href="http://osgeo-org.1560.x6.nabble.com/uploading-plugin-files-to-hub-qgis-org-td5107396.html">http://osgeo-org.1560.x6.nabble.com/uploading-plugin-files-to-hub-qgis-org-td5107396.html</a></p>
<p>Did someone remove the Redmine Gitosis plugin or was Gitosis broken on a server update?<br />Was this server space related?</p> QGIS Application - Feature request #7235 (Open): Add option to avoid users producing invalid topo...https://issues.qgis.org/issues/72352013-02-25T07:27:11ZDuncan Golicherdgolicher@gmail.com
<p>Attempts to remove intersections when digitising over invalid topologies lead to unexpected behaviour. See bug <a class="issue tracker-1 status-5 priority-5 priority- closed" href="https://issues.qgis.org/issues/7225" title="QGIS crashes after failed intersect removal (Closed)">#7225</a> and related issues. The problem also extends to snapping and hole removal (bug <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/4880" title=""add feature" tool (for polygons) + "avoid intersection" is inconsistent when it is used to fill ... (Closed)">#4880</a>).<br />It would probably be safer overall if users were digitising with an option switched on that rejected all invalid polygons. If they do draw an invalid polygon they could be provided with a warning message, the invalid vertices marked, and the offending polygon would not be added to the layer until all the errors are fixed. This could be a default option as it would probably prevent users from forcing QGIS to run code that may have difficulty finding consistent ways of dealing with errors. The option to deactivate the checks should be provided, along with a clear warning of the possible consequences of doing so.</p> QGIS Application - Feature request #6255 (Feedback): Add button to force recalculating stats of r...https://issues.qgis.org/issues/62552012-08-27T04:27:53Zalobo -aloboaleu@gmail.com
<p>Currently QGIS relies on mean and sd values on the<br />GTif if present for stretching based on sd. Sometimes<br />this information can be wrong and gdalinfo -stats does<br />not force recalculating stats (see <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/5035" title="stretching with nb of standard deviation: always min = max = 0 (Closed)">#5035</a>).<br />The user should be able to force QGIS recalculating stats,<br />probably a button in Properties/Style would be a good option</p>