Created attachment 60644 [details]
After installing any of recent LO versions, both Russian and English bundled dictionaries are shown as 'broken' in Extension Manager.
Please check if this bug is reproducible with the latest stable release on clean install.
Changed status to NEEDINFO.
In 3.6 they show no error message, but all their Options pages are empty.
Have you tried to remove the directory 'extensions' in your LibreOffice user profile (%appdata%\LibreOffice\3\user\extensions)?
Then restart LibO 184.108.40.206.
See 'Bug 53006 - Autocorrection TWo INitial CApitals does not work because of bundled extensions problem'.
Created attachment 65479 [details]
3.6 screenshot [EN dict]
Created attachment 65483 [details]
My result (all dictionaries installed):
Screenshot of bundled 'dict-ru' (+ Options) with LibO 220.127.116.11 (on WinXP 32b).
It seems you have replaced the original bundled 'dict-ru' (2011.01.29) with another version (2011.12.05)?
No, that is a dictionary from the package.
Created attachment 65489 [details]
Sorry, my mistake — my ignorance in Cyrillic.
Your screenshot shows the *English* dictionaries.
Well, 'dict-en' (+ Options) works fine for me, too.
How to reproduce your problem?
Does this problem arise with a brand new LibreOffice default user profile?
Yes, it does.
To reproduce it, install LO 3.5/3.6, start any application and open Extension manager. You may remove user profile data, the program files data, it will be the same.
(In reply to comment #12)
> To reproduce it, install LO 3.5/3.6, start any application and open Extension
> manager. You may remove user profile data, the program files data, it will be
> the same.
Installation LibO 18.104.22.168, LibreOffice default user profile:
- I have started swriter.exe.
- I have set the language of UI to Russian.
- I have removed the directory 'extensions' in my LibreOffice user
profile (%appdata%\LibreOffice\3\user\extensions) to recreate the cache of the (bundled) extensions.
- Then I have restarted LibO 22.214.171.124.
The screenshot 'ui-ru_extmgr_dict-en_options_lo-126.96.36.199.png' shows my result (works for me).
Best would be to test again with LibO 188.8.131.52 – where bug 53006 has been fixed.
See → https://wiki.documentfoundation.org/index.php?title=ReleaseNotes/3.6#Most_annoying_bugs :
"[...] Missing dictionary options pages (in “Tools - Extension Manager...”, selecting a bundled dictionary extension like “English spelling dictionaries, hyphenation rules, thesaurus, and grammar checker” does not display an “Options...” button). [...]"
Created attachment 65550 [details]
Created attachment 65595 [details]
I'm not buying it. This is how it appears on FRESH installation with VIRGIN user profiles. Other UI language. Other OS. Same issue.
(In reply to comment #15)
> I'm not buying it. This is how it appears on FRESH installation with VIRGIN
> user profiles. Other UI language. Other OS. Same issue.
Could you try http://wiki.documentfoundation.org/Installing_in_parallel and comment?
Running from administrative install folder: works.
After Installation and launch: same result.
So you may need to fix that lolinstaller of yours.
Hm, currently it seems only Urmas suffers from this problem, or did I miss something?
I can't remember tho have seen any broken dictionaries.
I found some other similar bugs without mandatory relation to this bug:
"Bug 37561 - Failed installing extension: Duden-Korrektor 5.0/6.0"
"Bug 43707 - FILEOPEN PDF brings up (ASCII) filter selector instead of opening document"
Searching Mailing lists with Google also shows many results, but none of them really matches with Urmas' result.
@Urmas: Translated error message also is "Status of this extension is unknown" in " 3.6 screenshot [EN dict] "?
I wonder what difference between Server installation and normal installation might cause this difference
Yes, it does, as it does in each version since 3.5.something.
Still exist in 184.108.40.206.
Updated from 3.5.5 (dictionaries were fine) to 3.6.0 and got broken dictionaries again... They display in Extension manager, but not in Language settings...
As far as I can remember this was happening every time I upgrade LO from one version to another... The only thing that fixed it for me was total deinstallation, deletion of the LibreOffice folders in AppData and Program Files and subsequent clean install...
Windows 7 x64
Only these 2 dictionaries are affected since 3.5, so please take that 'broken user profile' crap out of my bug.
What is the difference between Russian, English dictionaries and every other one?
(In reply to comment #23)
> What is the difference between Russian, English dictionaries and every other
For example, both have grammar checker (ligtproof).
In my version 3.6.1, I also get "Status of this extension is unknown" for the bundled English spelling... grammar extension. However, spelling checking, thesaurus amd hyphenation actually works fine. They show up in the Writing Aids box. It's only Lightproof grammar that is neither showing up as installed nor working.
I've earlier had the problem of spelling not working. Removing the extension folder so that EibO can regenerate them solved it. (I've to do it for every installation since then.) However for this version, this workaround doesn't bring grammar checker back to life.
I have to reiterate: Why does the Grammar checker works from raw LO installsource, but not from the installed instance? How does your installer manage to fuck up the installation so?
I seem to have the same problem in LibreOffice 220.127.116.11
That is ridiculous. THE SAME problem is STILL present in 18.104.22.168 and affect now Brazilian dictionary too!
(In reply to comment #28)
> That is ridiculous. THE SAME problem is STILL present in 22.214.171.124 and affect
> now Brazilian dictionary too!
Urmas, to help track down your problem, can you do the following:
* Generate a zip file (the original zip format, <http://en.wikipedia.org/wiki/Zip_%28file_format%29>, /not/ something like 7-Zip etc.) containing all the (recursive) content of your LO installation's share/extensions/dict-en/ (but not containing dict-en as a root directory itself), save that zip file as "C:\test.oxt".
* Completely remove your LO installation's share/extensions/ folder (or move it away, to restore it later).
* Completely remove any existing LO/OOo user profiles (or move them away, to restore them later).
* Open and close soffice once (you could check that "Tools - Extension Manager..." shows no extensions at all, neither "Installation" nor "Shared" nor "User" ones).
* On a command line, change to your LO installation's program/ directory, then execute "unopkg add C:\test.oxt". Does that generate any output? If not, what is the output of "unopkg list"?
Created attachment 73175 [details]
Yes, there is output:
ERROR: Binary URP bridge disposed during call
Unlike the bundled one, this extension has "Enable" button in the list, having the same URP bridge message during activation, and consequently doesn't function at all.
> URL: vnd.sun.star.expand:$UNO_USER_PACKAGES_CACHE/uno_packages/lu46afs0.tmp_/dict-en-standalone.oxt/Lightproof.py
> is registered: no
It appears that for some reason the active UNO component registration of the Python Lightproof.py, offloaded from unopkg to a uno.exe it spawns, crashes the uno.exe. To find out more, it might help to run soffice from within Dependency Walker. To do so, do the first four steps from comment 29, and instead of the last step ("unopkg add") do the following:
* Start soffice from within Dependency Walker, see comment 28 of bug 51252 for details. Add C:\test.oxt via "Tools - Extension Manager... - Add...". Within Dependency Walker there should now be a window for the spawned uno.exe sub-process (among windows for any other spawned sub-processes), please copy all the output from the bottom frame of that window.
Created attachment 73186 [details]
So the problematic line is
> LoadLibraryExW("C:\Program Files\LibreOffice 4.0\program\..\program\pythonloader.uno.dll", 0x00000000, LOAD_WITH_ALTERED_SEARCH_PATH) returned NULL by thread 5. Error: (126).
No idea how that can happen for you. What version of Windows is that? You start LO as soffice.exe, not soffice.bin, right? What is your PATH environment variable?
(In reply to comment #33)
> No idea how that can happen for you.
The easiest idea might be that you did a custom installation of LO and disabled the "Python-UNO Bridge" optional component. -- Did you?
If you mean "Python-UNO bindings: Enables automation in LibreOffice through a Python language" component, it is uninstalled as I have no use of automation of any kind and there is no any hint in installer that it is required for spelling checker.
So either fix the dependencies or use truthful descriptions in installer. Having useful error messages is also nice.
(But of course support for Firefox toolbar pictures is the top-priority instead.)
@atimar: I wonder if it would be best to always install the "Python-UNO Bridge" component on Windows unconditionally?
(In reply to comment #36)
> @atimar: I wonder if it would be best to always install the "Python-UNO
> Bridge" component on Windows unconditionally?
Yes, I agree. We have too many install options.
Andras Timar committed a patch related to this issue.
It has been pushed to "master":
fdo#49202 install the "Python-UNO Bridge" component on Windows unconditionally
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.