Closed CyrilleB79 closed 1 year ago
Hi @CyrilleB79. Although is hard to replicate this issue now, I found another issue that is related with this one. I was not aware that submodules can't be imported from installTasks, when IBMTTS is installed the first time, installTasks won't run because the required modules are not loaded from the pending install.
In your case the imported module was present from the previous copy of IBMTTS, but not the new required appConfig module.
I removed the importing references to local submodules of the add-on in the installTasks file.
I'm closing this issue now, please feel free to comment it if you still get issues.
Note: This issue is a copy of the issue previously reported on NVDA add-on mailing list. As asked for better traceability, I open this GitHub issue in the repo.
Message
Hi David
I have been facing an issue updating IBMTTS. This message is just for your information or for whoever is facing the same issue because, personally, I have found a workaround.
My IBMTTS version was 22.07.x (do not remember exactly which one) and I was running NVDA 2022.4. First, I have updated NVDA to 2023.1beta1. Logically, IBMTTS as well as many other add-ons have become incompatible. Then I have manually downloaded IBMTTS 23.02.1 and tried to install it. I have had an error in install task, failing on the following import:
from synthDrivers._settingsDB import appConfig
I have not a copy of the error traceback anymore. Thus the add-on could not be updated.I have disabled all add-ons except IBMTTS in add-on manager and tried to reinstall, but I was facing the same error.
Finally, I have restarted NVDA with add-on disabled and installed IBMTTS 23.02.1 successfully.
To try reproducing the error (to report it to you), I have installed (actually unzipped) IBMTTS 22.07.2 in a clean NVDA config. And tried to update to IBMTTS 23.02.1. The driver has been updated successfully. However on next restart, I have the following error in the log:
As written before, this is just for your information, given that as a workaround, the add-on can be installed after restarting NVDA with add-ons disabled.
Cheers,
Cyrille