You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2014/02/27 01:03:38 UTC
[Bug 124323] New: Not operating spellchecker : installation repair
default
https://issues.apache.org/ooo/show_bug.cgi?id=124323
Bug ID: 124323
Issue Type: DEFECT
Summary: Not operating spellchecker : installation repair
default
Product: Writer
Version: 4.0.1
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: configuration
Assignee: issues@openoffice.apache.org
Reporter: bty-adminf1@trebly.net
CC: issues@openoffice.apache.org
Created attachment 82726
--> https://issues.apache.org/ooo/attachment.cgi?id=82726&action=edit
Error message file not found in add-extensions update
Hi,
The problem is completely identified and described.
Will be solved by a light check complement, but for the moment the lack leads
to a crash of ooe.
If the "dict411.oxt" installation had failed or if the directory svu2l6v.tmp_
had been destroyed accidentally, the repair installation will not repair this
then the following problem succeeds :
1- The orthography check for french don't functions even activated in a right
way (note that even well defined the "french" option is never checked into the
menu/tools/language/text, then it is impossible to imagine that the French
dictionnary is not well set)
2- If the user or admin tries to update the dictionary, then he will get the
error message (joined) : missing file .../dict411.oxt. The OK leads to a ooe
crash
The manual restoration of the file and subdir make a good reparation.
Nevertheless note that with this reparation the dictionary will not be
activated if a reset is not made manually with option language reset (click and
select French dictionary as it is the default).
It is not loaded at start, no search done : probably the fact that the
extension has not be found previously let it unactivated till the selection of
language generates the re-installation it (not visible into extensions list).
Needs :
- Show the language selected with "check" into main menu/tools/language, even
default
- After repair installation run, check the extensions (all of them) and
reinstall which ones are default or defined into extensions list (an extension
file could be destroyed)
- do not show into language value in current selected value of option...
language if the corresponding extension dictionary is not found
Best regards
Trebly
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 124323] CRASH if dictionary is damaged
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124323
--- Comment #2 from trebly <bt...@trebly.net> ---
Hi,
Ok.
These problems are linked.
when I was project manager, I use to have roblems formulation and a level to
treat the whole problem environment related to failure.
So I will create :
- Bug 1 : if default dict411.oxt has been damaged the try to update failure
(error management) must check the directory, create it if missin (as installer
does)reinstall the file from the original or from the ref site (as MS does in
his updates management), or define a kbnnnnn for repair by update as MS does.
Note about the reasons which lead to such situation :
- Disk failure, file cannot be repaired
- Trojan which damages user.dat and need to duplicate the user (without .dat)
and rebuilds .dat. The duplication can fail (the copy file of MS basic
- Cleaner which can not copy or suppress "tmp" dir and files.
- Various accidents which can alter files (any "try" to open a file file must
be supposed "not sure to be the good nor exist")
The optimization of the way to hold errors generated by default of access to
files is an important problem. The error handler must get each file open write,
by default stop the program with security with a unique basic message module.
When error are repeated for any reason the handler can be enhanced to repair
recommendations or sometimes automatic repair. This is the way, I used to
develop soft. This is not at all to tell you what you should do, but for you to
know how other works in the same conditions. This don't makes the soft so heavy
nor slower at all to execute (because there no check before opening just catch
errors)
- Bug 2 : As the French default dictionary is a part of the main install. The
repair mode should check all directory and file form a directory image and
rebuild. It does not. The fact that the default dictionary uses the extension
feature (as extensions) is completely different from extensions management, the
default dictionary is a basic feature, not installed as extension. Must be hold
as any basic function.
- Bug 3 : Auto check of extensions : each extension should have a check of
configuration function (integrity signature, developed by the author, quite the
same as install but keeping options if valid). Then for a suitable repair a
main function, which belongs to main installer (as for updater) should run
sequentially all these checks.
- Bug 4 : The current even default language should be shown in main
menu/language/ various (marked, paragraph, all text) which a check mark if set
- Bug 5 : In option/language the shown current value even value must correspond
to a checked and validated extension (dictionary) not only from parameters.
This avoid that a not validated extension should be displayed as set valid
while it is no more valid.
- Bug 6 : When option/java is activated an automatic search of java candidate
installation is ran. If just one is found it is checked by default, if several
the user (admin) will make the choice. The OK button doesn't make anything else
than close, it should run test java functioning normally. This would avoid that
user could think to have validated while in fact java launch fails.
- Bug 7 : When users defines java parameters, as this parameters are related to
the current valid java installation selection. The values should be checked
(valid content) and a launch of java with these parameters should be performed.
- Bug 8 - Doc : while these bug are not solved the doc which recommends to
update the dictionary should be modified, it is wrong : if dictionary is
damaged the action will crash ooe.
All this validates basic functions around five subjects :
- java installation
- default dictionary damaged repair
- repair mode for basic functions using ".oxt" function (not extensions for
user but using .oxt feature)
- repair mode for extension manager
- UI for current dictionary activation and validated
To list and defined then check and follow the linked elements which participate
to the same user and UI function is a development manager job.
Note : I communicate repeatedly about this problem with BugZilla and others
MantisBT about intercommunication of projects UI oriented and their elementary
split into components which are are supposed managed, but how. This is the same
with ECLIPSE which uses the same connectors to bugs managers, to group, connect
and follow simply with the minimum of efforts with crossed projects and
generate associated reports is and headache generator.
Best regards
Trebly
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Issue 124323] CRASH if dictionary is damaged
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124323
Rainer Bielefeld <ra...@bielefeldundbuss.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #3 from Rainer Bielefeld <ra...@bielefeldundbuss.de> ---
This one will never be fixed, multiple Bugs in 1 report, Unknown benefit from
some of the wishes ...
I added to my to-do list to check what of reported items should get a separate
report
--
You are receiving this mail because:
You are on the CC list for the issue.
You are the assignee for the issue.
You are watching all issue changes.
[Issue 124323] CRASH if dictionary is damaged
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124323
Edwin Sharp <el...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needmoreinfo |needhelp
CC| |elish@apache.org
--
You are receiving this mail because:
You are on the CC list for the issue.
You are the assignee for the issue.
You are watching all issue changes.
[Issue 124323] CRASH if dictionary is damaged
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124323
Rainer Bielefeld <ra...@bielefeldundbuss.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|rainerbielefeld_ooo_qa@biel |
|efeldundbuss.de |
--
You are receiving this mail because:
You are on the CC list for the issue.
You are the assignee for the issue.
You are watching all issue changes.
[Bug 124323] Not operating spellchecker : installation repair
default
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124323
trebly <bt...@trebly.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest|--- |4.0.1
Confirmation on| |
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 124323] CRASH if dictionary is damaged
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124323
Rainer Bielefeld <ra...@bielefeldundbuss.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needmoreinfo
CC| |rainerbielefeld_ooo_qa@biel
| |efeldundbuss.de
Summary|Not operating spellchecker |CRASH if dictionary is
|: installation repair |damaged
|default |
Severity|critical |normal
--- Comment #1 from Rainer Bielefeld <ra...@bielefeldundbuss.de> ---
I doubt that it can be expected that OS (WIN7?) repair installation (Start ->
System settings -> Software -> AOO - Repair' also will repair Extensions.
@trebly:
Wen can't handle such "so many problems with ... " bug reports [1]
Let's limit this one to the CRASH problem. Please contribute a clear and simple
step by step instruction how to damage a Server Installation [2] with it's own
separate user profile [3] so that the crash will happen.
Other problems you observed we can handle in separate bug reports later.
Used Hyperlinks:
[1]
<http://www.openoffice.org/qa/issue_handling/basic_rules.html#one_per_issue>
[2] <https://wiki.openoffice.org/wiki/Run_OOo_versions_parallel>
[3]
<https://wiki.openoffice.org/wiki/Documentation/How_Tos/Handling_the_OpenOffice.org_User_Profile>
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Issue 124323] CRASH if dictionary is damaged
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124323
--- Comment #4 from trebly <bt...@trebly.net> ---
Hi,
I have enumerated detailed problems as named "bugs".
I am completely conscious that is impossible to "attack" such problems using
the concept "1 bug = (1 action and 1 project)".
For development I commonly was using this way :
[1 bug (or bad featured)] <-> [1 request] <-> [<one or several functions and
pieces of soft involved>] <-> [n - actions (todo)] <-> [current projects]
it is a problem of structure of database for development management, I explain
:
It is not economically possible to do each job individually, but if the problem
is known what we have (always) to do is to manage soft components structure,
the list of bugs+bad_featured+enhancements, the list of decided projects.
With these tables (common in project management) we can manage the links
between the 3 structures.
Then each time a project is launched it is easy to get the
"bugs+bad_featured+enhancements" that are linked and to decide to treat someone
for a very low-cost because it become just a little element of an upgrade
process.
What I see as priorities :
1- For each options changes which involves JAVA / run when OK is hitten an
little sequence (as the one is run for search in help) which will crash if Java
is not running well and send an ALERT message "JAVA is not running Well on the
system".
2- For "Repair installation" be carefull to check the existency of each
directory (use always try and error exception catch -> (re)create it and fill).
This can be easily done for the case that I found, and later for all concerned
directory of a module which must be upgraded for another reason.
So my global answer is :
- most of should be fixed (which one and which content) but cannot be treated
as "punctual action" which would be too expensive.
- each element of "fix-code" (which is into various places of the whole soft)
can be (which ones and with coherent specifications) integrated in "todo" list
associated to various projects
- all choosen as useful will be cleaned progressively for the next years
- there is no change for solving bug linked to the "bugs" that are in my list
which leads to a coherent and unique main development. So it can be a long term
progressive action.
The tools and the way to solve which is involved, used, to manage this type of
problems are not well adapted. For my own I uses a database described for a
part at the beginning of this message.
Best regards
trebly
--
You are receiving this mail because:
You are on the CC list for the issue.
You are the assignee for the issue.
You are watching all issue changes.
[Bug 124323] Not operating spellchecker : installation repair
default
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=124323
trebly <bt...@trebly.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bty-adminf1@trebly.net
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.