https://bz.apache.org/ooo/show_bug.cgi?id=121930
--- Comment #132 from John <john.h...@yahoo.co.uk> --- Thank you. hanya describes his analysis of the problem and the rationale for his script in Comment 103 which I have copied below. (NB. hanya's reference to registrymodifications.xcu is in response to my Comment 102 where I wrongly thought the fault lay in registrymodifications.xcu) In my [hanya] oppinion, the spell checker problem is not in registrymodifications.xcu, but the problem there in the remained configuration file in user/uno_packages/cache/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend directory. If a configuration file which contains %origin% placeholder in an extension package, a file is created with expanded %origin% in the backend directory. It looks, if uninstallation or update of some extension package terminated by some issue, a generated file remained in backend. But the real contant of the extension package has been gone. So the remaiend file tells the dictionary file should be loaded. But if there is no dictionary file in the specified location in the configuration, all words are marked as wrong with red wave under line. After revision 1762054, dictionary files not found are ignored. But still the broken configuration causes problems like spell checker not working. Even if there is the way to reset registrymodification.xcu file, this problem would not be solved. Because there is no settings causes this problem in registrymodification.xcu file. So, proposed way to fix this problem in user's profile is: - Find configuration files which contains dictionary location in the configuration backedn directory mentioned above. - Check existance of dictionary files listed in the found files. - If a dictionary file is not exist anymore, omit the part in the file. - Restart the office. - Check dictionaries installed in the extension manager. The files in the registry backend should be listed in backenddb.xml and configmgr.ini file. If we can remove files which contains the problem safely from the lists, we should do so. But remained configuration files are not problem if there is no error in the file anymore. -- You are receiving this mail because: You are the assignee for the issue.
