Issue 64039 - Assertion "Fallback scenario for localized value failed ..." locks office
Summary: Assertion "Fallback scenario for localized value failed ..." locks office
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: OOo 2.0.3
Assignee: andreas.schluens
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-05 17:17 UTC by niklas.nebel
Modified: 2006-04-27 12:11 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description niklas.nebel 2006-04-05 17:17:00 UTC 
In m162 non-product, when a new document is created, there's an assertion
"Fallback scenario for localized value failed ..." from a background thread
(filter::config::LateInitThread). This conflicts with other background stuff
(SfxEventAsyncer_Impl) and locks the office completely, making non-pro versions
almost useless (you have to disable assertions to open a document).
Comment 1 andreas.schluens 2006-04-07 08:56:55 UTC 
The shown assertion is placed right here. Because it shows a real error. There is a 
new filter added some minors before, which uses a wrong configuration. But nobody 
recognized this error, because nobody before used a non pro version .-)

I've improved the assertion in a way, that it shows the name of the config item, which 
isnt configured right. The assertion itself wont be removed. Further I've changed the filter 
config of the problematic item writerglobal8_HTML.
Comment 2 andreas.schluens 2006-04-12 13:54:52 UTC 
.
Comment 3 andreas.schluens 2006-04-27 12:11:04 UTC 
fixed on master