Re: [Qgis-user] QGIS 3.4.2 still very slow to work in Windows 10

[David Addy]

Thanks for all your comments. I think things were pretty good using 3.2, and
I had got used to using Version 3 with geopackage etc, and going back to
2.18 was rather painful for me. These hanging up problems for me really
started in 3.4. 
I have just found that changing my Settings to make QGIS start up with a new
project, (rather than loading the last project worked on) seems to be a lot
faster to open this way.



--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] QGIS 3.4.2 still very slow to work in Windows 10

[Mike Flannigan]

I can report that I do not see the same thing reported
below.  I use QGIS 3.2.0 on Win7 with a pretty good graphics
card and I don't have any problems at all.  I'm thinking it
has perhaps froze up a couple times since the install in late
June 2018, but I don't recall the last time that happened.

I just opened a project with 266,000 point features, and it
takes 18 seconds to open the attribute table, but works
flawlessly.

I am using Intel Zeon CPU E5-1630 v4 @ 3.70GHz - 16GB Ram.

I have never tried QGIS 3.4.1.



Mike


On 12/10/2018 2:00 PM, qgis-user-requ...@lists.osgeo.org wrote:

Hi David,
everything you've detected happens since the transition to 3.x also on
windows 7 on PC with i7 4780 and 32GB ram.
any operation, even the simplest one, such as saving or calculating polygon
areas in a shapefile causes freeze of QGIS. Not to mention the node tool
where a forum should be open apart there is a ticket here but only 8 people
have participated ...
(http://osgeo-org.1560.x6.nabble.com/Node-Tool-proposing-improvements-td5387054.html).
Moreover:
- there is  no currently a native topological verification tool of
shapefiles (the new validator incorporated in editing is almost impossible
to run on shapefile with hundreds of polygon in ...)
It will take years, in my opinion, before the 3.x version can be used
productively.
Unfortunately, the gap between users and developers remains gigantic,
although most of the developers say that users have been asked .. sin until
2.18.x everything was wonderful.

I Hope that somebody from QGIS.org can see our perplexities and adjust as
far as possible this version which for now remains only a container of good
ideas

Regards


-
Antonio


___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] 3.4.2: file dialogs freeze for several seconds (Mac Mojave)

[b.j.kobben]

Thanks Peter, the 3.4.2. version from that location indeed does not have the 
dialog freezing problem. So what’s different here...?


--
Barend Köbben


On 11/12/2018, 08:17, "Peter Petrik" 
mailto:peter.pet...@lutraconsulting.co.uk>> 
wrote:

Hi,

can you please try package from 
https://lutraconsulting.github.io/qgis-mac-packager/ and see if your problem 
persists even there?

Kind regards,
Peter


On Mon, Dec 10, 2018 at 4:38 PM 
mailto:b.j.kob...@utwente.nl>> wrote:
Hi all,

Since updating to 3.4.2 (from 3.4.1, details below*) whenever QGIS uses my 
systems (MacOS) file dialogs I experience freezes of up to several seconds: the 
whole QGIS software stops doing anything and does not react. Until now it 
always recovers, gets back to normal, but it makes using the software annoying 
and awkward. I also notice that when starting, the QGIS icon in the dock does 
not “bounce” as it’s supposed to, but hangs frozen in the air

Did anyone else experience this, and (preferably) knows a solution...?

* running on mac OSX Mojave 10.14.1:
QGIS version

3.4.2-Madeira

QGIS code branch

Release 3.4

Compiled against Qt

5.11.2

Running against Qt

5.11.2

Compiled against GDAL/OGR

2.3.2

Running against GDAL/OGR

2.3.2

Compiled against GEOS

3.7.0-CAPI-1.11.0

Running against GEOS

3.7.0-CAPI-1.11.0 673b9939

PostgreSQL Client Version

9.6.10

SpatiaLite Version

4.4.0-RC1

QWT Version

6.1.3

QScintilla2 Version

2.10.8

PROJ.4 Version

493


--
Barend Köbben
Senior Lecturer – ITC-University of Twente & ATLAS
PO Box 217, 7500 AE Enschede (Netherlands)
ITC Building (room 1-065)
@barendkobben
+31-(0)53 4874 253



___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] QGIS 3.4.2 still very slow to work in Windows 10

[Antongeo76]

Saber Razmjooei wrote
> On Tue, 11 Dec 2018 at 10:39, Antongeo76 <

> antoviscomi@

> > wrote:
> 
>> berndv. wrote
>> > Hi,
>> >
>> > I can't contribute to your particular problems, but have some remarks.
>> >
>> > You said you "reverted" to 2.18. On Windows, you can easily run 3.x
>> > besides 2.x. Do you have the same problems with 2.18?  If so, it's
>> > really your personal installation that fails, I think.
>> >
>> > The node tool was redesigned in 3.x, and there is quite a discussion
>> > going on, cause not so many people like the new behaviour.
>> >
>> > In general, I would like to say, that the promotion of the newest
>> > release shown in QGIS is quite a bad idea: The inexperienced will not
>> > hesitate to update and therefore run in every possible bug, being left
>> > clueless, while the more experienced are more cautious and install it
>> > only anlongside for testing purposes first.
>> >
>> > The developers are in a bad situation: They need lots of testers to
>> find
>> > bugs, but in my opinion they reach the wrong users with that
>> > advertisement. (no idea how to improve this)
>> >
>> > Furthermore, the new version had a bad start, cause (as I understood)
>> > last-minute-changes in dependencies caught them unprepared.
>> >
>> > Unfortunately, no one gives warnings about the major issues somewhere
>> > prominently e.g. on the QGIS.org website, so you have to read the
>> > mailing-list(s) and search in the issue queue yourself. In my opinion,
>> > in QGIS3 the developers were a little too ambitious, but it seems they
>> > also had kind of bad luck as well. Lots of features introduced are
>> > somewhat bleeding-edge and need time to ripe.
>> >
>> > As I rarely use Windows, I'm not of big help. I just want to recommend
>> > you to use the network installer (advanced install!) and install the
>> 2.x
>> > LTR and the 3.x LTR in parallel and update them through the installer
>> > once in a while, and keep 2.18 for productive work as long as you do
>> not
>> > trust the 3.x version.
>> >
>> > The open source mantra is "release early, release often", but that
>> > doesn't mean that everyone has to update early and often as well!
>> >
>> > Cheers,
>> >
>> > Bernd
>> >
>> > Am 10.12.18 um 17:59 schrieb David Addy:
>> >> I have always loved QGIS and I have extolled its virtues to local
>> >> historians
>> >> and archaeologists in my area.
>> >> I have had to keep quiet about it lately.
>> >> I was somewhat relieved to hear a comment on a recent video of the
>> >> Oceania
>> >> meeting that QGIS 3.4.1 was a dud release as it caused Windows to
>> crash
>> >> at
>> >> random moments. I had thought that all the long pauses, messages of
>> QGIS
>> >> not
>> >> responding, and crashing when being closed down was some awful feature
>> >> unique to my computer. I had even tried reverting to 2.18 for a while.
>> >> However, after I upgraded to 3.4.2 I still had problems.
>> >> Opening QGIS on Windows 10 can take over half a minute before anything
>> >> happens apart from the outline box of the QGIS window full of blank
>> >> space.
>> >> Once a project finally loads up any random operation can still get the
>> >> "QGIS
>> >> not responding" message.
>> >> This can result in further issues because I try pressing buttons to
>> get
>> a
>> >> response.
>> >> I even bought Anita's 4th edition of "Learn QGIS" to see if I was
>> doing
>> >> something radically wrong. It did highlight a few wrinkles until I got
>> to
>> >> page 55 when I discovered instructions on the edit node tool. This
>> tool
>> I
>> >> had used OK in the past, but it now baffles me totally. I cannot get
>> it
>> >> to
>> >> do what the book says.
>> >> I am now losing my confidence in 3.4.2 and can only hope that the next
>> >> point
>> >> release will produce improvements.
>> >> It would really help if known major issues like this could be posted
>> >> here,
>> >> perhaps as a sticky which stays at the top, to let users know that
>> they
>> >> are
>> >> not alone with an issue.
>> >> Sorry to complain.
>> >>
>> >>
>> >>
>> >> --
>> >> Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
>> >> ___
>> >> Qgis-user mailing list
>> >>
>>
>> > Qgis-user@.osgeo
>>
>> >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> > ___
>> > Qgis-user mailing list
>>
>> > Qgis-user@.osgeo
>>
>> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>>
>> HI Bernd,
>> I fully agree with you,
>> even on the fact of the versions installed and to be used for
>> productivity
>> (I've installed all concomitant versions available for a single machine,
>> and
>> I use them almost every day)...
>> the fact is that every time I write about freezes  or general
>> malfunctions
>> (here or in QGIS issues)
>> I

Re: [Qgis-user] QGIS 3.4.2 still very slow to work in Windows 10

[Antongeo76]

-
Antonio
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] QGIS 3.4.2 still very slow to work in Windows 10

[Saber Razmjooei]

On Tue, 11 Dec 2018 at 10:39, Antongeo76  wrote:

> berndv. wrote
> > Hi,
> >
> > I can't contribute to your particular problems, but have some remarks.
> >
> > You said you "reverted" to 2.18. On Windows, you can easily run 3.x
> > besides 2.x. Do you have the same problems with 2.18?  If so, it's
> > really your personal installation that fails, I think.
> >
> > The node tool was redesigned in 3.x, and there is quite a discussion
> > going on, cause not so many people like the new behaviour.
> >
> > In general, I would like to say, that the promotion of the newest
> > release shown in QGIS is quite a bad idea: The inexperienced will not
> > hesitate to update and therefore run in every possible bug, being left
> > clueless, while the more experienced are more cautious and install it
> > only anlongside for testing purposes first.
> >
> > The developers are in a bad situation: They need lots of testers to find
> > bugs, but in my opinion they reach the wrong users with that
> > advertisement. (no idea how to improve this)
> >
> > Furthermore, the new version had a bad start, cause (as I understood)
> > last-minute-changes in dependencies caught them unprepared.
> >
> > Unfortunately, no one gives warnings about the major issues somewhere
> > prominently e.g. on the QGIS.org website, so you have to read the
> > mailing-list(s) and search in the issue queue yourself. In my opinion,
> > in QGIS3 the developers were a little too ambitious, but it seems they
> > also had kind of bad luck as well. Lots of features introduced are
> > somewhat bleeding-edge and need time to ripe.
> >
> > As I rarely use Windows, I'm not of big help. I just want to recommend
> > you to use the network installer (advanced install!) and install the 2.x
> > LTR and the 3.x LTR in parallel and update them through the installer
> > once in a while, and keep 2.18 for productive work as long as you do not
> > trust the 3.x version.
> >
> > The open source mantra is "release early, release often", but that
> > doesn't mean that everyone has to update early and often as well!
> >
> > Cheers,
> >
> > Bernd
> >
> > Am 10.12.18 um 17:59 schrieb David Addy:
> >> I have always loved QGIS and I have extolled its virtues to local
> >> historians
> >> and archaeologists in my area.
> >> I have had to keep quiet about it lately.
> >> I was somewhat relieved to hear a comment on a recent video of the
> >> Oceania
> >> meeting that QGIS 3.4.1 was a dud release as it caused Windows to crash
> >> at
> >> random moments. I had thought that all the long pauses, messages of QGIS
> >> not
> >> responding, and crashing when being closed down was some awful feature
> >> unique to my computer. I had even tried reverting to 2.18 for a while.
> >> However, after I upgraded to 3.4.2 I still had problems.
> >> Opening QGIS on Windows 10 can take over half a minute before anything
> >> happens apart from the outline box of the QGIS window full of blank
> >> space.
> >> Once a project finally loads up any random operation can still get the
> >> "QGIS
> >> not responding" message.
> >> This can result in further issues because I try pressing buttons to get
> a
> >> response.
> >> I even bought Anita's 4th edition of "Learn QGIS" to see if I was doing
> >> something radically wrong. It did highlight a few wrinkles until I got
> to
> >> page 55 when I discovered instructions on the edit node tool. This tool
> I
> >> had used OK in the past, but it now baffles me totally. I cannot get it
> >> to
> >> do what the book says.
> >> I am now losing my confidence in 3.4.2 and can only hope that the next
> >> point
> >> release will produce improvements.
> >> It would really help if known major issues like this could be posted
> >> here,
> >> perhaps as a sticky which stays at the top, to let users know that they
> >> are
> >> not alone with an issue.
> >> Sorry to complain.
> >>
> >>
> >>
> >> --
> >> Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
> >> ___
> >> Qgis-user mailing list
> >>
>
> > Qgis-user@.osgeo
>
> >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
> > ___
> > Qgis-user mailing list
>
> > Qgis-user@.osgeo
>
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
> HI Bernd,
> I fully agree with you,
> even on the fact of the versions installed and to be used for productivity
> (I've installed all concomitant versions available for a single machine,
> and
> I use them almost every day)...
> the fact is that every time I write about freezes  or general malfunctions
> (here or in QGIS issues)
> I seem to be the only one to be affected (or we are in very few users to
> observe and report these anomalies) ...
>
> Greetings
> unfortunately it is often difficult to communicate remotely ...
> we 

Re: [Qgis-user] QGIS 3.4.2 still very slow to work in Windows 10

[Antongeo76]

berndv. wrote
> Hi,
> 
> I can't contribute to your particular problems, but have some remarks.
> 
> You said you "reverted" to 2.18. On Windows, you can easily run 3.x 
> besides 2.x. Do you have the same problems with 2.18?  If so, it's 
> really your personal installation that fails, I think.
> 
> The node tool was redesigned in 3.x, and there is quite a discussion 
> going on, cause not so many people like the new behaviour.
> 
> In general, I would like to say, that the promotion of the newest 
> release shown in QGIS is quite a bad idea: The inexperienced will not 
> hesitate to update and therefore run in every possible bug, being left 
> clueless, while the more experienced are more cautious and install it 
> only anlongside for testing purposes first.
> 
> The developers are in a bad situation: They need lots of testers to find 
> bugs, but in my opinion they reach the wrong users with that 
> advertisement. (no idea how to improve this)
> 
> Furthermore, the new version had a bad start, cause (as I understood) 
> last-minute-changes in dependencies caught them unprepared.
> 
> Unfortunately, no one gives warnings about the major issues somewhere 
> prominently e.g. on the QGIS.org website, so you have to read the 
> mailing-list(s) and search in the issue queue yourself. In my opinion, 
> in QGIS3 the developers were a little too ambitious, but it seems they 
> also had kind of bad luck as well. Lots of features introduced are 
> somewhat bleeding-edge and need time to ripe.
> 
> As I rarely use Windows, I'm not of big help. I just want to recommend 
> you to use the network installer (advanced install!) and install the 2.x 
> LTR and the 3.x LTR in parallel and update them through the installer 
> once in a while, and keep 2.18 for productive work as long as you do not 
> trust the 3.x version.
> 
> The open source mantra is "release early, release often", but that 
> doesn't mean that everyone has to update early and often as well!
> 
> Cheers,
> 
> Bernd
> 
> Am 10.12.18 um 17:59 schrieb David Addy:
>> I have always loved QGIS and I have extolled its virtues to local
>> historians
>> and archaeologists in my area.
>> I have had to keep quiet about it lately.
>> I was somewhat relieved to hear a comment on a recent video of the
>> Oceania
>> meeting that QGIS 3.4.1 was a dud release as it caused Windows to crash
>> at
>> random moments. I had thought that all the long pauses, messages of QGIS
>> not
>> responding, and crashing when being closed down was some awful feature
>> unique to my computer. I had even tried reverting to 2.18 for a while.
>> However, after I upgraded to 3.4.2 I still had problems.
>> Opening QGIS on Windows 10 can take over half a minute before anything
>> happens apart from the outline box of the QGIS window full of blank
>> space.
>> Once a project finally loads up any random operation can still get the
>> "QGIS
>> not responding" message.
>> This can result in further issues because I try pressing buttons to get a
>> response.
>> I even bought Anita's 4th edition of "Learn QGIS" to see if I was doing
>> something radically wrong. It did highlight a few wrinkles until I got to
>> page 55 when I discovered instructions on the edit node tool. This tool I
>> had used OK in the past, but it now baffles me totally. I cannot get it
>> to
>> do what the book says.
>> I am now losing my confidence in 3.4.2 and can only hope that the next
>> point
>> release will produce improvements.
>> It would really help if known major issues like this could be posted
>> here,
>> perhaps as a sticky which stays at the top, to let users know that they
>> are
>> not alone with an issue.
>> Sorry to complain.
>>
>>
>>
>> --
>> Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
>> ___
>> Qgis-user mailing list
>> 

> Qgis-user@.osgeo

>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
> ___
> Qgis-user mailing list

> Qgis-user@.osgeo

> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

HI Bernd,
I fully agree with you, 
even on the fact of the versions installed and to be used for productivity 
(I've installed all concomitant versions available for a single machine, and
I use them almost every day)... 
the fact is that every time I write about freezes  or general malfunctions
(here or in QGIS issues) 
I seem to be the only one to be affected (or we are in very few users to
observe and report these anomalies) ...

Greetings
unfortunately it is often difficult to communicate remotely ... 
we should have a developer sitting next to prove that the software often 
does not run as it should and you would expect



-
Antonio
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
_

Re: [Qgis-user] QGIS 3.4.2/GRASS

[Martin Bittens]

Luigi Pirelli,

thank you so much for your hints.

My QGIS 3.4.2 /GRASS installation is as follows:

PATH=C:\OSGEO4~1\apps\qgis\bin;C:\OSGEO4~1\apps\grass\grass-7.4.2\lib;C:\OSGEO4~1\apps\grass\grass-7.4.2\bin;C:\OSGEO4~1\apps\Python37;C:\OSGEO4~1\apps\Python37\Scripts;C:\OSGEO4~1\apps\qt5\bin;C:\Rtools\bin;C:\Rtools\mingw_32\bin;C:\Rtools\mingw_64\bin;C:\Program 
Files\MiKTeX 
2.9\miktex\bin;C:\OSGEO4~1\apps\Python27\Scripts;C:\OSGEO4~1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBem;C:\OSGEO4~1\apps\msys\bin;C:\Program 
Files\R\R-3.4.4\bin\x64;C:\Program Files\RStudio\bin

GDAL_DATA=C:\OSGEO4~1\share\gdal
GDAL_DRIVER_PATH=C:\OSGEO4~1\bin\gdalplugins
GDAL_FILENAME_IS_UTF8=YES
GEOTIFF_CSV=C:\OSGEO4~1\share\epsg_csv
GISBASE=C:\OSGEO4~1\apps\grass\grass-7.4.2
GRASS_PROJSHARE=C:\OSGEO4~1\share\proj
GRASS_PYTHON=C:\OSGEO4~1\bin\python.exe
JPEGMEM=100
OSGEO4W_ROOT=C:\OSGEO4~1
PROJ_LIB=C:\OSGEO4~1\share\proj
PYTHONHOME=C:\OSGEO4~1\apps\Python37
QGIS_PREFIX_PATH=C:/OSGEO4~1/apps/qgis
QT_PLUGIN_PATH=C:\OSGEO4~1\apps\qgis\qtplugins;C:\OSGEO4~1\apps\qt5\plugins
QT_RASTER_CLIP_LIMIT=4096
VSI_CACHE=TRUE
VSI_CACHE_SIZE=100
O4W_QT_PREFIX=C:/OSGEO4~1/apps/Qt5
O4W_QT_BINARIES=C:/OSGEO4~1/apps/Qt5/bin
O4W_QT_PLUGINS=C:/OSGEO4~1/apps/Qt5/plugins
O4W_QT_LIBRARIES=C:/OSGEO4~1/apps/Qt5/lib
O4W_QT_TRANSLATIONS=C:/OSGEO4~1/apps/Qt5/translations
O4W_QT_HEADERS=C:/OSGEO4~1/apps/Qt5/include

I am not sure if these settings are those you want to see. If you do 
need more, please let me know.


As far as I understood the QGIS 3.4.2 settings GRASS 7.4.2 should be 
used. After I read your comment on the path issues I checked the 
/apps/grass folder. 3 different versions are installed there:


grass-6.4.3

grass-7.4.2

grass-7.7.svn

In accordance to your advice I removed the .svn term from the GRASS 7.7 
folder name and - it works. I can use now the GRASS commands in QGIS 
3.4.2. Additionally I changed in the same way the folder name in the 
grass77svn.bat and the related env.bat using GRASS 7.7.svn as a 
stand-alone application as well.


I am  wondering which GRASS version QGIS 3.4.2 actually is using? 
Unfortunately in the QGIS 3.4.2 menu 
Settings/Options/Processing/Providers/GRASS there is no longer an option 
available that allows to define the path to the correct GRASS version 
(as it was in QGIS 3.2.1 - which was my last QGIS 3 version).


Best regards

Martin


Am 12/10/2018 um 4:48 PM schrieb Luigi Pirelli:
processing Grass7Utils.py is trying to understand the grass folders 
assuming that the path is something like grass-... 
in your case this path is grass-svn => bang! trying to convert it as 
int! it's, I'm almost sure, a bug... can you fill an issue in 
https://issues.qgis.org/projects/qgis/issues/new


the fix is simple, but please share more about what is your qgis 
installation and grass configuration


regards

Luigi Pirelli

**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* GitHub: https://github.com/luipir
* Mastering QGIS 2nd Edition:
* 
https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition

* Hire me: http://goo.gl/BYRQKg
**


On Mon, 10 Dec 2018 at 19:09, Martin Bittens > wrote:


Hello!

Today I made an update to QGIS 3.4.2 and now I can't use anymore the
GRASS commands in the toolbox The following python error message
appears
when I try to open a GRASS command:

2018-12-10T16:00:28 WARNING    Traceback (most recent call last):
   File

"C:/OSGEO4~1/apps/qgis/./python/plugins\processing\gui\ProcessingToolbox.py",

line 223, in executeAlgorithm
   ok, message = alg.canExecute()
   File

"C:/OSGEO4~1/apps/qgis/./python/plugins\processing\algs\grass7\Grass7Algorithm.py",

line 1020, in canExecute
   message = Grass7Utils.checkGrassIsInstalled()
   File

"C:/OSGEO4~1/apps/qgis/./python/plugins\processing\algs\grass7\Grass7Utils.py",

line 468, in checkGrassIsInstalled
   if Grass7Utils.installedVersion() is not None:
   File

"C:/OSGEO4~1/apps/qgis/./python/plugins\processing\algs\grass7\Grass7Utils.py",

line 98, in installedVersion
   if Grass7Utils.grassBin() is None:
   File

"C:/OSGEO4~1/apps/qgis/./python/plugins\processing\algs\grass7\Grass7Utils.py",

line 153, in grassBin
   path = Grass7Utils.grassPath()
   File

"C:/OSGEO4~1/apps/qgis/./python/plugins\processing\algs\grass7\Grass7Utils.py",

line 212, in grassPath
   grassfolders = sorted([f for f in
os.listdir(testfolder)
if f.start

Re: [Qgis-user] QGIS 3.4.2 still very slow to work in Windows 10

[Antongeo76]

Saber Razmjooei wrote
> It's been said a lot and often gets dismissed by users (similar to have
> you
> turn off and on your computer), but most of the issues can be resolved by:
> 1- Start your QGIS 3, with a clean profile.
> 2- Remove/disable all 3rd party plugins
> 
> If all fails, report the bug with a sample data and step-by-step to
> reproduce the issue.
> 
> Regards
> Saber
> 
> 
> On Mon, 10 Dec 2018 at 17:49, Bernd Vogelgesang <

> bernd.vogelgesang@

> >
> wrote:
> 
>> Hi,
>>
>> I can't contribute to your particular problems, but have some remarks.
>>
>> You said you "reverted" to 2.18. On Windows, you can easily run 3.x
>> besides 2.x. Do you have the same problems with 2.18?  If so, it's
>> really your personal installation that fails, I think.
>>
>> The node tool was redesigned in 3.x, and there is quite a discussion
>> going on, cause not so many people like the new behaviour.
>>
>> In general, I would like to say, that the promotion of the newest
>> release shown in QGIS is quite a bad idea: The inexperienced will not
>> hesitate to update and therefore run in every possible bug, being left
>> clueless, while the more experienced are more cautious and install it
>> only anlongside for testing purposes first.
>>
>> The developers are in a bad situation: They need lots of testers to find
>> bugs, but in my opinion they reach the wrong users with that
>> advertisement. (no idea how to improve this)
>>
>> Furthermore, the new version had a bad start, cause (as I understood)
>> last-minute-changes in dependencies caught them unprepared.
>>
>> Unfortunately, no one gives warnings about the major issues somewhere
>> prominently e.g. on the QGIS.org website, so you have to read the
>> mailing-list(s) and search in the issue queue yourself. In my opinion,
>> in QGIS3 the developers were a little too ambitious, but it seems they
>> also had kind of bad luck as well. Lots of features introduced are
>> somewhat bleeding-edge and need time to ripe.
>>
>> As I rarely use Windows, I'm not of big help. I just want to recommend
>> you to use the network installer (advanced install!) and install the 2.x
>> LTR and the 3.x LTR in parallel and update them through the installer
>> once in a while, and keep 2.18 for productive work as long as you do not
>> trust the 3.x version.
>>
>> The open source mantra is "release early, release often", but that
>> doesn't mean that everyone has to update early and often as well!
>>
>> Cheers,
>>
>> Bernd
>>
>> Am 10.12.18 um 17:59 schrieb David Addy:
>> > I have always loved QGIS and I have extolled its virtues to local
>> historians
>> > and archaeologists in my area.
>> > I have had to keep quiet about it lately.
>> > I was somewhat relieved to hear a comment on a recent video of the
>> Oceania
>> > meeting that QGIS 3.4.1 was a dud release as it caused Windows to crash
>> at
>> > random moments. I had thought that all the long pauses, messages of
>> QGIS
>> not
>> > responding, and crashing when being closed down was some awful feature
>> > unique to my computer. I had even tried reverting to 2.18 for a while.
>> > However, after I upgraded to 3.4.2 I still had problems.
>> > Opening QGIS on Windows 10 can take over half a minute before anything
>> > happens apart from the outline box of the QGIS window full of blank
>> space.
>> > Once a project finally loads up any random operation can still get the
>> "QGIS
>> > not responding" message.
>> > This can result in further issues because I try pressing buttons to get
>> a
>> > response.
>> > I even bought Anita's 4th edition of "Learn QGIS" to see if I was doing
>> > something radically wrong. It did highlight a few wrinkles until I got
>> to
>> > page 55 when I discovered instructions on the edit node tool. This tool
>> I
>> > had used OK in the past, but it now baffles me totally. I cannot get it
>> to
>> > do what the book says.
>> > I am now losing my confidence in 3.4.2 and can only hope that the next
>> point
>> > release will produce improvements.
>> > It would really help if known major issues like this could be posted
>> here,
>> > perhaps as a sticky which stays at the top, to let users know that they
>> are
>> > not alone with an issue.
>> > Sorry to complain.
>> >
>> >
>> >
>> > --
>> > Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
>> > ___
>> > Qgis-user mailing list
>> > 

> Qgis-user@.osgeo

>> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> ___
>> Qgis-user mailing list
>> 

> Qgis-user@.osgeo

>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
> 
> 
> 
> -- 
> Saber Razmjooei
> www.lutraconsulting.co.uk
> 
> ___
> Qgis-user mailing list

> Qgis-user@.osgeo

> List info: https://lists.os

Re: [Qgis-user] QGIS 3.4.2 still very slow to work in Windows 10

[Saber Razmjooei]

It's been said a lot and often gets dismissed by users (similar to have you
turn off and on your computer), but most of the issues can be resolved by:
1- Start your QGIS 3, with a clean profile.
2- Remove/disable all 3rd party plugins

If all fails, report the bug with a sample data and step-by-step to
reproduce the issue.

Regards
Saber


On Mon, 10 Dec 2018 at 17:49, Bernd Vogelgesang 
wrote:

> Hi,
>
> I can't contribute to your particular problems, but have some remarks.
>
> You said you "reverted" to 2.18. On Windows, you can easily run 3.x
> besides 2.x. Do you have the same problems with 2.18?  If so, it's
> really your personal installation that fails, I think.
>
> The node tool was redesigned in 3.x, and there is quite a discussion
> going on, cause not so many people like the new behaviour.
>
> In general, I would like to say, that the promotion of the newest
> release shown in QGIS is quite a bad idea: The inexperienced will not
> hesitate to update and therefore run in every possible bug, being left
> clueless, while the more experienced are more cautious and install it
> only anlongside for testing purposes first.
>
> The developers are in a bad situation: They need lots of testers to find
> bugs, but in my opinion they reach the wrong users with that
> advertisement. (no idea how to improve this)
>
> Furthermore, the new version had a bad start, cause (as I understood)
> last-minute-changes in dependencies caught them unprepared.
>
> Unfortunately, no one gives warnings about the major issues somewhere
> prominently e.g. on the QGIS.org website, so you have to read the
> mailing-list(s) and search in the issue queue yourself. In my opinion,
> in QGIS3 the developers were a little too ambitious, but it seems they
> also had kind of bad luck as well. Lots of features introduced are
> somewhat bleeding-edge and need time to ripe.
>
> As I rarely use Windows, I'm not of big help. I just want to recommend
> you to use the network installer (advanced install!) and install the 2.x
> LTR and the 3.x LTR in parallel and update them through the installer
> once in a while, and keep 2.18 for productive work as long as you do not
> trust the 3.x version.
>
> The open source mantra is "release early, release often", but that
> doesn't mean that everyone has to update early and often as well!
>
> Cheers,
>
> Bernd
>
> Am 10.12.18 um 17:59 schrieb David Addy:
> > I have always loved QGIS and I have extolled its virtues to local
> historians
> > and archaeologists in my area.
> > I have had to keep quiet about it lately.
> > I was somewhat relieved to hear a comment on a recent video of the
> Oceania
> > meeting that QGIS 3.4.1 was a dud release as it caused Windows to crash
> at
> > random moments. I had thought that all the long pauses, messages of QGIS
> not
> > responding, and crashing when being closed down was some awful feature
> > unique to my computer. I had even tried reverting to 2.18 for a while.
> > However, after I upgraded to 3.4.2 I still had problems.
> > Opening QGIS on Windows 10 can take over half a minute before anything
> > happens apart from the outline box of the QGIS window full of blank
> space.
> > Once a project finally loads up any random operation can still get the
> "QGIS
> > not responding" message.
> > This can result in further issues because I try pressing buttons to get a
> > response.
> > I even bought Anita's 4th edition of "Learn QGIS" to see if I was doing
> > something radically wrong. It did highlight a few wrinkles until I got to
> > page 55 when I discovered instructions on the edit node tool. This tool I
> > had used OK in the past, but it now baffles me totally. I cannot get it
> to
> > do what the book says.
> > I am now losing my confidence in 3.4.2 and can only hope that the next
> point
> > release will produce improvements.
> > It would really help if known major issues like this could be posted
> here,
> > perhaps as a sticky which stays at the top, to let users know that they
> are
> > not alone with an issue.
> > Sorry to complain.
> >
> >
> >
> > --
> > Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
> > ___
> > Qgis-user mailing list
> > Qgis-user@lists.osgeo.org
> > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user



-- 
Saber Razmjooei
www.lutraconsulting.co.uk
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] disabling qgis.db

[Régis Haubourg]

Hi, well I used a python script, and my admin guys rewrote it from scratch
with powershell.

The business logic was this one:

- create a template folder accessible to the init script.
  - in the folder add a  cleaned template QGIS user profile
  - add a "delta" ini file containing all keys you want to add, delete,
update. I used a diff syntax (+ to add, - to delete, nothing to update)
- we add a file flag in each user profile that has been treated
- on session opening:
  - if you don't find the flag, deploy a preconfigured the raw qgis profile
  - if you find the profile. Apply the delta file to maintain the profile

Done.

Cheers
Régis



Le mar. 11 déc. 2018 à 08:46,  a
écrit :

> Hi Régis,
>
>
>
> thanks for your reply! How did you do it? Python script on session start?
> In my case, it would be OK if e.g. users have their individual GUI settings
> or spatial bookmarks but all connections in browser-panel and default CRS
> should reset to (globally maintained) default on closing QGIS. Do you have
> experience how to implement that?
>
>
>
> Regards
>
> Benjamin
>
>
>
> *Von:* Régis Haubourg [mailto:regis.haubo...@gmail.com]
> *Gesendet:* Montag, 10. Dezember 2018 17:12
> *An:* Fuenfer-Koenigstein.Benjamin IT-LN-TS
> *Cc:* QGIS list
> *Betreff:* Re: [Qgis-user] disabling qgis.db
>
>
>
> Hi Benjamin,
>
> I think the guidelines for software generally assumes that user profiles
> should be in editable location. I'm not sure we can ensure you in the long
> run that you will not face regressions sometimes.
>
> To adress your use case, I used to work with session startup script that
> cleared / reset user profiles on session close or session opening. The
> assumption was to let user free to change their profile settings but not
> for all settings (mandatory plugins for instance, default SRS..)
>
> Cheers
>
> Régis
>
>
>
>
>
> Le lun. 10 déc. 2018 à 16:19,  a
> écrit :
>
> Hello,
>
>
>
> I have an issue with creating a central QGIS configuration on a network
> drive. The goal is to have one read-only configuration that all users use.
> Generally works like a charm with starting QGIS 3.2 with --profiles-path
> pointing to a read-only dir. Users get the right settings, they still can
> play around but changes are discarded when quitting QGIS. Only problem is
> qgis.db, seems that QGIS necessarily needs write access to that file,
> otherwise it throws an error at start (but works with no problems
> subsequently). Is there any way to avoid that, e.g. starting qigs ‘silent’
> or setting the path to qgis.db to a local user folder? Seems that qgis.db
> doesn’t contain any crucial configuration, though same bookmarks for all
> users would be nice to have.
>
> I’m aware of https://issues.qgis.org/issues/13732 and generally
> understand Nathan’s and Nyall’s point of view but still think it would make
> sense to ignore qgis.db for use cases like mine.
>
>
>
> Thanks for your ideas and help!
>
>
>
> Regards
>
>
>
> Benjamin Fünfer-Königstein
>
>
>
>
>
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
>
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user