Bug 73668 - text not rendered fully (cut off) when editing 90deg rotated rectangle
Summary: text not rendered fully (cut off) when editing 90deg rotated rectangle
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
(earliest affected) release
Hardware: Other All
: medium normal
Assignee: Not Assigned
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Shapes
  Show dependency treegraph
Reported: 2014-01-15 16:09 UTC by Michael Stahl (allotropia)
Modified: 2022-08-16 04:00 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Michael Stahl (allotropia) 2014-01-15 16:09:11 UTC
same as bug 72072 but in Draw

regression in first 4.1 release ( from:

commit 3137258e346a9c16b2e61747fd926a1e7d358d02
Author:     Armin Le Grand <alg@apache.org>
AuthorDate: Thu May 3 10:59:32 2012 +0000
Commit:     Caolán McNamara <caolanm@redhat.com>
CommitDate: Mon Mar 11 07:50:32 2013 +0000

    Resolves: #i118905# Changed EditEngine to be able to paint to overlay directly
    i.e. paint to VirtualDevice as well, not only to Window.
    Removed the no longer needed switch between buffered and unbuffered overlay,
    this removes the flickering white block.
Comment 1 Joel Madero 2015-01-05 17:18:50 UTC
Adding bibisected to whiteboard as bisected keyword is a subset of bibisected whiteboard.

Comment 2 Robinson Tryon (qubit) 2015-12-13 11:09:34 UTC Comment hidden (obsolete)
Comment 3 Xisco Faulí 2016-09-26 15:03:08 UTC
Adding Cc: to Armin Le Grand
Comment 4 QA Administrators 2018-07-02 02:36:29 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2020-08-15 04:25:34 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2022-08-16 04:00:30 UTC
Dear Michael Stahl (CIB),

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team