Processing: Get scripts /models from online collection crashes QGIS #24224
Labels
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Crash/Data Corruption
High Priority
Processing
Relating to QGIS Processing framework or individual Processing algorithms
Author Name: Andreas Plesch (@andreasplesch)
Original Redmine Issue: 16314
Affected QGIS version: 2.18.3
Redmine category:processing/core
Assignee: Victor Olaya
Opening (double clicking) Get script (or models) from on-line collection in the Processing tool box crashes QGIS.
Here is the console output before the segmentation fault:
@warning: Object::connect: No such signal QWebPage::loadProgress(int)
Warning: Object::connect: No such signal QWebPage::unsupportedContent(QNetworkReply*)
Warning: Object::connect: No such signal QWebFrame::titleChanged(QString)
Warning: Object::connect: No such signal QWebPage::loadProgress(int)
Warning: Object::connect: No such signal QWebFrame::titleChanged(QString)
Warning: Object::connect: No such signal QWebFrame::iconChanged()
Warning: Object::connect: No such signal QWebFrame::urlChanged(QUrl)
Warning: Object::connect: No such signal QWebPage::loadStarted()
Warning: Object::connect: No such signal QWebPage::loadProgress(int)
Warning: Object::connect: No such signal QWebPage::statusBarMessage(QString)
Warning: Object::connect: No such signal QWebPage::linkClicked(QUrl)
Warning: Object::connect: No such signal QWebPage::selectionChanged()
Warning: Object::connect: No such signal QWebPage::microFocusChanged()
Warning: QMetaObject::invokeMethod: No such method QWebPage::repaintRequested(QRect)
Warning: QMetaObject::invokeMethod: No such method QWebPage::repaintRequested(QRect)
Warning: QMetaObject::invokeMethod: No such method QWebPage::repaintRequested(QRect)
Warning: QMetaObject::invokeMethod: No such method QWebPage::repaintRequested(QRect)
Warning: QMetaObject::invokeMethod: No such method QWebPage::repaintRequested(QRect)
Warning: QMetaObject::invokeMethod: No such method QWebPage::repaintRequested(QRect)
Segmentation fault
@
The text was updated successfully, but these errors were encountered: