QGIS Issue Tracking: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-05-24T06:08:29ZQGIS Issue Tracking
Redmine QGIS Application - Bug report #22134 (Open): Unable to copy selected rows from attibute table whi...https://issues.qgis.org/issues/221342019-05-24T06:08:29ZURIIT URIITkupr@uriit.ru
<p>While the “Dock Attribute Table” button is pressed, it is not possible to copy all selected lines in the attribute table using the “Ctrl + c” key combination.<br />After undocking the attribute table, everything works fine.</p>
<p><img src="https://issues.qgis.org/attachments/download/14979/1.png" alt="" /></p> QGIS Application - Bug report #22133 (Feedback): form not loaded properly from qml filehttps://issues.qgis.org/issues/221332019-05-23T15:22:48ZRobin Rotsaertrobin.rotsaert@limburgs-landschap.be
<p>when saving the form-information from one geopackage-layer as a qml-file and trying to load it to another geopackage-layer (both have some entirely equal columns) only the "general" form setup is loaded. The widget type isn't, the defaults neither (haven't checked on the constraints).</p> QGIS Application - Bug report #22132 (Feedback): Slow Vector Layer Line Rendering Speedhttps://issues.qgis.org/issues/221322019-05-23T12:20:15ZDavid MacNeildavid_macneil@hotmail.com
<p>I've had layer rendering speed issues since going from 3.2 to 3.4 which continued on up to 3.6.3. The GPS traces in an 820 MB spatialite database take many times as long to draw as they used to.</p>
<p>Today I stumbled across a workaround for it by accident. When I reduced the line width from the default to 0.03 in order to render a high resolution png, the old performance level was restored. I could increase the line width to 0.13 without a performance hit, but 0.14 or higher and back to molasses.</p>
<p>I'm unsure if there is something special in general about the transition between line thickness at those numbers, or if it maybe be the thickness in my data at which the many parallel lines become wide enough to start overlapping.</p> QGIS Application - Bug report #22130 (Feedback): qgis crashed in the backgroundhttps://issues.qgis.org/issues/221302019-05-23T06:30:13ZKarsten Teblingkarsten.tebling@gmail.com
<a name="User-Feedback"></a>
<h2 >User Feedback<a href="#User-Feedback" class="wiki-anchor">¶</a></h2>
<p>qgis crashed in the background while I was using Firefox, I had one shapefile open, one non-permanent output and one WMS. I recently made a fresh install of qgis with purging all profiles, so this should somewhat be a clean install, I only have one plugin installed by now.</p>
<a name="Report-Details"></a>
<h2 >Report Details<a href="#Report-Details" class="wiki-anchor">¶</a></h2>
<p><strong>Crash ID</strong>: 7d29924f4829425ab791f7ff594e8177cc850b2c</p>
<p><strong>Stack Trace</strong><br /><pre>
QMapDataBase::freeNodeAndRebalance :
QgsAuthMethodRegistry::operator= :
QMetaObject::activate :
QThread::finished :
QThread::currentThreadId :
QThread::start :
BaseThreadInitThunk :
RtlUserThreadStart :
</pre></p>
<p><strong>QGIS Info</strong><br />QGIS Version: 3.6.3-Noosa<br />QGIS code revision: <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/0c5774c0685d4b6f3e92a086234455708d1cd427" title="Release of 3.6.3">0c5774c068</a><br />Compiled against Qt: 5.11.2<br />Running against Qt: 5.11.2<br />Compiled against GDAL: 2.4.1<br />Running against GDAL: 2.4.1</p>
<p><strong>System Info</strong><br />CPU Type: x86_64<br />Kernel Type: winnt<br />Kernel Version: 6.1.7601</p> QGIS Application - Bug report #22129 (Feedback): QGIS crashes when opening a new projecthttps://issues.qgis.org/issues/221292019-05-23T04:54:23ZNeil Bombardiernbombardier@svc.nsw.gov.au
<p>QGIS 3.6.2 crashed when opening a new project</p>
<a name="User-Feedback"></a>
<h2 >User Feedback<a href="#User-Feedback" class="wiki-anchor">¶</a></h2>
<p>trying to open a different project</p>
<a name="Report-Details"></a>
<h2 >Report Details<a href="#Report-Details" class="wiki-anchor">¶</a></h2>
<p><strong>Crash ID</strong>: d89364a0253e3b92c7eb9e4bc5327eee1e254b05</p>
<p><strong>Stack Trace</strong><br /><pre>
QList<QItemSelectionRange>::empty :
QUndoStack::canRedo :
QgsUndoWidget::indexChanged :
QMetaObject::activate :
QUndoStack::clear :
QUndoStack::~QUndoStack :
QgsProjectFileTransform::operator= :
QObjectPrivate::deleteChildren :
QObject::~QObject :
QgsVectorLayerUndoCommandRenameAttribute::~QgsVectorLayerUndoCommandRenameAttribute :
QgsMapLayerStore::removeMapLayers :
QgsMapLayerStore::removeMapLayers :
QgsMapLayerStore::removeAllMapLayers :
QgsProject::clear :
QgisApp::closeProject :
QgisApp::addProject :
QgisApp::openProject :
QMetaObject::activate :
QMenu::~QMenu :
QMetaObject::activate :
QAction::activate :
QMenu::actionGeometry :
QMenu::actionGeometry :
QMenu::mouseReleaseEvent :
QWidget::event :
QMenu::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QApplicationPrivate::sendMouseEvent :
QSizePolicy::QSizePolicy :
QSizePolicy::QSizePolicy :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QGuiApplicationPrivate::processMouseEvent :
QWindowSystemInterface::sendWindowSystemEvents :
QEventDispatcherWin32::processEvents :
TranslateMessageEx :
TranslateMessage :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main :
BaseThreadInitThunk :
RtlUserThreadStart :
</pre></p>
<p><strong>QGIS Info</strong><br />QGIS Version: 3.6.1-Noosa<br />QGIS code revision: <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/2468226bc97b78ef3b193ac2883b7d3de9e3b4d1" title="osgeo4w: updates for grass 7.6.1 (cherry picked from commit a19fc89e5fb71b9e30de7196494b247f243a...">2468226bc9</a><br />Compiled against Qt: 5.11.2<br />Running against Qt: 5.11.2<br />Compiled against GDAL: 2.4.1<br />Running against GDAL: 2.4.1</p>
<p><strong>System Info</strong><br />CPU Type: x86_64<br />Kernel Type: winnt<br />Kernel Version: 6.1.7601</p> QGIS Application - Bug report #22087 (Open): GRASS Region Extent not shown in Batch Modehttps://issues.qgis.org/issues/220872019-05-15T16:22:49ZPedro Venânciopedrongvenancio@gmail.com
<p>When using Processing GRASS algorithms in batch mode, the GRASS_REGION_EXTENT_PARAMETER is not shown.</p>
<p>This happens in QGIS 3.4.7 and QGIS 3.6.2, but seems ok in 3.7 (master).</p>
<p>To reproduce:</p>
<p>1. Run a GRASS algorithm. For instance, v.to.rast. In 'Advanced parameters' you see "GRASS GIS 7 region extent (xmin, xmax, ymin, ymax) [optional]".<br />2. Run the same algorithm as Batch Process.<br />3. Toggle to advanced mode.<br />4. The "GRASS GIS 7 region extent (xmin, xmax, ymin, ymax)" column is not shown.</p> QGIS Application - Bug report #22049 (Feedback): Persistent crashes when editing nodeshttps://issues.qgis.org/issues/220492019-05-12T11:39:53ZKevan Delaneykevan.delaney@yahoo.com
<p>Cause: editing one of 3 vector layers or creating a new polygon in one of them. <br />Symptom: The screen freezes, the pointer starts drawing a blue rectangle with the one corner stuck on the screen where it first froze. The pointer cannot select entities but when dragged over to the menus I can save the layers and sometimes even the project before it crashes totally - after 10 seconds or so.<br />Tried: new project, tried faster computer, tried saving layers as Spatialite tried 3.4.7 Madiera, tried splitting some longer lines into shorter segments and this seemed to work at first. <br />2 of the vector layers were created originally from MapInfo and geometry adjusted by hand to match Aerial Image. <br />Am using an external hard drive (portability). Will try to migrate all to the newer computer's internal drive.</p> QGIS Application - Bug report #21986 (Open): Can not save data of type "array of characters (Stri...https://issues.qgis.org/issues/219862019-05-03T10:58:37ZMickaël CALLACmickael.callac@lannion-tregor.com
<p>Test environment:<br />QGis 3.4.7-1 (LTR)<br />database: spatiaLite</p>
<p>The error appears in the case of a layer connected to a base SpatiaLite (generated by ogr2ogr) and for an array type field characters. The field in QGis has been set as "value relational ", the option" Allow multiple selections "is checked.</p>
<p>The field in QGis has the following properties:</p>
<p>Type: QString<br />Identity type: StringList<br />This is a field of type "JSONSTRINGLIST" in the base spatiaLite<br />When saving this field, the following error appears: 2019-05-03T11: 39: 48<br />CRITICAL Layer name layer: Type 5 of the x attribute of the entity y is unknown.</p> QGIS Application - Bug report #21775 (Open): qgis crash when filtering a layer with an attachment...https://issues.qgis.org/issues/217752019-04-05T08:41:44ZSergii Brazhynenkosbrazhinenko@yahoo.com
<p><strong>qgis crash when filtering a layer with an attachment field</strong></p>
<p>Crash ID: f40bf397c5155333687146b59354eebf255adf60</p>
<p>Stack Trace<br /><pre>
QtPluginWidgetAdapter::~QtPluginWidgetAdapter :
WebCore::ImageDocument::imageElement :
WebCore::ImageDocument::imageElement :
WebCore::DocumentWriter::end :
QWebFrame::setUrl :
QgsExternalResourceWidget::loadDocument :
QMetaObject::activate :
QgsFileWidget::fileChanged :
QMetaObject::activate :
QLineEdit::qt_static_metacall :
QMetaObject::activate :
QWidgetLineControl::finishChange :
QWidgetLineControl::internalSetText :
QgsExternalResourceWidgetWrapper::setValue :
QgsEditorWidgetWrapper::setFeature :
QgsAttributeForm::resetValues :
QgsAttributeForm::setFeature :
QgsDualView::mFeatureList_currentEditSelectionChanged :
QMetaObject::activate :
QgsFeatureListView::currentEditSelectionChanged :
QgsFeatureListView::editSelectionChanged :
QMetaObject::activate :
QItemSelectionModel::emitSelectionChanged :
QItemSelectionModel::select :
QItemSelectionModel::select :
QgsFeatureListViewDelegate::~QgsFeatureListViewDelegate :
QMetaObject::activate :
QTimer::timerEvent :
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 :
QGIS Info
QGIS Version: 3.6.1-Noosa
QGIS code revision: 2468226bc9
Compiled against Qt: 5.11.2
Running against Qt: 5.11.2
Compiled against GDAL: 2.4.1
Running against GDAL: 2.4.1
System Info
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 10.0.17134
</pre></p> QGIS Application - Bug report #21586 (Open): Windows and Processing Raster calculator pyqgis trou...https://issues.qgis.org/issues/215862019-03-14T15:00:13Zmatteo ghettamatteo.ghetta@gmail.com
<p>The bug seems to be related ONLY on Windows system. A small dataset in attach.</p>
<p>Briefly: it seems that when using the Processing Raster calculator in Windows via pyqgis, it is not possible to use raster(s) entire path(s). Only raster names loaded in the TOC are available.</p>
<p>To reproduce the error:</p>
<ul>
<li>load the attached `calculated` raster in the TOC</li>
<li>run this script (that uses gdal_proximity on the loaded raster and then the output of gdal_proximity is used in the raster calculator)</li>
</ul>
<pre>
param_proximity = {
'INPUT': QgsProject.instance().mapLayersByName('calculated')[0],
'BAND': 1,
'UNITS' : 0,
'OUTPUT': os.path.join(output, 'distance.tif')
}
proximity = processing.run("gdal:proximity", param_proximity)
param_calculated = {
'EXPRESSION':'{}@1 * {}'.format(proximity['OUTPUT'], formula),
'LAYERS': proximity['OUTPUT'],
'OUTPUT': os.path.join(output, 'calcolato.tif')
}
calculated = processing.run("qgis:rastercalculator", param_calculated)
iface.addRasterLayer(calculated['OUTPUT'], 'final')
</pre>
<p>This is working on Linux and on QGIS 3.4, 3.6 and master while is ALWAYS failing in Windows. To make it working on Windows some lines have to be added:</p>
<pre>
param_proximity = {
'INPUT': QgsProject.instance().mapLayersByName('calculated')[0],
'BAND': 1,
'UNITS' : 0,
'OUTPUT': os.path.join(output, 'distance.tif')
}
proximity = processing.run("gdal:proximity", param_proximity)
QgsProject.instance().addMapLayer(QgsRasterLayer(proximity['OUTPUT'], 'dummy'))
rl = QgsProject.instance().mapLayersByName('dummy')[0]
param_calculated = {
'EXPRESSION':'{}@1 * {}'.format(rl.name(), formula),
'LAYERS': rl.name(),
'OUTPUT': os.path.join(output, 'calcolato.tif')
}
calculated = processing.run("qgis:rastercalculator", param_calculated)
iface.addRasterLayer(calculated['OUTPUT'], 'final')
</pre>
<p>Fianlly, but still <b>extremely</b> important, with the same data the result is completely different. On Windows there are some super strange values (1.79769e+308 adn -1.79769e+308): some serious trouble with NODATA values?</p> QGIS Application - Bug report #21501 (Open): Distance matrix does not maintain data type and prec...https://issues.qgis.org/issues/215012019-03-06T15:20:18ZAndy Whyteandrew.g.whyte@gmail.com
<p>I have noticed that the distance matrix does not maintain precision or data type in InputID field created from the ID of the Input Point Layer to the tool.</p>
<p>This is an issue because it means I cannot join my result to an existing layer. The Target Point layer does not seem to do this.</p>
<p>For example the attached shapefile has an ID column (double, REAL, 20, P=0). When run through the distance matrix it inserts a decimal place. Additionally even if I use an integer ID field the output table will still not join to itself so it must be changing the type somehow to stop it from joining.</p>
<p>I am using QGIS 3.6</p> QGIS Application - Bug report #20760 (Open): Edits in GeoJson datasources are not saved anymorehttps://issues.qgis.org/issues/207602018-12-09T22:08:01ZEhsan Aliverdiehsan.aliverdi@gmail.com
<p>I tested this issue in Qgis 3.4.0, 3.4.1, 3.4.2 in all the same issue<br />in our company we work with Geojson files in Qgis. When editing the attributes of an existing feature in Geojson layer, QGIS creates a temp layer and applies the changes on that new temp layer and never applies the changes on original layer. <br />this problem wasn't there in version 3.2.3</p> QGIS Application - Bug report #20018 (Feedback): Server and desktop too slow with Postgis viewshttps://issues.qgis.org/issues/200182018-10-04T17:32:39ZJesus Rodriguez Marcialjesus.rodriguezmarcial@telefonica.com
<p>If a layer is defined with a view or with sql, qgis issues a select distinct count of the id, I guess that it does that to assert that the Id is unique. If I have a huge table, it takes some 60 seconds to execute (and naively enough, multiply it if several layers are based on the same exact view) It causes timeouts in qgis server, and makes the map unusable. There should be a way to tell Qgis that I'm pretty sure that the PK is valid. Adding insult to injury, I don't even want to edit the data.</p> QGIS Application - Bug report #19626 (Reopened): World map incorrectly drawn when using a differe...https://issues.qgis.org/issues/196262018-08-15T07:04:02Z克鲁 黄tone90999@hotmail.com
<p>When I use Natural Earth as data source and want to change projection for the project to customized Robinson, the map breaks apart (see attached file). <br />I use a projection as follows: <br />Proj4: +proj=robin +lon_0=150dE +x_0=0 +y_0=0 +datum=WGS84 +units=m +no_defs<br />Hope if it's not a bug. But if it is, I'd like to know if there's a workaround.</p> QGIS Application - Bug report #18295 (Open): PostGIS Data Loads Extemely Slowhttps://issues.qgis.org/issues/182952018-03-01T15:35:18ZMickey Dietrich
<p>I have added data from PostGIS in Version 2.18 and the one data set loads in about 2 seconds. With the new 3.0 version, it takes 2 minutes to load that same data layer. All my data sets load really slow in Version 3.0. Not sure what the difference is from 2.18 to 3.0, but it has really caused problems with using the newer version, since we utilize the PostGIS database for accessing most all of our data. Is there something I am missing to make it load faster like in 2.18 or is there something behind the scenes causing this problem? Thanks, Mickey</p>