QGis 2.14 misc warnings

[darkblueb]

shown by launching via X on the command line:

user@osgeolive:~$ qgis
Warning: loading of qgis translation failed [/usr/share/qgis/i18n//qgis_en_US]
Warning: loading of qt translation failed [/usr/share/qt4/translations/qt_en_US]
Warning: QCss::Parser - Failed to load file  "/style.qss" 
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
Warning: QFileSystemWatcher: failed to add paths: /home/user/.qgis2//project_templates
Warning 1: libXML: 0: Element 'SrcSql': This element is not expected.
en
/usr/share/qgis/python/plugins/SurveyingCalculation/i18n/en.qm

[Bas Couwenberg]

I've updated the summary because these are warnings, not errors.

This issue should be closed and the warnings ignored, or the issues should be forwarded upstream for them to fix.

[kalxas]

Ticket retargeted after milestone closed

[darkblueb]

bump 12dev; qgis 2.18 shows:

user@osgeolive:~$ qgis

(qgis.bin:2536): GLib-GIO-CRITICAL **: 14:28:47.731: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(qgis.bin:2536): GLib-GIO-CRITICAL **: 14:28:47.731: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(qgis.bin:2536): GLib-GIO-CRITICAL **: 14:28:47.731: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Warning: Object::connect: No such signal QgsMergedBookmarksTableModel::&QgsMergedBookmarksTableModel::selectItem( const QModelIndex &index )
Warning: Object::connect:  (receiver name: 'QgsBookmarksBase')
Warning: QCss::Parser - Failed to load file  "/style.qss" 
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
Warning: QFileSystemWatcher: failed to add paths: /home/user/.qgis2//project_templates
Warning: QLayout: Attempting to add QLayout "" to QgsPanelWidgetStack "mWidgetStack", which already has a layout
Warning 1: libXML: 0: Element 'SrcSql': This element is not expected.
C
/usr/share/qgis/python/plugins/SurveyingCalculation/i18n/C.qm

[darkblueb]

12dev beta2

behavior unchanged, upstream teams working on other things