Error message when using Divvun Manager on Windows 10

[Trondtr]

The Version is 2.2.1 (fetched today). I mark a language for installation (Here: Komi-Zyryan, but I get the same behavuour for all languages). This is a new behaviour, as I was able to install spellers before the summer vacation.

[bbqsrc]

@Trondtr try again today, it is likely you were trying to install one of the -mso variants, and I have now removed those (they're built into the non-mso packages these days).

[Trondtr]

Thanks! I will have access to my Windows machine on monday, and I'll return to the issue then.

[snomos]

@rueter had an identical error:

[Trondtr]

Here is an update on this issue: I still get the same error msg (on a newly installed DM from today 9.3.) but only for some languages, thus for spellers smj, rmn, mrj spellers are installed, but for rmf, krl, mhr I get the error msg quoted.

It thus seems the error is not with the DM, but with the fsts. My question is thus: Where should I look for errors? My first thought is to make a speller for LO on my own machine, which I have done for rmf, krl, mhr, with success. So where should I look for the error distinguishing these three from smj, rmn, mrj? The error is not in the quality of the linguistic content: smj and mrj and mhr are mature, rmn are empty, rmf and krl are inbetween (linguistically speaking).

[Trondtr]

@bbqsrc in your earlier comment you asked whether the error msg still was there. I tried today, installing spellers for rmg, krl, vep, etc., and get the same error message as reported earlier. The DM version is 2.3.1.7b....e0

A further issue: I noticed that smn was installed in DM but not listed with the V mark in MS Word. I then uninstalled smn (which went well) and then tried to install it again. Then, the familiar error msg from above popped up. So it seems we are stuck.

[alvskar]

ExitStatus(7) appears to be coming from Windows itself here, and that corresponds to ERROR_ARENA_TRASHED. If that's indeed the error, it's a very vague one, effectively "something went seriously wrong and made Windows very unhappy".

Potentially system corruption, but given it's occurring only for specific languages, most likely the eventual installer .exe Pahkat runs to install the language is malformed somehow, there's some signing issue, etc. Might be an issue with how Pahkat is packaging some of the languages, or something off in the package itself. Not an issue that can be fixed within Divvun Manager.

This still occurring?

[Trondtr]

Unfortunately the Department wanted their Windows computer back, but I have an older machine, also with Windows 10 on it. My report is somewhat inconclusive:

On the positive side:

• I am not able to repeate the error message above. I install the Komi speller (or other spellers or keyboards), and the DM behaves, and gives the status "Installed" when I return to the app, both after and also before restart
• The Inari Saami keyboard and speller was installed during this test, and the keyboard showed up in the "Add language" menu in Windows afterwards, and worked.
• The Inari Saami speller worked as a dream in Libre Office, with today's date. Fantastic! (my MS Word was not available)
• The same was the case for Mansi (marked as {mns} by LO). I had installed it earlier, and it displayed today's date. Great!

More problematic

• I also installed two cyrillic-based keyboards and spellers. The Komi speller mentioned above, and Kildin Saami (keyboard) and Eastern Mari (both keyboard and spellers), were installed today and came out as "Installed" afterwards. Kildin Saami and Eastern Mari (the keyboards) did not come up in the keyboard menu (contrary to Inari Saami).
• The Eastern Mari spellchecker was listed by LO, but without the ABC, and without a speller.

The conclusion is thus that the DM works fine (?) but that there are some problems on (it seems) the Window side of things. My machine is old, so this should be tested by someone else.

[snomos]

Thanks for testing, @Trondtr . We'll keep this issue open a while still, awaiting more testing and feedback. @rueter could you try? And @aarppe ?

[snomos]

Also, we should check technical metadata for problematic packages, ie the manifest.toml file, which should contain proper UUID's. Just in case the UUID is bogus for whatever reason.