#1416 closed defect (worksforme)
wingrass7 nightly build crash on start
Reported by: | MilenaN | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.0.0 |
Component: | Startup | Version: | svn-trunk |
Keywords: | encoding | Cc: | |
CPU: | x86-64 | Platform: | MSWindows 7 |
Description
Hi,
wingrass7 behaves in a strange way on start:
- It starts in a minimised window, so the user is not sure if anything happened after clicking the grass icon.
- When the (windows) user finds eventually the minimised grass window and makes it bigger, the cmd window (!) appears, encouraging him gently to "Hit RETURN to continue" (what on earth RETURN is, the user thinks).
- Finally Welcome window appears but no grass database can be found (when grass 64 and 65 have no problem with it on the same pc). Pointed to the path, grass crasches with the following message in cmd:
Traceback (most recent call last):
File "C:\Program Files (x86)\GRASS 7.0.SVN\etc\gui\wxpython\gis_set.py", line
877, in <module>
GRASSStartUp = StartUp(0)
File "c:\OSGeo4W\apps\Python25\lib\site-packages\wx-2.8-msw-unicode\wx\_core.p
y", line 7935, in init
self._BootstrapApp()
File "c:\OSGeo4W\apps\Python25\lib\site-packages\wx-2.8-msw-unicode\wx\_core.p
y", line 7509, in _BootstrapApp
return _core_.PyAppBootstrapApp(*args, kwargs)
File "C:\Program Files (x86)\GRASS 7.0.SVN\etc\gui\wxpython\gis_set.py", line
862, in OnInit
File "C:\Program Files (x86)\GRASS 7.0.SVN\etc\gui\wxpython\gis_set.py", line
697, in OnBrowse
self.OnSetDatabase(event)
File "C:\Program Files (x86)\GRASS 7.0.SVN\etc\gui\wxpython\gis_set.py", line
686, in OnSetDatabase
self.OnSelectLocation(None)
File "C:\Program Files (x86)\GRASS 7.0.SVN\etc\gui\wxpython\gis_set.py", line
635, in OnSelectLocation
self.listOfLocations[self.lblocations.GetSelection()]))
File "C:\Program Files (x86)\GRASS 7.0.SVN\etc\gui\wxpython\gis_set.py", line
599, in UpdateMapsets
gisdbase = self.gisdbase)
File "c:/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/etc/gui/wxpython/gui
_modules/gcmd.py", line 610, in RunCommand
File "c:/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/etc/gui/wxpython/gui
_modules/gcmd.py", line 610, in <lambda>
File "c:/osgeo4w/usr/src/grass_trunk/dist.i686-pc-mingw32/etc/gui/wxpython/gui
_modules/utils.py", line 664, in DecodeString
File "C:\Program Files (x86)\GRASS 7.0.SVN\Python25\lib\encodings\utf_8.py", l
ine 16, in decode
return codecs.utf_8_decode(input, errors, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xa3 in position 26: unexpect ed code byte Error in GUI startup. If necessary, please report this error to the GRASS develo pers. Switching to text mode now.
Change History (4)
comment:1 by , 12 years ago
follow-up: 3 comment:2 by , 11 years ago
Keywords: | encoding added |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
Although, it is hard to say if this encoding error was fixed, no activity and no further reports, so closing this ticket as worksforme, so there are some people here and there running localized GRASS 7 on MS Windows.
Reopen if the the error is the same, create a new one if the error is different. Please try to make ticket summary less general, e.g. use end of the Python traceback (WinGRASS 7 nightly build crash on start with UnicodeDecodeError). Use {{{
and }}}
to separate tracebacks or any other errors from your text in the report. However, thanks for your reports in any form.
Good comment about Hit RETURN to continue, create a ticket for it if you think that it should be changed (and discuss some translation if possible).
follow-up: 4 comment:3 by , 11 years ago
Replying to wenzeslaus:
Good comment about Hit RETURN to continue, create a ticket for it if you think that it should be changed (and discuss some translation if possible).
I was pretty shocked last year when I was talking some post-grad students through some task and they just looked at me blankly when I said to press the Return key. These kids never saw a typewriter.... No idea how I'd try to explain the difference between \r and \n to them. :)
methinks we need to teach them. ;)
Hamish
ps- the translation's easy, aka "Enter"
comment:4 by , 11 years ago
Replying to hamish:
ps- the translation's easy, aka "Enter"
"Enter" is typically printed on the key on the lower-right of the numeric keypad. While that often has the same effect as the Return (down-and-left-arrow) key, it isn't always the case.
Please try out more recent build. Still relevant?