Bug report #12657

Processing/GRASS don't work under Windows if username or input/output paths have non ascii chars

Added by Giovanni Manghi over 4 years ago. Updated 9 months ago.

Status:Closed
Priority:Normal
Assignee:Victor Olaya
Category:Processing/GRASS
Affected QGIS version:3.4.4 Regression?:No
Operating System:Windows Easy fix?:No
Pull Request or Patch supplied:No Resolution:fixed/implemented
Crashes QGIS or corrupts data:No Copied to github as #:20770

Description

Already discussed with Victor and Alexander. The issue has no easy solution apparently.

If the username has non ascii chars in it Processing returns the error message saying that GRASS is not installed.

If the non ascii chars are in the input/output paths then the modules run but ultimately fail.

This is no issue under Linux.


Related issues

Related to QGIS Application - Bug report #9425: grass_script.bat always fails if USERNAME contains MBCS Closed 2014-01-25
Related to QGIS Application - Bug report #13120: Processing gdal tools do not work if Windows username con... Closed 2015-07-15
Related to QGIS Application - Bug report #16250: Processing ogr tools problems in QGIS 2.18.10 when specia... Closed 2017-02-28

History

#1 Updated by Giovanni Manghi over 4 years ago

  • Affected QGIS version changed from 2.8.1 to master
  • Priority changed from Normal to High
  • Target version set to Future Release - High Priority

#2 Updated by Médéric RIBREUX over 3 years ago

  • Status changed from Open to In Progress

Hello,

I am working on it (only made with GRASS7)...

Following my work on #9425, I found a way to use input and output files with mbcs characters in their name for GRASS7 algorithms.

I have made the fix tests on MS-Windows XP for the moment (the only VM with MS I have). I will try it on MS-Windows 7 next week and make a Pull-Request for this soon (so you can test it).

Stay tuned !

#3 Updated by Giovanni Manghi over 3 years ago

thanks!

#4 Updated by Médéric RIBREUX over 3 years ago

Hello,

the PR is published.

Feel free to test it !

#5 Updated by Giovanni Manghi almost 3 years ago

  • Pull Request or Patch supplied changed from No to Yes

#6 Updated by Giovanni Manghi over 2 years ago

  • Target version deleted (Future Release - High Priority)
  • Priority changed from High to Normal
  • Status changed from In Progress to Open

#7 Updated by Giovanni Manghi over 2 years ago

  • Easy fix? set to No
  • Regression? set to No

#8 Updated by Victor Olaya 9 months ago

  • Description updated (diff)
  • Status changed from Open to Feedback

Things seem to be fine in 3.4.

Should this be closed?

#9 Updated by Giovanni Manghi 9 months ago

Victor Olaya wrote:

Things seem to be fine in 3.4.

Should this be closed?

I will check ASAP.

#10 Updated by Giovanni Manghi 9 months ago

  • Resolution set to fixed/implemented
  • Pull Request or Patch supplied changed from Yes to No
  • Status changed from Feedback to Closed
  • Affected QGIS version changed from master to 3.4.4

yes, it seems fixed!

Also available in: Atom PDF