QGIS2 - could not load "processing" plugin #203
Comments
|
Nobody? |
|
Hi @rkrug, thanks for reporting. Does this happen when launched from the QGIS.app bundle and not from the wrapper shell script? |
|
Hi @dakcarto, yes - the same error. I installed qgis2 new and deleted the Some more info: And here is the complete output from the commandline start: |
|
@rkrug, I've updated |
|
@dakcarto, Still the same error. |
|
@dakcarto, I'm having a near-identical error, for what it's worth. Starting from QGIS.app bundle on El Capitan. Have re-installed with no luck. Let me know if there's any additional info I can provide. |
|
We would like to use/support the |
|
Hmm. This might be an issue with incorrect parsing of an antiquated Try:
Please report if that works. Also, looks like this is fixed in: qgis/QGIS@4923e46 However, I think that fix masks the bad 'leftover' setting on macOS. If the workaround does work, then applying the fix and adding another should do the trick. |
|
Thanks
Should I then remove the plist? Any adverse effects? Concerning qgis/QGIS@4923e46 : I don't know if this has anything to do with the bug, but I have saga installed (via osgeo4mac). |
|
Does not work for me 😕 After moving However, on startup the error persist. I´m launching via the link in Quitting QGIS and overwriting with the backup from the desktop also does not fix it. I keep getting the |
|
So there seem to be different issues at work. |
|
@pat-s But this does not solve the regis issue. I just tried it - it persists. |
|
@rkrug wrote:
and, @pat-s wrote:
That was just a restore operation, so you didn't lose your settings. Return of any error is expected, and nothing is attempted to be fixed with that. Can you guys just test the change noted in qgis/QGIS@4923e46 ? Manually edit:
I would prefer not to patch the formulae, unless necessary (which seems like it is now). I'd also like to know that such patching will actually fix the issue. Thanks! Also note: |
|
@dakcarto Applying qgis/QGIS@4923e46 does not fix it for me |
|
I haven't done any special, as far as I am aware of. exports: do you refer to |
|
@pat-s @dakcarto But it also works if I start egis using
ore using the wrapper script suppled. For completion again the results from the first few lines of and |
|
@rkrug thanks! I did not do Rebuilding and checking. If this is the fix, these buildings options should be set as default. Let's see :) brew info qgis2
osgeo/osgeo4mac/qgis2: stable 2.18.3, HEAD [keg-only]
Open Source Geographic Information System
http://www.qgis.org
/usr/local/Cellar/qgis2/2.18.3 (8,781 files, 222.8M)
Built from source on 2017-02-01 at 10:23:41
From: https://github.com/osgeo/homebrew-osgeo4mac/blob/master/Formula/qgis2.rb
==> Dependencies
Build: cmake ✔, bison ✔, flex ✔
Required: qt-4 ✔, sip-qt4 ✔, pyqt-qt4 ✔, qca-qt4 ✔, qscintilla2-qt4 ✔, qwt-qt4 ✔, qwtpolar-qt4 ✔, qjson-qt4 ✔, gsl ✔, sqlite ✔, expat ✔, proj ✔, spatialindex ✔, fcgi ✔, gdal2 ✔, gdal2-python ✔, pyspatialite ✔
Recommended: postgresql ✔
Optional: gpsbabel-qt4 ✘, grass6 ✔, orfeo5 ✘, homebrew/science/r ✔, saga-gis ✔
==> Requirements
Required: unlinkedqgis2 ✔, python ✔
==> Options
--with-api-docs
Build the API documentation with Doxygen and Graphviz
--with-gdal-1
Build with GDAL/OGR v1.x instead of v2.x
--with-globe
Build with Globe plugin, based upon osgEarth
--with-gpsbabel-qt4
Build with gpsbabel-qt4 support
--with-grass
Build with GRASS 7 integration plugin and Processing plugin support (or install grass-7x first)
--with-grass6
Build extra GRASS 6 for Processing plugin
--with-isolation
Isolate .app's environment to HOMEBREW_PREFIX, to coexist with other QGIS installs
--with-oracle
Build extra Oracle geospatial database and raster support
--with-orfeo5
Build extra Orfeo Toolbox for Processing plugin
--with-qspatialite
Build QSpatialite Qt database driver
--with-r
Build extra R for Processing plugin
--with-saga-gis
Build extra Saga GIS for Processing plugin
--without-debug
Disable debug build, which outputs info to system.log or console
--without-postgresql
Build without current PostgreSQL client
--without-server
Build without QGIS Server (qgis_mapserv.fcgi)
--HEAD
Install HEAD version |
|
@rkrug @dakcarto Building with |
|
@rkrug @dakcarto I finally solved my problems. The error was:
Caused by some interferences between Now QGIS starts fine! 🐺 I will now do checks with building QGIS without |
|
@dakcarto @rkrug When building via both No difference in usage is detected if SAGA and GRASS are not set as options during building. Suggesting to add a note that multiple python interpreters can interfere with each other and cause problems for QGIS. I will now stick to brews python only from here on. |
|
@rkrug and @pat-s thanks for digging into this! Glad to see things are working. I'll look into adding some patches to the formula. @rkrug wrote:
This option ensures only Homebrew is used, excluding macOS system Python and bypassing any Kyngchaos install interaction. @pat-s wrote:
The optional Processing installs are purely optional, except GRASS7, which if added, or is found to already be installed, then the QGIS core C++ GRASS7 plugin is also built during QGIS compilation. If you install GRASS7 later, after QGIS, then the core GRASS7 plugin will not have been built (though Processing algorithms will still work).
This is not specific to QGIS or this tap, per se. Mixing Python interpreters is prone to cause issues with any part of Homebrew, though more so with applications that are built against Python core headers/libs, like QGIS. |
|
@pat-s Now that you have it running, we could dig into the |
|
@rkrug wrote:
Well, the default in Homebrew is not to be dependent upon its Python, so having isolation enabled would go against that. It also will not work for setups where a user has mixed Python C extensions, built by different Python installs of the same version (though they should be ABI compatible), or where the user has user-space Python overrides (which are not removed for isolation). Isolation cleans the PATH, making it specific to Homebrew, and cleans Python support by skipping PYTHON_PATH and ignoring system Python packages. Even though that is helpful, for some instances, I think it should not be default. |
|
@dakcarto OK - I accept your assessment. I am in no position to argue - I know way to little about Python for that and to understand the implications. |
|
Hi, I know nothing about python, so forgive my questions. I just did a clean install on a new mac (sierra), and upon completion, brew said that I should install a few missing python dependencies using pip. So I did that, but psycopg2, the library mentioned in this thread failed to install: cc -bundle -undefined dynamic_lookup -arch x86_64 -arch i386 -Wl,-F. build/temp.macosx-10.12-intel-2.7/psycopg/psycopgmodule.o build/temp.macosx-10.12-intel-2.7/psycopg/green.o build/temp.macosx-10.12-intel-2.7/psycopg/pqpath.o build/temp.macosx-10.12-intel-2.7/psycopg/utils.o build/temp.macosx-10.12-intel-2.7/psycopg/bytes_format.o build/temp.macosx-10.12-intel-2.7/psycopg/connection_int.o build/temp.macosx-10.12-intel-2.7/psycopg/connection_type.o build/temp.macosx-10.12-intel-2.7/psycopg/cursor_int.o build/temp.macosx-10.12-intel-2.7/psycopg/cursor_type.o build/temp.macosx-10.12-intel-2.7/psycopg/diagnostics_type.o build/temp.macosx-10.12-intel-2.7/psycopg/error_type.o build/temp.macosx-10.12-intel-2.7/psycopg/lobject_int.o build/temp.macosx-10.12-intel-2.7/psycopg/lobject_type.o build/temp.macosx-10.12-intel-2.7/psycopg/notify_type.o build/temp.macosx-10.12-intel-2.7/psycopg/xid_type.o build/temp.macosx-10.12-intel-2.7/psycopg/adapter_asis.o build/temp.macosx-10.12-intel-2.7/psycopg/adapter_binary.o build/temp.macosx-10.12-intel-2.7/psycopg/adapter_datetime.o build/temp.macosx-10.12-intel-2.7/psycopg/adapter_list.o build/temp.macosx-10.12-intel-2.7/psycopg/adapter_pboolean.o build/temp.macosx-10.12-intel-2.7/psycopg/adapter_pdecimal.o build/temp.macosx-10.12-intel-2.7/psycopg/adapter_pint.o build/temp.macosx-10.12-intel-2.7/psycopg/adapter_pfloat.o build/temp.macosx-10.12-intel-2.7/psycopg/adapter_qstring.o build/temp.macosx-10.12-intel-2.7/psycopg/microprotocols.o build/temp.macosx-10.12-intel-2.7/psycopg/microprotocols_proto.o build/temp.macosx-10.12-intel-2.7/psycopg/typecast.o -L/usr/local/lib -lpq -lssl -lcrypto -o build/lib.macosx-10.12-intel-2.7/psycopg2/_psycopg.so
ld: library not found for -lssl
clang: error: linker command failed with exit code 1 (use -v to see invocation)
error: command 'cc' failed with exit status 1
----------------------------------------
Command "/usr/bin/python -u -c "import setuptools, tokenize;__file__='/private/tmp/pip-build-EjOU9Y/psycopg2/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-Cb2tlu-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /private/tmp/pip-build-EjOU9Y/psycopg2/Seems like something like this was mentioned in the comments, but I'm not seeing how to get this properly installed |
|
If you search for the error on the web ( It is recommended to use the |
|
Ok, Does using python from brew involve anything else besides just As for the psycopg2 error, I have no idea why, but I came back to this a week later, and it just installed normally the way it did in another sierra mac. Weird. Anyways, happy to have a working QGIS app now! |
|
@dakcarto Thank you SO FUCKING MUCH. Applying qgis/QGIS@4923e46 worked flawlessly for me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I installed qgis2 on Sierrra, and I get the following error when starting:
The same happens if Y start from the wrapper script.
Any suggestions?
The text was updated successfully, but these errors were encountered: