[Upstream] Writer Picture Background No Fill does not persist saving to .doc

[Yiannis Barbanas]

1) lsb_release -rd
Description: Ubuntu 11.10
Release: 11.10

2) apt-cache policy libreoffice-writer
libreoffice-writer:
  Installed: 1:3.4.3-3ubuntu2
  Candidate: 1:3.4.3-3ubuntu2
  Version table:
 *** 1:3.4.3-3ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages
        100 /var/lib/dpkg/status

3) What is expected to happen in LibreOffice Writer via the Terminal:

cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/873287/+attachment/2540085/+files/problematic%20document.doc -O inf.doc && lowriter -nologo inf.doc

select the picture at bottom right -> Format -> Picture -> Background tab -> No Fille -> OK -> Save as .doc -> Close -> Reopen and the No Fill persists.

4) What happens is it does not.

WORKAROUND: Save as .odt.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: libreoffice-core 1:3.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
Architecture: i386
Date: Thu Oct 13 15:05:06 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcEnviron:
 LANGUAGE=en_US:el:en
 LANG=el_GR.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

[penalvch (penalvch)]

Yiannis Barbanas, thank you for reporting this and helping make Ubuntu better. Could you please attach the document that when edited as described demonstrates this problem?

[penalvch (penalvch)]

Yiannis Barbanas, the issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at http://wiki.documentfoundation.org/BugReport . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[penalvch (penalvch)]

Downstream bug may be found at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/873287

1) lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

2) apt-cache policy libreoffice-writerlibreoffice-writer:
  Installed: 1:3.5.2-2ubuntu1
  Candidate: 1:3.5.2-2ubuntu1
  Version table:
 *** 1:3.5.2-2ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

3) What is expected to happen in LibreOffice Writer via the Terminal:

cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/873287/+attachment/2540085/+files/problematic%20document.doc -O inf.doc && lowriter -nologo inf.doc

select the picture at bottom right -> Format -> Picture -> Background tab -> No Fille -> OK -> Save as .doc -> Close -> Reopen and the No Fill persists.

4) What happens is it does not.

WORKAROUND: Save as .odt.

[penalvch (penalvch)]

Downstream bug may be found at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/873287

1) lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

2) apt-cache policy libreoffice-writerlibreoffice-writer:
  Installed: 1:3.5.2-2ubuntu1
  Candidate: 1:3.5.2-2ubuntu1
  Version table:
 *** 1:3.5.2-2ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

3) What is expected to happen in LibreOffice Writer via the Terminal:

cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/873287/+attachment/2540085/+files/problematic%20document.doc -O inf.doc && lowriter -nologo inf.doc

select the picture at bottom right -> Format -> Picture -> Background tab -> No Fille -> OK -> Save as .doc -> Close -> Reopen and the No Fill persists.

4) What happens is it does not.

WORKAROUND: Save as .odt.

[Mcavalleri91 (mcavalleri91)]

I can confirm this with LO 4.1.1. on Windows 7 SP1

[Mcavalleri91 (mcavalleri91)]

I can confirm this with LO 4.1.1. on Windows 7 SP1

[Mcavalleri91 (mcavalleri91)]

Notice: AOO 4.0 works correctly.

[Mcavalleri91 (mcavalleri91)]

Notice: AOO 4.0 works correctly.

[Beluga (beluga)]

Bug persists on Win 7 64-bit 4.3.2.2.

But on dev build there is no fill to begin with. Version: 4.4.0.0.alpha1+
Build ID: a8c24b25fd9fb21097a08a22797bf61b59099ea1
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-21_06:33:33

[Beluga (beluga)]

Bug persists on Win 7 64-bit 4.3.2.2.

But on dev build there is no fill to begin with. Version: 4.4.0.0.alpha1+
Build ID: a8c24b25fd9fb21097a08a22797bf61b59099ea1
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-21_06:33:33

[Yousuf 'Jay' Philips (philipz85)]

Confirmed in 3.3.0, 3.6.7, 4.3.

Version: 4.3.4.0.0+
Build ID: bea74d73f4782b17f5286327f15db60ab3ae85de
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:libreoffice-4-3, Time: 2014-10-15_05:34:17

[Yousuf 'Jay' Philips (philipz85)]

Confirmed in 3.3.0, 3.6.7, 4.3.

Version: 4.3.4.0.0+
Build ID: bea74d73f4782b17f5286327f15db60ab3ae85de
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:libreoffice-4-3, Time: 2014-10-15_05:34:17

[Yousuf 'Jay' Philips (philipz85)]

(In reply to todventtu from comment #3)
> Bug persists on Win 7 64-bit 4.3.2.2.
>
> But on dev build there is no fill to begin with. Version: 4.4.0.0.alpha1+
> Build ID: a8c24b25fd9fb21097a08a22797bf61b59099ea1
> TinderBox: Win-x86@39, Branch:master, Time: 2014-10-21_06:33:33

The bug of it opening in master with transparent fill is bug 85283.

[Yousuf 'Jay' Philips (philipz85)]

(In reply to todventtu from comment #3)
> Bug persists on Win 7 64-bit 4.3.2.2.
>
> But on dev build there is no fill to begin with. Version: 4.4.0.0.alpha1+
> Build ID: a8c24b25fd9fb21097a08a22797bf61b59099ea1
> TinderBox: Win-x86@39, Branch:master, Time: 2014-10-21_06:33:33

The bug of it opening in master with transparent fill is bug 85283.

[Qubit (qubit)]

Migrating Whiteboard tags to Keywords: (filter:doc)

[Qa-admin-q (qa-admin-q)]

** Please read this message in its entirety before responding **

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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

[Marcus Tomlinson (marcustomlinson)]

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

[Marcus Tomlinson (marcustomlinson)]

Synchronising bug status with upstream.

[Qa-admin-q (qa-admin-q)]

Dear Christopher M. Penalver,

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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

[Justin Luth (jluth)]

Fixed in LO 7.0 by commit 38e7e6f348df5d6b37d7e0051fd3b8c227db69e6
Author: Justin Luth on Tue Apr 14 17:39:36 2020 +0300

    tdf#132094 doc: fix export of fill in wrap-through fly frames

    This builds on commit 2f13dbac060ae6af7e25ad3eff675cc859cfb3ff
    by Miklos Vajna on Fri Jun 15 08:49:46 2012 +0100
        n#325936 fix ww8 export of fly frames with transparent bg
    where he wisely and cautiously says
        Regression from commit ed8b5f2d -- to be safe, reverted only
        for fly frames in headers.
    because for some unknown reason, way back in 2002, commit
    ed8b5f2debac216243930aba0873e0d75de8d0dd forced all
    frames to specify a background fill. Typically of
    course this is white, and so who notices?

    Well, you notice if your frame is transparent, and
    now the area fill hides something that it is over top of.
    Like for example a transparent image, where the text wraps
    through the image.

    At first I was going to just try and revert everything.
    Then I decided it likely was a difference between how
    LO and MSO handled stacking/overlapping things.
    After that, I was going to just make an exception for
    eShapeType == mso_sptPictureFrame, but that only seems
    necessary if there is something underneath. If the something
    is just a background, that is handled anyway, so really
    it would only be other shapes or (most importantly) text,
    so the safest thing is testing wrap through, which there was
    already a pre-defined variable to reuse
    (and fix the spelling).

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