Created attachment 70785 [details] Bundled English spelling extension has unknown status, LOdev daily build 2012-11-28 on Mac OS X I don’t know if this a severe problem or just a glitch, but anyway I need to report it: In the newest daily master build for Mac OS X, i. LOdev 4.0.0.0.alpha1+ (Build ID: 519c947f213ec69b0c92d3ea76193270644263e; pull time: 2012-11-28 04:07:39) the “Extension Manager” window says that our bundled “English spelling dictionaries, hyphenation rules, thesaurus, and grammar checker“ extension has “unknown” status. See the attached screenshot. This problem was NOT present in the previous daily build I have tested, i.e. LOdev 4.0.0.0.alpha1+ (Build ID: 6aabe09ac092c51d4b394bde9c7ea0055b952e3; pull time: 2012-11-26 00:28:52). So: a regression?! Removing/renaming the LOdev user profile does NOT change the situation: the extension still has the “unknown” status. I have not installed any other extensions at all. It does not change the situation if I install the the US English language Pack or not. Tested on Mac OS X 10.6.8 (Intel).
@ Andras Timar: Hi Andras, I do not know who is our expert for such issues (is this an extension issue or a linguistic issue), but I hope you can take a look at my report and decide what to do -- if this is not a problem at all, but just or glitch, or if this is a serious problem, and who can help here ... Thank you very much!
I have the same situation for a year or so in retail... and no one was giving a damn so far.
From an --enable-dbgutil installation's output below, it looks like a problem related to the Python 3 switch to me. > Python exception: <class 'ImportError'>: type lightproof_impl_en.locales is unknown, traceback follows > lo/core/solver/unxlngx6/installation/opt/program/uno.py:303 in function _uno_import() [raise ImportError( "type "+ name + "." +x + " is unknown" )] > lo/core/solver/unxlngx6/installation/opt/share/extensions/dict-en/Lightproof.py:6 in function <module>() [from lightproof_impl_en import locales] > lo/core/solver/unxlngx6/installation/opt/program/pythonloader.py:100 in function getModuleFromUrl() [exec(codeobject, mod.__dict__)] > lo/core/solver/unxlngx6/installation/opt/program/pythonloader.py:146 in function writeRegistryInfo() [mod = self.getModuleFromUrl( locationUrl )] > > warn:desktop.deployment:3944:1:lo/core/desktop/source/deployment/registry/dp_backend.cxx:676: unexpected RuntimeException "<class 'ImportError'>: type lightproof_impl_en.locales is unknown, traceback follows > lo/core/solver/unxlngx6/installation/opt/program/uno.py:303 in function _uno_import() [raise ImportError( "type "+ name + "." +x + " is unknown" )] > lo/core/solver/unxlngx6/installation/opt/share/extensions/dict-en/Lightproof.py:6 in function <module>() [from lightproof_impl_en import locales] > lo/core/solver/unxlngx6/installation/opt/program/pythonloader.py:100 in function getModuleFromUrl() [exec(codeobject, mod.__dict__)] > lo/core/solver/unxlngx6/installation/opt/program/pythonloader.py:146 in function writeRegistryInfo() [mod = self.getModuleFromUrl( locationUrl )] > > "
Added Laszlo Nemeth to CC list. AFAIK he has just started to work on LightProof Python 3 port.
(In reply to comment #3) > From an --enable-dbgutil installation's output below, it looks like a > problem related to the Python 3 switch to me. At least for my recent master and libreoffice-4-0 Linux builds, the --enable-dbgutil output is gone again and the bundled English spelling extension is listed as fully working in the Extension Manager, so it looks like Laszlo fixed that.
Sorry for my missing feedback. I have fixed the Python 3 related problems of the grammar checker component of the dictionary extension, but I tried to test, why is this component missing from the Options->Language Settings->Writing Aids -> Available language modules list in my build (maybe PyUNO hasn't had complete Python 3 port, yet). I will test it with a new build and report the problem, if it exists.
Well, I wanted to verify that this bug is fixed, but on Mac OS X (10.6.8), both * our official 4.0.0 beta 1 and * the last master build for Mac OS X: Version 4.1.0.0.alpha0+ (Build ID: e43d62fb39e0b6b3e59b22110460d23b6d507b5) TinderBox: MacOSX-Intel@1-built_no-moz_on_10.6.8, Branch:master, Time: 2012-12-06_09:19:57 still show the problem. I don’t know if this is important. Seems that I have to wait for a newer Master master build for Mac OS X. If the bug is still reproducible in a newer build, I should probably file a new bug report especially for the remaining problems on Mac OS X, shouldn’t I? @ Stephan Bergmann (or whoever knows about it ;-): Does LibreOffice 4.0 rely on the Python version installed on the system? Or does it include its own version of Python? I ask because Mac OS 10.6.8 includes only Python 2.6.1 (r261:67515, Jun 24 2010, 21:47:49); so, if this extension needs Python 3 and if it does not include its own Python, this would explain why the extension still fails to load on my machine ... Thank you for your help!
Hi Roman, I think, LibreOffice 4 and this bundled extension have to support Python 2.6, too.
Roman: It seems, I have found the bug behind the missing English grammar checking in LibreOffice 4 (invalid unicode and byte array operations) in pythonloader.py. I will push a patch afternoon.
@ László: Thank you very much for your continued investigation! I am looking forward to your patch ...
(In reply to comment #10) > @ László: > Thank you very much for your continued investigation! I am looking forward > to your patch ... Roman: thank you very much for your help! Unfortunately, I have found only a small porting problem in the inner DEBUG mode of the pythonloader. But I have made a new issue for the detected configuration problem of the dictionary extensions: see Bug 58503