QGIS Application: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2018-12-03T04:01:16ZQGIS Issue Tracking
Redmine Bug report #20695 (Closed): Crash when adding new feature with editing feature turned on qgis 3.4.2https://issues.qgis.org/issues/206952018-12-03T04:01:16ZSahit Tuntas Sadonosahitsadono@gmail.com
<a name="User-Feedback"></a>
<h2 >User Feedback<a href="#User-Feedback" class="wiki-anchor">¶</a></h2>
<p>Crash when adding new feature with editing feature turned on</p>
<a name="Report-Details"></a>
<h2 >Report Details<a href="#Report-Details" class="wiki-anchor">¶</a></h2>
<p><strong>Crash ID</strong>: e0f73e726c750b65e289fb1ab5d5574b149a1a67</p>
<p><strong>Stack Trace</strong><br /><pre>
QMimeType::staticMetaObject :
QgsMapCanvas::setMapTool :
QgisApp::activateDeactivateLayerRelatedActions :
QMetaObject::activate :
QgisApp::activeLayerChanged :
QgisApp::onActiveLayerChanged :
QMetaObject::activate :
QgsLayerTreeView::currentLayerChanged :
QgsLayerTreeView::onCurrentChanged :
QMetaObject::activate :
QItemSelectionModel::setCurrentIndex :
QAbstractItemView::setCurrentIndex :
QgisApp::autoSelectAddedLayer :
QgisApp::identifyMapTool :
QMetaObject::activate :
QgsLayerTreeRegistryBridge::addedLayersToLayerTree :
QgsLayerTreeRegistryBridge::layersAdded :
QMetaObject::activate :
QgsProject::legendLayersAdded :
QgsProject::addMapLayers :
QgisApp::addVectorLayer :
QgisApp::qt_static_metacall :
QMetaObject::activate :
QgsDataSourceManagerDialog::addVectorLayer :
QgsDataSourceManagerDialog::addProviderDialog :
QMetaObject::activate :
QgsAbstractDataSourceWidget::addVectorLayer :
wildcards :
QMetaObject::activate :
QAbstractButton::clicked :
QAbstractButton::click :
QAbstractButton::mouseReleaseEvent :
QWidget::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 :
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.2-Madeira<br />QGIS code revision: <a class="changeset" href="https://issues.qgis.org/projects/qgis/repository/revisions/22034aa0704dde196fa18f9f7baa901834499b37" title="fix link error on windows">22034aa070</a><br />Compiled against Qt: 5.11.2<br />Running against Qt: 5.11.2<br />Compiled against GDAL: 2.3.2<br />Running against GDAL: 2.3.2</p>
<p><strong>System Info</strong><br />CPU Type: x86_64<br />Kernel Type: winnt<br />Kernel Version: 10.0.17134</p> Bug report #19951 (Closed): Edit mode doesn't work when ogr vector layers have filtershttps://issues.qgis.org/issues/199512018-09-26T08:13:27ZLoïc BARTOLETTI
<p>When you add a filter to a layer<sup><a href="#fn1">1</a></sup>, the editing mode is disabled</p>
<p>[1] Confirmed on a geopackage but not with postgis</p>
<p>Ref <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/16027" title="Editing GeoPackage from DWG/DXF Import after Save as Layer Definition File (Closed)">#16027</a></p> Bug report #18543 (Closed): 'Select features by value' QGIS crasheshttps://issues.qgis.org/issues/185432018-03-26T12:36:47ZEnrico Fioreenricofiore@libero.it
<p>If you active "Select features by value" tool to perform a research in a layer and then you try to edit the same layer, QGIS crashes.</p> Bug report #18061 (Closed): Package qgis-plugin-grass on ubuntu repositorieshttps://issues.qgis.org/issues/180612018-02-08T12:24:52ZRoberto Marzocchiroberto.marzocchi@gter.it
<p>It is now available GRASS 7.4 and people can update the grass package but the package qgis-plugin-grass depends on grass722 which is not available</p> Bug report #15385 (Closed): "Recent Projects" problemshttps://issues.qgis.org/issues/153852016-08-03T03:16:38ZDan Jacobsonjidanni@jidanni.org
<p>User upon starting, sees "Recent Projects" with no way to right click to<br />delete one.</p>
<p>All he can do is double click, opening it. With no way to close it,<br />other than quitting Qgis entirely.</p>
<p>And still no way to delete it via the menus.</p>
<p>Starting up again, he single click a Recent Project, highlighting it, but then in<br />Project->Properties we only learn about a project without a file. Why<br />isn't this greyed out if we are not supposed to chose it?</p> Bug report #14694 (Closed): DB Manager: F5 not workinghttps://issues.qgis.org/issues/146942016-04-15T20:19:54ZPaolo Cavallinicavallini@faunalia.it
<p>n the DB Manager SQL window, pressing Execute correctly run the query,<br />whereas F5 does not.</p> Bug report #14428 (Closed): Join Attribute table in processing Toolbox fails!https://issues.qgis.org/issues/144282016-03-04T09:30:03ZClaas Leinerclaas.leiner@gkg-kassel.de
<p>Join Attribute table in processing Toolbox fails in QGIS 2.14 / Ubuntu 14.04</p>
<p>error message:<br /> File "/usr/share/qgis/python/plugins/processing/algs/qgis/JoinAttributes.py", line 82, in processAlgorithm<br /> for current, feat in features:<br /> ValueError: too many values to unpack<br />too many values to unpack See log for more details.</p> Bug report #14258 (Closed): Line width size assistant fails to load values when column is name "...https://issues.qgis.org/issues/142582016-02-09T04:26:59ZPaolo Cavallinicavallini@faunalia.it
<p>The assistant fails to load values of a variable (length, real) from a particular layer.<br />Other variables (integers, strings) are loaded.</p> Feature request #11107 (Closed): Multiple Selection: Two areas for improvement. https://issues.qgis.org/issues/111072014-08-27T04:49:23ZMarc-André Saia
<p>Hi,<br />1: In almost all the software out there, the "Shift" key is associated with multiple selection. In Qgis, it is also the case in the PrintComposer and in the browser. Why then should I use the "Ctrl" key? Result: When working with multiple software, is often chosen the wrong key. What can be frustrating not only in Qgis, but also in other software, because of the "bad habit" of the "Ctrl" key. Why not offer the choice of two settings: The Qgis mode with the "Ctrl" key and normalized with the "Shift" key mode?</p>
<p>2: Currently, when you want to add items to a previous selection, the select tool deselects items already selected in selection. It would be more convenient, with all modes of selection, except for the selection mode for single element, that additions to a selection does not deselect the pre-selected items. Again, why not offer to the user the mode Qgis original selection mode and normalized selection mode like in almost all software?</p> Feature request #11022 (Closed): Difficult to modify nodes of contiguous polygons https://issues.qgis.org/issues/110222014-08-07T22:05:45ZAlain FERRATON
<p>in edit mode<br />node considered is not always that of the selected polygon</p>
<p>see the attachment</p>
<p>see also : <a class="issue tracker-1 status-5 priority-4 priority- closed" href="https://issues.qgis.org/issues/10234" title="Difficult to edit nodes of polygons close together (Closed)">#10234</a></p> Bug report #8380 (Closed): Opening D&D form crashes QGIShttps://issues.qgis.org/issues/83802013-07-29T07:12:48ZPaolo Cavallinicavallini@faunalia.it
<ul>
<li>open a large PostGIS layer (30k polygons)</li>
<li>create a simple Drag&Drop form</li>
<li>open the Info tool</li>
<li>click on a geom</li>
<li>click on Actions>Geometry view form</li>
<li>crash with:</li>
</ul>
<pre>
Exception executing sql: must be member of role "postgres"
Warning: Cannot open file '/images/themes/default/mActionDeleteSelected.svg', because: No such file or directory
Warning: Cannot open file '/images/themes/default/mActionDeleteSelected.svg', because: No such file or directory
Warning: Cannot open file '/images/themes/default/mActionZoomToSelected.svg', because: No such file or directory
Warning: Cannot open file '/images/themes/default/mActionZoomToSelected.svg', because: No such file or directory
Warning: QLayout: Cannot add null widget to QVBoxLayout/mAttributeEditorLayout
Warning: QFont::setPointSize: Point size <= 0 (0), must be greater than 0
Warning: QFont::setPointSize: Point size <= 0 (0), must be greater than 0
WARNING: there is no transaction in progress
Exception executing sql: syntax error at or near "$1"
RIGA 1: INSERT INTO iso_metadata(md_scope, $1 , fileid, parentid, g...
^
QUERY: INSERT INTO iso_metadata(md_scope, $1 , fileid, parentid, geometry) VALUES('undefined', XMLPARSE(DOCUMENT $1 ), $2 , $3 , $4 )
CONTESTO: SQL statement in PL/PgSQL function "registerisometadata" near line 31
Exception executing sql: must be member of role "postgres"
Exception executing sql: syntax error at or near "$1"
RIGA 1: INSERT INTO iso_metadata(md_scope, $1 , fileid, parentid, g...
^
QUERY: INSERT INTO iso_metadata(md_scope, $1 , fileid, parentid, geometry) VALUES('undefined', XMLPARSE(DOCUMENT $1 ), $2 , $3 , $4 )
CONTESTO: SQL statement in PL/PgSQL function "registerisometadata" near line 31
Warning: QFont::setPointSize: Point size <= 0 (0), must be greater than 0
Warning: QFont::setPointSize: Point size <= 0 (0), must be greater than 0
Warning: QFont::setPointSize: Point size <= 0 (0), must be greater than 0
Warning: QFont::setPointSize: Point size <= 0 (0), must be greater than 0
Exception executing sql: must be member of role "postgres"
Exception executing sql: must be member of role "postgres"
Debug: "layerid = intersezione20130729160050518"
Warning: QFont::setPointSize: Point size <= 0 (0), must be greater than 0
Warning: QFont::setPointSize: Point size <= 0 (0), must be greater than 0
Fatal: QGIS died on signal 11
Stacktrace (piped through c++filt):
Annullato
paolo@felis:~$ /usr/bin/qgis.bin(dumpBacktrace()+0x66)[0x4eb6d6]
/usr/bin/qgis.bin(myMessageOutput(QtMsgType, char const*)+0x42)[0x4eb792]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(qt_message_output(QtMsgType, char const*)+0x21)[0x7fb07b3c7831]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x70c79)[0x7fb07b3c7c79]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(qFatal(char const*, ...)+0x94)[0x7fb07b3c8484]
/lib/x86_64-linux-gnu/libc.so.6(+0x35260)[0x7fb0783f0260]
/usr/lib/libqgis_gui.so.1.9.0(QgsAttributeEditor::createWidgetFromDef(QgsAttributeEditorElement const*, QWidget*, QgsVectorLayer*, QVector<QVariant>&, QMap<int, QWidget*>&, bool)+0xe2)[0x7fb07c0cebc2]
/usr/lib/libqgis_gui.so.1.9.0(QgsAttributeEditor::createWidgetFromDef(QgsAttributeEditorElement const*, QWidget*, QgsVectorLayer*, QVector<QVariant>&, QMap<int, QWidget*>&, bool)+0x346)[0x7fb07c0cee26]
/usr/lib/libqgis_gui.so.1.9.0(QgsAttributeDialog::QgsAttributeDialog(QgsVectorLayer*, QgsFeature*, bool, QgsDistanceArea, QWidget*, bool)+0x3b95)[0x7fb07c0d3f25]
/usr/bin/qgis.bin(QgsFeatureAction::newDialog(bool)+0x178)[0x5c58f8]
/usr/bin/qgis.bin(QgsFeatureAction::viewFeatureForm(QgsHighlight*)+0x1c)[0x5c5c9c]
/usr/bin/qgis.bin(QgsIdentifyResultsDialog::featureForm()+0x1b2)[0x5bdc52]
/usr/bin/qgis.bin(QgsIdentifyResultsDialog::itemClicked(QTreeWidgetItem*, int)+0x1b5)[0x5c25c5]
/usr/bin/qgis.bin[0x7b5e9a]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(QMetaObject::activate(QObject*, QMetaObject const*, int, void**)+0x2d8)[0x7fb07b4e5cf8]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(QTreeWidget::itemClicked(QTreeWidgetItem*, int)+0x40)[0x7fb07adda8f0]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(QMetaObject::activate(QObject*, QMetaObject const*, int, void**)+0x2d8)[0x7fb07b4e5cf8]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(QAbstractItemView::clicked(QModelIndex const&)+0x25)[0x7fb07ad685f5]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(QAbstractItemView::mouseReleaseEvent(QMouseEvent*)+0x148)[0x7fb07ad687a8]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(QWidget::event(QEvent*)+0xace)[0x7fb07a8c4d0e]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(QFrame::event(QEvent*)+0x1e)[0x7fb07ac6295e]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(QAbstractItemView::viewportEvent(QEvent*)+0x1d3)[0x7fb07ad719e3]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(QTreeView::viewportEvent(QEvent*)+0x30)[0x7fb07adb08d0]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*)+0x86)[0x7fb07b4d1cc6]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(QApplicationPrivate::notify_helper(QObject*, QEvent*)+0x6c)[0x7fb07a8756ec]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(QApplication::notify(QObject*, QEvent*)+0x3ad)[0x7fb07a87bebd]
/usr/lib/libqgis_core.so.1.9.0(QgsApplication::notify(QObject*, QEvent*)+0x5b)[0x7fb07c658aab]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(QCoreApplication::notifyInternal(QObject*, QEvent*)+0x6d)[0x7fb07b4d1b5d]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool)+0x153)[0x7fb07a87b673]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x2403cb)[0x7fb07a8ed3cb]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(QApplication::x11ProcessEvent(_XEvent*)+0x5fc)[0x7fb07a8ebe3c]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x266792)[0x7fb07a913792]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x146)[0x7fb076cefea6]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x481f8)[0x7fb076cf01f8]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fb076cf029c]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x65)[0x7fb07b4fece5]
/usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x266846)[0x7fb07a913846]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x2f)[0x7fb07b4d07bf]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)+0x175)[0x7fb07b4d0ab5]
/usr/lib/x86_64-linux-gnu/libQtCore.so.4(QCoreApplication::exec()+0x8b)[0x7fb07b4d60fb]
/usr/bin/qgis.bin(main+0x2215)[0x4e73f5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fb0783dc995]
/usr/bin/qgis.bin[0x4eb208]
</pre> Bug report #8237 (Closed): Georeferencer:Japanese file name problemhttps://issues.qgis.org/issues/82372013-07-08T03:55:40ZKOSUKE ASAHIasahi@hcc.co.jp
<p>Could I report GDAL georeferencer problem here?</p>
<p>Error occurs, when we use Japanese file name to output file name.<br />There are two kind behavior.<br />- file name characters were garbled when we use Japanese characters file name<br />- don't get any output when file path include Japanese characters</p>
<p>Tested QGIS d37e03b from OSGeo4W.</p> Bug report #8186 (Closed): Fail to make spatial index for shapefile, with Japanese string in the...https://issues.qgis.org/issues/81862013-06-27T21:49:24Zyoichi Kayamayoichi.kayama@gmail.com
<p>after load shapefile that filename contain Japanese string, when make spatial index at the property dialog, fail.<br />In directory name with some Japanese character, but all file name are ascii, make spatial index was success.<br />Only fail file name with some Japanese character ,to make spatial index.</p>
<p>Here is log messeage</p>
<p>OGR<sup><a href="#fn3">3</a></sup>error 1 Layer ‹Œ’¬‘º not recognised.</p> Feature request #6632 (Closed): Implement QgsPostgresProvider::addFeatures for TopoGeometry layershttps://issues.qgis.org/issues/66322012-11-05T14:56:59ZSandro Santillistrk@kbt.io
<p>editing is implemented, but we also want to add new items.</p> Bug report #6097 (Closed): Getting wrong attribute values from a feature in qgishttps://issues.qgis.org/issues/60972012-07-25T07:56:57ZStig Henning Fredheimstighenning@hotmail.com
<p>This scenario shows the bug:<br />I make two polylines features(in my example both consists of two points) with the add feature tool. Then I (with code) add some attribute values on the first feature, then changes the geometry of the second feature before I add values to the second values.</p>
<p>When I use layer.featureAtId() to get the second feature and then reads it, I get the values from the first feature.<br />But when using feat.geometry().asPolyline(), I get the correct geometry</p>
<p>I don't get this problem if I don't change the geometry or if I commit the two new polylines before doing the mentioned operations.</p>
<p>In the attribute table it is correct. If I use layer.nextFeature(feat) to iterate through all the features I get the right value.</p>
<p>There is a python script attached to show the bug. This code demands a little manual interaction to work. The comments says where the interaction is needed.</p>