That is helpful… I’ll try to make them the same.
1 Like
This might be a bit beyond scope.
The Gramps AOI installer has a default (non-optional) Dictionary and Translation set to en-GB.
However, given the color/colour and -ize/-ise thoughout the GUI, the Translation must be en-US (which is not an option in the Translations checkboxes)
This is probably not very important… except the the en-US Dictionary option IS available and yet IS NOT selected by default.
Responses in the past say it is not possible to deselect the en-GB defaults in Dictionaries and Translations.
But perhaps TWO dictionaries could selected by default? The en-GB and the en-US ?
@Nick-Hall and colleagues, I think you’ll find this Gramps AIO 6.0.7 windows version ready for final testing:
It should now put the files as before:
Sorry, @emyoulation I wasn’t able to alter the translation languages.
2 Likes
I really appreciate all the work that you have put into this. The old cx_Freeze version was failing to build on a regular basis. Hopefully the PyInstaller version will be more reliable.
I don’t use Windows myself, but I’m sure that there are people who are willing to do some testing for us.
2 Likes
I’ve used Windows forever but I’m not a developer. That probably means that although I willing to do some testing I’m not actually able to help because I’ve no idea what to do with the .yml file on the end of the link posted by @dsblank.
Any clues as to how to use it to get a .exe that I can run and report back on what happens?
There is a link at the bottom of the link to download a zip file, then run the installer exe.
Oh, I’ll take another look as I missed that…
1 Like
I think I’m not seeing it because I don’t have a github account. I’ll create one as soon as I get a chance…
2 Likes
@dsblank Thanks so much for generating this build and the new installer! 
I installed it in a Windows 10 clean sandbox environment. The first problem I’ve encountered after creating a new family tree is that running Family Trees > Import… crashes Gramps to the desktop every time. Is anyone else seeing this? In the same environment, I installed Gramps 6.0.6 and this operation works fine.
Comparing the output of Pre-Requisites checker on 6.0.7 vs 6.0.6 and ignoring version differences, 6.0.7 is missing:
- GExiv2 (known)
- GooCanvas
- NumPy
- pydotplus
- pygraphviz
Finally, a few console messages on startup:
(process:4260): GLib-GIRepository-CRITICAL **: 13:49:30.774: Unable to load platform-specific GIO introspection data: Typelib file for namespace 'GLibWin32' (any version) not found
(process:4260): GLib-GIRepository-CRITICAL **: 13:49:30.914: Unable to load platform-specific GIO introspection data: Typelib file for namespace 'GioWin32' (any version) not found
(gramps.exe:4260): Gtk-WARNING **: 13:49:47.450: Could not find the icon 'missing-image-ltr'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
http://icon-theme.freedesktop.org/releases
Any ideas?
The Windows Event viewer might have recorded why Gramps was killed by Windows
Thanks for the reminder. Crash occurs in libglib-2
Problem signature
Problem Event Name: APPCRASH
Application Name: grampsw.exe
Application Version: 0.0.0.0
Application Timestamp: 69bee2da
Fault Module Name: libglib-2.0-0.dll
Fault Module Version: 2.88.0.0
Claude says:
The crash is almost certainly missing gschemas.compiled. Two problems:
- glib-compile-schemas.exe is probably not in the PyInstaller bundle (it’s a utility, not imported by Python), so the NSIS
post-install step silently fails - GSETTINGS_SCHEMA_DIR is not set in grampsaiow.py, so GLib doesn’t know where to find schemas even if they were compiled
The fix has two parts:
In build.sh: compile the schemas during the build (before pyinstaller runs) so gschemas.compiled is already present when PyInstaller
copies share/glib-2.0/schemas/ into the bundle:
glib-compile-schemas /mingw64/share/glib-2.0/schemas/
In grampsaiow.py: tell GLib where to find the compiled schemas at runtime:
environ[“GSETTINGS_SCHEMA_DIR”] = join(_meipass, “share”, “glib-2.0”, “schemas”)
This way we don’t need glib-compile-schemas.exe in the bundle at all — the compiled file is baked in at build time.
@codefarmer or others: would you be able to pick up it up at this point? I just can NOT test out the binaries.
I’m able to spend some time on it today. However, at this point I feel I might have a better chance at attempting to fix the AIO (cx_freeze version) than the new one. Let me pick that up from the comments you posted about fixing the ssl cert issues in that build.
A post was split to a new topic: Strange “db changed” Debugging warning
@emyoulation Can we move @stuck’s message with feedback on the released Windows AIO 6.0.7 to a new thread? The reason is that this thread is about the alternate installer that Doug created, whereas the released installer available now is not based on that. Thanks.
2 Likes
We can probably close this whole post
1 Like