Issue 118705 - Adding an unordered list results in crash
Summary: Adding an unordered list results in crash
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOo 3.3
Hardware: All All
: P2 Major (vote)
Target Milestone: ---
Assignee: writerneedsconfirm
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-29 19:08 UTC by tommyads
Modified: 2012-01-02 08:32 UTC (History)
3 users (show)

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

Attachments
sample text. editing as described in the bug-report results in crash. (14.17 KB, application/vnd.oasis.opendocument.text)
2011-12-29 19:08 UTC, tommyads 		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 tommyads 2011-12-29 19:08:17 UTC 
Created attachment 77093 [details]
sample text. editing as described in the bug-report results in crash.

See attachment. Open it with writer, Version 330m20. Go to the end of the document, and klick on the button for starting an unordered list (Aufzählungsliste an/aus, Shift+F12) => then writer crashes!!!
I tried this for 3-4 times, always resulting in a crash.
Comment 1 Marcus 2011-12-29 19:42:48 UTC 
I can confirm the crash also on Linux with version OOO330m20.
Comment 2 Marcus 2011-12-29 19:44:06 UTC 
cannot reproduce the issue with your steps
Comment 3 Marcus 2011-12-29 20:09:41 UTC 
please ignore my last comment, mixed-up with another issue, sorry
Comment 4 Ariel Constenla-Haile 2011-12-29 21:19:36 UTC 
I can't reproduce it with 3.4.0 (latest nightly build from http://ci.apache.org/projects/openoffice/install )
Can anyone else try?
Comment 5 Oliver-Rainer Wittmann 2012-01-02 08:25:52 UTC 
I can not reproduce the crash with
- OOo 3.4 Beta
- my local developer build from 2011-12-22 of AOO

--> close issue as fixed in next release
Comment 6 Oliver-Rainer Wittmann 2012-01-02 08:32:32 UTC 
closing issue as it can not be reproduced in recent builds.

feel free to reopen it, if the crash can be reproduce in recent builds.