Bug 47200 - Using Writer 3.5.0 I can't edit textframe content anymore
Summary: Using Writer 3.5.0 I can't edit textframe content anymore
Status: RESOLVED DUPLICATE of bug 43892
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-11 05:36 UTC by piedro
Modified: 2012-03-12 02:39 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

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

Note You need to log in before you can comment on or make changes to this bug.
Description piedro 2012-03-11 05:36:26 UTC 
When opening a valid textdocument (odt) that was edited with wirter 3.3 before without any problems a textframe containing the shipping address of my customers cannot be edited anymore. I tried removing any locking of postion, content and size - still i can change size and position but not the content. It's even impossible to mark the text with the mouse .... 

Thi9s is reproducible with every document i open. 


thx for reading, 
piedro
Comment 1 Rainer Bielefeld Retired 2012-03-11 22:32:35 UTC 
@piedro
Please attach a sample document and a document related step by step instruction how to reproduce the problem.
Is your problem the one described in "Bug 43892 - EDITING text frame: context can not be reached by mouse click"?
Comment 2 piedro 2012-03-12 01:16:00 UTC 
Yes! You are right! It is a duplicate to the mentioned bug. THough I don't use the beta. It's the final 3.5.0 on Kubuntu 64bit. 

By reading through the duplicate bug I've understood that it is easy to work around by selcting the frame and pressing "Enter" ... 

thx a lot! 

piedro
Comment 3 Rainer Bielefeld Retired 2012-03-12 02:39:43 UTC 
DUP for now!

@reporter:
Please feel free to reopen this Bug if you find evidence that we have an independent issue here.

*** This bug has been marked as a duplicate of bug 43892 ***