QGIS » QGIS Application

I think this bug is specific to the 64 bits version. Can you retry with the 32 bits version?

Yes, I can confirm that this problem is specific to the 64-bit version of QGIS. I ran both versions (32 and 64 bit) in a virtual machine (Win 7 x64) and had no issues with the 32-bit version, but repeated the issue in the 64-bit version. I also tried the 32-bit version of QGIS in a virtual machine with Win 8.0 x64 and had no problems plotting graphs, while it was with my 64-bit version of QGIS in Win 8.1 x64 that I first noticed the issue.

Unfortunately, I cannot switch to the 32-bit QGIS (Win 8.1 x64) because I ran into a more serious issue with GRASS, where it would simply crash after the first operation (in GRASS (standalone), within QGIS, and within the Processing plugin).

I am still willing to try solutions within virtual machines to help with the debugging of the plotting issue within the Processing plugin. I really like this plugin and think this is a necessary tool for spatial analysis.

Unfortunately, I cannot switch to the 32-bit QGIS (Win 8.1 x64) because I ran into a more serious issue with GRASS, where it would simply crash after the first operation (in GRASS (standalone), within QGIS, and within the Processing plugin).

this is another issue. If it GRASS standalone crashes for some reason then it is normal it does not work in the qgis plugin or processing toolbox.

How GRASS was installed, using the qgis standalone installer? osgeo4w? what is the module that makes it crash?

I really like this plugin and think this is a necessary tool for spatial analysis.

yes, in fact it is not a plugin anymore, is part of qgis now.

does this happen only on Windows or Linux too?

On Linux it works as expected.

I haven't tried it on Linux, nor will I in the near future.

I had installed QGIS as a standalone (not osgeo4w). Every command made it crash. Strangely though, I could load layers from the database, but as soon as I ran a command, a windows shell window opened and closed quickly (could not read any text within it), and then it stopped responding. Examples of commands I tried - v.buffer.dist and v.distance.

I had installed QGIS as a standalone (not osgeo4w). Every command made it crash. Strangely though, I could load layers from the database, but as soon as I ran a command, a windows shell window opened and closed quickly (could not read any text within it), and then it stopped responding. Examples of commands I tried - v.buffer.dist and v.distance.

processing works overall ok on Windows standalone/osgeo4w, and what you are experiencing can be a local issue. A screencast would help try understand what it is going on.

I believe this qualifies as blocker because it is a functionality that doesn't work as expected. It is not technically a regression because it never worked properly, but it's a problem that usually frustrates users and leads them to conclude "the R integration doesn't work".

Filipe Dias wrote:

I believe this qualifies as blocker because it is a functionality that doesn't work as expected. It is not technically a regression because it never worked properly, but it's a problem that usually frustrates users and leads them to conclude "the R integration doesn't work".

I understand Filipe, but it is not a regression and when fixed it can always be updated as a plugin. In my point of view then processing issues should never be blockers, especially if during the pre-release period there is now one actively working on them.

The fix reported in #7643 works for me with QGIS 2.8.1 from OSGeo4W64.
After deleting the processing directory in .qgis2/python/plugins,
plots were generated as expected by for instance the "F Function" and
the "G Function".

Some providers are being removed from QGIS/Processing (will be available as plugin) and so are their categories in the bug tracker. To not leave them orphaned of a category they are being reassigned to processing/core.