Issue 113929 - OOo crash when change form control anchor to "as character"
Summary: OOo crash when change form control anchor to "as character"
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO330m4
Hardware: Unknown Windows 7
: P3 Trivial (vote)
Target Milestone: OOo 3.3
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords: oooqa, regression
Depends on:
Blocks: 111112
  Show dependency tree
 
Reported: 2010-08-17 09:22 UTC by r4zoli
Modified: 2010-08-27 12:04 UTC (History)
1 user (show)

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

Attachments
bugdoc (57.10 KB, application/vnd.sun.xml.base)
2010-08-17 09:25 UTC, r4zoli 		no flags Details
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 r4zoli 2010-08-17 09:22:56 UTC 
OOo crash when change form control anchor to "as character".
- open attached odb file
- open form in edit mode
- select a form control, for example the navigation bar
- set anchor "as charater", OOo crash

This not happens in OOo 3.2.1, seems to me as regression.
Comment 1 r4zoli 2010-08-17 09:25:43 UTC 
Created attachment 71138 [details]
bugdoc
Comment 2 r4zoli 2010-08-17 09:27:52 UTC 
assign developer, set target.
Comment 3 Frank Schönheit 2010-08-17 09:58:11 UTC 
fs->Zoltan: care to raise this in releases@ooo?
Comment 4 r4zoli 2010-08-17 10:06:41 UTC 
Done.
Comment 5 Frank Schönheit 2010-08-26 14:31:05 UTC 
cannot reproduce - neither in OOO330.m4 nor in OOO330.m5

fs->msc: Do you have more luck with reproducing this?
Comment 6 r4zoli 2010-08-26 17:19:38 UTC 
I now tested on OOO330m5 and no crash.

Some changes it seems to solved in some way, the OOO330m3 still crashing.
Comment 7 Frank Schönheit 2010-08-27 08:29:27 UTC 
While it is strange that I cannot reproduce this - since you also fail to
reproduce it in m5, can we close the issue?
Comment 8 r4zoli 2010-08-27 12:03:42 UTC 
I think we could close as works for me.
If later happens again I will reopen issue.
Comment 9 r4zoli 2010-08-27 12:04:25 UTC 
Worksforme->Closing.