Re: [QGIS-Developer] Error in Windows nightlies

[Saber Razmjooei]

Eiv2 does not appear to be picked up automatically by the installer as the
mandatory lib. I had to select it manually and all working fine for me.

Cheers
Saber

On Fri, 16 Nov 2018 at 05:58, Nyall Dawson  wrote:

> Hi all/Jürgen,
>
> Since the introduction of the exiv2 dependency last week I'm having
> trouble loading the nightly Windows releases via osgeo4w. On startup I
> just get the error:
>
> Could not load qgis_app.dll.
> The specified module could not be found.
>
> (This is despite the qgis_app.dll file being present and correctly in the
> path).
>
> Is this a known issue?
>
> Nyall
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Saber Razmjooei
www.lutraconsulting.co.uk
+44 (0)7568 129733
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Error in Windows nightlies

[Nyall Dawson]

Hi all/Jürgen,

Since the introduction of the exiv2 dependency last week I'm having
trouble loading the nightly Windows releases via osgeo4w. On startup I
just get the error:

Could not load qgis_app.dll.
The specified module could not be found.

(This is despite the qgis_app.dll file being present and correctly in the path).

Is this a known issue?

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] How to get my styling widget back into screen space

[Nyall Dawson]

On Wed, 14 Nov 2018 at 22:57, Casper Børgesen  wrote:
>
> I have a laptop with two monitors attached. When undocking my laptop, moving 
> to a meeting room with a single projector, presenting something involving 
> QGIS, moving back to my monitors and docking my laptop, Windows 10 resizes my 
> applications and some of them are even returned to the primary monitor. This 
> also happens for QGIS but my undocked styling panel doesn’t – its floating 
> somewhere where I cannot see it.
>
>
>
> Is it possible somehow to move/return the styling panel (or any other 
> undocked panel) to visible screen space where I can fetch it?

Settings -> Options -> System > "Reset user interface to default settings"

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS composer export - issue with projection, scale & scalebar ?

[Nyall Dawson]

On Thu, 15 Nov 2018 at 03:41, kimaidou  wrote:
>
> Hi all,
>
> Sorry for my previous message, which (I just realize) can appear rude if you 
> have not received the first one.

I think it was worded ok and didn't come across rude (to me at least).

>>> I have created 2 very simple QGIS projects (attached with data)
>>>
>>> * 1 vector polygon grid 1km X 1km (GeoJSON), created with the Vector 
>>> processing tool.
>>> * 1 OpenStreetMap TMS background layer (EPSG:3857)
>>> * 1 A4 composer with a map taking full size, and a scale bar
>>> * 1 project in EPSG:3857 & its brother in EPSG:2154 (French proj)
>>>
>>> Issues noted:
>>>
>>> * In the composer, the scale bar does not fit with the 1km grid, in both 
>>> projects.
>>> * After defining the same scale (1:10 000) in the composers, the view are 
>>> really different in the 2 projects (see attached PDF)
>>>
>>> I know projections are biased representations of the reality, but as a user 
>>> perspective, this 2 behaviours really seem like issues. Every time a user 
>>> prints a map and take the A4 paper, he is condident he will be able to use 
>>> his ruler to measure things and convert to real distances according to the 
>>> scale. Or report N times the scale bar segments to get distances.
>>>
>>> I am like someone who just discovers the Earth is not flat...
>>>
>>> NB: I have tested this behaviour only in 2.18.

It's the same in 3.x.

My 2c: I don't actually believe there's an issue here. QGIS scale bars
*ALWAYS* use ellipsoidal distances, regardless of the projection (and
have for longer than I've been involved in the project, so since some
version earlier than 1.7).
This means you'll see differences between a 1km size grid created in a
some local projection vs the scale bar's size, because the grid size
is a cartesian size measurement based on a projected CRS, vs distances
measured on the ellipsoid. The differences will be more extreme for
CRSes which are bad for distance/area preservation, especially 3857.

I think the solution here is really just education -- we need to make
sure users know that 3857 is unsuitable for anything but web maps, and
that it's THEIR responsibility to make an informed decision what the
correct CRS is for their project.**

Nyall

** in reality, we'll never win this battle, and there'll always be
uninformed, untrained users pushing out junk results out based on 3857
calculations.
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Import in PostGIS from Processing

[Nyall Dawson]

On Thu, 15 Nov 2018 at 04:48, Paolo Cavallini  wrote:
>
> Oh, I see, you're right. Not sure it's the right semantic though, I'll have 
> to check similar commands.
> Thanks.

IIRC this was a conscious change, because we're not "importing" from
QGIS into postgres, we're exporting some layer FROM qgis INTO
postgres. Importing would be correct only if the operation was being
triggered from the postgres side (e.g. pgadmin importing qgis data).

Nyall



>
> Il 14 novembre 2018 19:38:53 CET, Raymond Nijssen  ha 
> scritto:
>>
>> Hi Paolo,
>>
>> Not sure, but is this what you mean?
>>
>>
>> algorithm name:
>>
>> 'Export to PostgreSQL'
>>
>> description:
>>
>> Export to PostgreSQL
>> This algorithm imports a vector layer into a PostGIS database, creating
>> a new table.
>> Prior to this a connection between QGIS and the PostGIS database has to
>> be created (for example with the DB Manager).
>>
>> in the dialog:
>> "layer to import"
>>
>>
>> It looks a bit confusing, though it depends on the view point wetter it
>> is an import or an export.
>>
>> Regards,
>> Raymond
>>
>>
>>
>> On 14-11-18 19:13, Paolo Cavallini wrote:
>>>
>>> Hi all,
>>>
>>> the Import alg in Processing is called Export in 3.4, whereas it is
>>> correct in 3.2 and earlier. Could someone confirm?
>>>
>>> Thanks.
>>>
>> 
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> --
> Sorry for being short
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS Processing "R" Provider -- 3.x beta available

[Alex Mandel]

Nyall,

I can confirm the plugin loads without error on QGIS 3.4.1, Ubuntu 16.04
I'll need to find an R script or two to test with.

Thanks this is very appreciated,
Alex

On 11/15/18 14:34, Nyall Dawson wrote:
> Hi lists,
> 
> Just a quick announcement that the Processing provider for R scripts
> in QGIS, which was dropped for QGIS 3.0, is now available as a beta
> for QGIS 3.4. It's now published as a standalone plugin which must be
> manually installed (together with manual installation of the
> underlying R software!).
> 
> This is a pre-release beta version only -- the script syntax may
> change in the final release, so be warned that you may need to update
> scripts as a result. But the good news is that this should be 100%
> compatible with Processing R scripts from 2.x, with no change required
> to the scripts!
> 
> To reflect its beta status, the plugin is currently only available via
> manual download from GitHub, and isn't (yet) available via the
> standard QGIS plugin repository. To install, download the zip release
> from https://github.com/north-road/qgis-processing-r/releases/tag/v0.0.2,
> and then install via the Plugins -> Manage and Install Plugins >
> Install from ZIP tab. After the plugin is installed you'll need to
> enable the provider via the Settings > Options > Processing >
> Providers > R > Activate checkbox.
> 
> Testing feedback is sought and very welcome -- just file issues on
> https://github.com/north-road/qgis-processing-r/issues with a detailed
> description of any issues you encounter.
> 
> This release was made possible thanks to a funding grant by QGIS.org.
> 
> Regards,
> Nyall
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> 

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] QGIS Processing "R" Provider -- 3.x beta available

[Nyall Dawson]

Hi lists,

Just a quick announcement that the Processing provider for R scripts
in QGIS, which was dropped for QGIS 3.0, is now available as a beta
for QGIS 3.4. It's now published as a standalone plugin which must be
manually installed (together with manual installation of the
underlying R software!).

This is a pre-release beta version only -- the script syntax may
change in the final release, so be warned that you may need to update
scripts as a result. But the good news is that this should be 100%
compatible with Processing R scripts from 2.x, with no change required
to the scripts!

To reflect its beta status, the plugin is currently only available via
manual download from GitHub, and isn't (yet) available via the
standard QGIS plugin repository. To install, download the zip release
from https://github.com/north-road/qgis-processing-r/releases/tag/v0.0.2,
and then install via the Plugins -> Manage and Install Plugins >
Install from ZIP tab. After the plugin is installed you'll need to
enable the provider via the Settings > Options > Processing >
Providers > R > Activate checkbox.

Testing feedback is sought and very welcome -- just file issues on
https://github.com/north-road/qgis-processing-r/issues with a detailed
description of any issues you encounter.

This release was made possible thanks to a funding grant by QGIS.org.

Regards,
Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Limitations of the search locator "af" option?

[Matthias Kuhn]

Hi Harrissou,

It's the "display name" configured in layer properties -> display.
What's shown in the form view of the attribute table.

This way it's highly configurable, what's actually searched for in all
the layers. Especially with numbers it would often be impossible to find
something useful without somehow limiting the attributes which are being
searched.

Regards

Matthias

On 11/15/18 6:03 PM, DelazJ wrote:
> Hi devs,
>
> I was about to write an issue report but given that I get a kind of
> consistent result, I wonder if it's by design or a bug. so better ask
> here before.
>
> I'm exploring the locator feature that searches in all layers , aka
> "af" and because it almost never returns something usable to me (I
> often search text), i tried to understand its logic and arrived to the
> following: It does not search in ALL fields of all layers; it searches
> ONLY in the field set as preview field for each layer.
>
> What is a preview field? It's that field in the Display tab of the
> layer properties that you choose to show map tips.
> By default, map tips option use the first field of the layer; actually
> looks like it uses the first field if it's a numeric field (maybe
> integer?). Having a string field as first in the layer does not
> populate the map tip option: you get a [Please define preview text],
> also shown in the locator bar. A bug I should report?
>
> The limitation about the "af" feature not using all fields, if ever
> that's true, is mentioned nowhere. Should be, given that the "active
> layer" option does browse all the fields and people would expect the
> same. And the relation between map tip fields and the locator should
> be more clearly visible. I don't know where but...
>
> I could open issue reports for these but would like to know if I'm not
> missing something.
>
> Regards,
> Harrissou
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
-- 
Matthias Kuhn
matth...@opengis.ch 
+41 (0)76 435 67 63 
OPENGIS.ch Logo 
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Limitations of the search locator "af" option?

[DelazJ]

Hi devs,

I was about to write an issue report but given that I get a kind of
consistent result, I wonder if it's by design or a bug. so better ask here
before.

I'm exploring the locator feature that searches in all layers , aka "af"
and because it almost never returns something usable to me (I often search
text), i tried to understand its logic and arrived to the following: It
does not search in ALL fields of all layers; it searches ONLY in the field
set as preview field for each layer.

What is a preview field? It's that field in the Display tab of the layer
properties that you choose to show map tips.
By default, map tips option use the first field of the layer; actually
looks like it uses the first field if it's a numeric field (maybe
integer?). Having a string field as first in the layer does not populate
the map tip option: you get a [Please define preview text], also shown in
the locator bar. A bug I should report?

The limitation about the "af" feature not using all fields, if ever that's
true, is mentioned nowhere. Should be, given that the "active layer" option
does browse all the fields and people would expect the same. And the
relation between map tip fields and the locator should be more clearly
visible. I don't know where but...

I could open issue reports for these but would like to know if I'm not
missing something.

Regards,
Harrissou
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [481] go2streetview approval notification.

[noreply]

Plugin go2streetview approval by pcav.
The plugin version "[481] go2streetview 7.6" is now approved
Link: http://plugins.qgis.org/plugins/go2streetview/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS 3.4 Plugin Python : error during import of PCRaster

[Michel Stuyts]

Have you tried installing it from the OSGeo shell instead of from the Windows 
default shell (cmd.exe)?


Michel



Van: QGIS-Developer [mailto:qgis-developer-boun...@lists.osgeo.org] Namens 
Christine
Verzonden: donderdag 15 november 2018 16:44
Aan: qgis-developer@lists.osgeo.org
Onderwerp: [QGIS-Developer] QGIS 3.4 Plugin Python : error during import of 
PCRaster


Hello all,


I am developping a plugin for QGIS 3.4. In my module irip_dockwidget.py when I 
try to import PCRaster 4.2. I get this error :

File 
"C:/Users/a/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\irip\irip_dockwidget.py",
 line 26, in import pcraster as pcr
File "C:/PROGRA~1/QGIS3~1.4/apps/qgis/./python\qgis\utils.py", line 672, in 
_import  mod = _builtin_import(name, globals, locals, fromlist, level)
File "C:\Program Files\pcraster-4.2.0\python\pcraster\__init__.py", line 62, in 
 raise ImportError(msg)
ImportError: The 'Microsoft Visual C++ 2015 Redistributable Update 3' is 
required to run PCRaster, available at:
 https://www.microsoft.com/en-us/download/details.aspx?id=53840
DLL load failed: Le module spécifié est introuvable.In case you cannot solve 
the issue please consult the PCRaster mailing list at: 
https://lists.geo.uu.nl/mailman/listinfo/pcraster-info

I’ve installed the MSCP as recommended in the message but the problem still 
remains. I’ve mailed to PCRaster team and wait for a reply but maybe have you  
already seen this problem and you have a solution.
Another point : I developed a command-line version of my application which 
works well.
My envir : Windows 8, QGIS 3.4 (QGIS-OSGeo4W-3.4.1-1-Setup-x86_64.exe), Python 
3.6, PCRaster 4.2
Thanks for your help,
Christine


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] QGIS 3.4 Plugin Python : error during import of PCRaster

[Christine]

Hello all,

 



I am developping a plugin for QGIS 3.4. In my module irip_dockwidget.py when I 
try to import PCRaster 4.2. I get this error :

 

File 
"C:/Users/a/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\irip\irip_dockwidget.py",
 line 26, in import pcraster as pcr

File "C:/PROGRA~1/QGIS3~1.4/apps/qgis/./python\qgis\utils.py", line 672, in 
_import  mod = _builtin_import(name, globals, locals, fromlist, level)
File "C:\Program Files\pcraster-4.2.0\python\pcraster\__init__.py", line 62, in 
 raise ImportError(msg)
ImportError: The 'Microsoft Visual C++ 2015 Redistributable Update 3' is 
required to run PCRaster, available at:
             https://www.microsoft.com/en-us/download/details.aspx?id=53840
DLL load failed: Le module spécifié est introuvable.In case you cannot solve 
the issue please consult the PCRaster mailing list at: 
https://lists.geo.uu.nl/mailman/listinfo/pcraster-info

 

I’ve installed the MSCP as recommended in the message but the problem still 
remains. I’ve mailed to PCRaster team and wait for a reply but maybe have you  
already seen this problem and you have a solution. 

Another point : I developed a command-line version of my application which 
works well.

My envir : Windows 8, QGIS 3.4 (QGIS-OSGeo4W-3.4.1-1-Setup-x86_64.exe), Python 
3.6, PCRaster 4.2

Thanks for your help,

Christine

 
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1002] VetEpiGIStool approval notification.

[noreply]

Plugin VetEpiGIStool approval by pcav.
The plugin version "[1002] VetEpiGIStool 0.800 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/VetEpiGIS-Tool/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [292] ZoomRC approval notification.

[noreply]

Plugin ZoomRC approval by pcav.
The plugin version "[292] ZoomRC 0.4.1" is now approved
Link: http://plugins.qgis.org/plugins/zoomrc/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1570] SPUGeo Memorial approval notification.

[noreply]

Plugin SPUGeo Memorial approval by pcav.
The plugin version "[1570] SPUGeo Memorial 0.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/spugeomemorial/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Cannot load QGIS source code in QTCreator

[Andrea Aime]

Thanks everybody for the followup! I'm answering this mail but I'll
integrate comments about the others too.

On Thu, Nov 15, 2018 at 8:26 AM Alessandro Pasotti 
wrote:

> Hi Andrea,
>
> I've never seen that particular error, I'd look into cmake installation
> and/or version.
>

See below


> The vast majority of QGIS C++ developers uses Qt Creator on a daily basis
> on different platforms, what work for me here is:
>
> Ubuntu xenial
>
> QtCreator: 4.7.2 installed from https://www.qt.io/download
> cmake version 3.10.2 self-built from sources
> Qt 10.0.1 self-built from sources
>
> Notice that none of the above was installed with apt, the main reason is
> that xenial is a little bit old, but IIRC that was also to avoid some
> problems in the integration of the different components.
>

I see... on my machine I have everything installed from apt instead,
versions are:

   - QT Creator 4.5.2
   - cmake 3.10.2
   - QT is 5.9.5 (you have QT 10 instead??)

 In other comments I've been invited to build from sources using cmake,
which I did, worked, but then trying to start qgis as built results in this:

aaime@colossus ~/devel/qgis/build-master (master) $ export
LD_LIBRARY_PATH=/home/aaime/apps/lib
aaime@colossus ~/devel/qgis/build-master (master) $
/home/aaime/apps/bin/qgis
src/app/main.cpp: 469: (main) [0ms] Starting qgis main
src/core/qgsmessagelog.cpp: 29: (logMessage) [0ms] 2018-11-15T10:04:25
QGIS[1] Successfully loaded globalsettingsfile path:
/home/aaime/apps/share/qgis/resources/qgis_global_settings.ini
src/core/qgsapplication.cpp: 158: (QgsApplication) [50ms] loading of qt
translation failed /usr/share/qt5/translations/qt_it_IT
src/app/qgsversionmigration.cpp: 92: (requiresMigration) [1ms] File version
is=2
src/app/qgscustomization.cpp: 945: (loadDefault) [4ms] Status path =
/Customization/status
src/app/qgscustomization.cpp: 946: (loadDefault) [0ms] status = 0
src/app/qgscustomization.cpp: 954: (loadDefault) [0ms] Default
customization not found in
/home/aaime/apps/share/qgis/resources/customization.ini
src/core/qgsfontutils.cpp: 277: (loadStandardTestFonts) [13ms] Test font
'QGIS Vera Sans' (Bold) loaded from testdata.qrc
src/core/qgsfontutils.cpp: 277: (loadStandardTestFonts) [7ms] Test font
'QGIS Vera Sans' (Roman) loaded from testdata.qrc
src/core/qgsapplication.cpp: 1706: (setMaxThreads) [71ms] maxThreads: -1
src/core/qgsapplication.cpp: 1722: (setMaxThreads) [0ms] set QThreadPool
max thread count to 16
src/core/qgsruntimeprofiler.cpp: 54: (end) [1ms] PROFILE: User profile
manager - 0
src/core/qgsruntimeprofiler.cpp: 54: (end) [46ms] PROFILE:
qgisapp/startup/Setting up UI - 0.046
src/core/qgsruntimeprofiler.cpp: 54: (end) [22ms] PROFILE:
qgisapp/startup/Checking database - 0.022
src/core/qgsruntimeprofiler.cpp: 54: (end) [0ms] PROFILE:
qgisapp/startup/Creating theme folder - 0
src/core/qgsproviderregistry.cpp: 105: (init) [2ms] Checking
/home/aaime/apps/lib/qgis/plugins for provider plugins
src/core/qgsproviderregistry.cpp: 158: (init) [7ms] Checking
/home/aaime/apps/lib/qgis/plugins/libbasicauthmethod.so: ...invalid (no
isProvider method)
src/core/qgsproviderregistry.cpp: 150: (init) [2ms] Checking
/home/aaime/apps/lib/qgis/plugins/libcoordinatecaptureplugin.so: ...invalid
(has type method)
QGIS died on signal 11Could not attach to process.  If your uid matches the
uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operazione non permessa.
No thread selected
No stack.
gdb returned 0
Annullato

I'm starting to think I'd be better of using a virtual machine where one
can do any custom setup required.
Someone was hinting at a video showing how to do that, using a vagrant
setup. Is the same also documented anywhere, like,
in text form?

Cheers
Andrea

== GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
(LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
http://www.geo-solutions.it http://twitter.com/geosolutions_it
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, 

[QGIS-Developer] Plugin [1350] Mascaret approval notification.

[noreply]

Plugin Mascaret approval by pcav.
The plugin version "[1350] Mascaret 0.1.10 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/Mascaret/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer