-
-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Windows 8.4.0dev cannot launch GUI with error in gui\wxpython\lmgr\statusbar.py
#3738
Comments
What's strange is that I only get it from a fresh install/environment, not from updating my current real OS OSGeo4w installation + patching. Is it something to do that some files/gisbase are not created yet on first launch after a new install and don't get noticed when developping? |
What do you get when you run |
I'll try tomorrow, it's a good idea. I managed to understand how to step through all initialization code+the called subprocess within vscode, inside windows sandbox and the osgeo4w installation of grass. I ended up getting at the point were it fails, and it's like the stack trace. What's weird was that in these lines: grass/gui/wxpython/lmgr/statusbar.py Lines 125 to 133 in b0a00b4
The result of gs.find_file() before the square brackets indexing was effectively |
But thinking about it, I might have an idea for this bug and #3739. Since the revision info and library (libgis) build dates are reporting outdated, and that at the beginning of the trace it mentions three libraries that can't be loaded, is it possible that the OSGeo4W build are built in a clean environment, and/or only do incremental compilation, and/or keep the repo cloned, and don't clean completely the file tree, ie either I found some alternative osgeo4w builds (https://wingrass.fsv.cvut.cz/grass84/osgeo4w/), and I think I found how to use them. So since I finished going through the debugging (finding out how to set it up was the longest), I want to flush the windows sandbox (close it and reopen it), and start again with that alternative package from the OSGeo4W installer, and see if the results are the same. If so, I'll also try the standalone windows builds from https://wingrass.fsv.cvut.cz/grass84/ and compare too. |
@petrasovaa I think you've got something: On a fresh install of 8.4-313-f4d8...-1 (fresh sandbox), running
But But on another fresh sandbox, downloading https://wingrass.fsv.cvut.cz/grass84/osgeo4w/grass-daily-8.4.0dev-55b2a2bccc-78.tar.bz2, predownloading (without installing) the requirements of the OSGeo4W grass-dev packages, then installing from local dir everything except grass-dev, then installing this grass-daily, this one works fine (except the formatting string in the history file), that works for the first time (like before I filed #3726, since no history existed yet). So I'm still tending towards a build issue rather than code issue. Maybe both? |
@echoix, the gdal308/gdal309 OSGeo4W packaging issue is fixed now since grass-dev-8.4-314-f3ccff668-1. |
I'm not available right now to test it again, but will try again later |
I was able to retry with grass-dev 8.4-314-xxxxxx-1, and it is effectively solved. I hope it isn't transient, and an intentional fix (to some code or the build environment) was applied. |
I don't know. I think @jef-n knows for sure. |
I didn't see any commits on the repo since you mentioned that it was fixed |
tested with OSGeo4W
GUI starts here. closing ticket? |
Describe the bug
I applied the changes from #3732 in a fresh installation in windows sandbox, since the nightly 8.4-313-f4d8c62ac-1 (for commit f4d8c62) didn't include the yet unmerged #3732.
I still get another error prevent from launching the GUI, and when I enter
g.gui wxpython
, I can get a stack trace mentioning the statusbar.py file, withgs.find_file
keyerror: 'name'To reproduce
Expected behavior
GRASS GUI is usable on windows at release
Screenshots
System description
Additional context
Before trying nightly 8.4-313-..., I tried 8.4-312-75375c90a-1 (for commit 75375c9), and in fact without patching 8.4-313-... and 8.4-312-..., on windows sandbox I get this error, while on my normal OS grass dev installation, with both unpatched I get the bug from #3726.
The text was updated successfully, but these errors were encountered: