Download it now!
Bug 120718 - Legacy background extension does not work
Summary: Legacy background extension does not work
Status: REOPENED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Extensions (show other bugs)
Version:
(earliest affected)
5.4.0.0.alpha1+
Hardware: All All
: medium normal
Assignee: Heiko Tietze
URL:
Whiteboard:
Keywords:
: 125601 (view as bug list)
Depends on: 125521
Blocks:
  Show dependency treegraph
 
Reported: 2018-10-20 04:49 UTC by Franklin Weng
Modified: 2019-06-04 10:29 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Franklin Weng 2018-10-20 04:49:10 UTC
Description:
In the 6.1 release notes:
Background images in Gallery and Area Fill dialog completely reworked tdf#114817 (Andreas Kainz, Heiko Tietze)

New Areafill backgrounds
This change breaks documents with relative links to the gallery, which was possible some time ago. Affected users can install the legacy background images per extension (https://extensions.libreoffice.org/extensions/legacy-gallery-backgrounds).

However after installing the legacy-gallery-backgrounds, it showed the "background" catalog in the gallery but doesn't work.  No matter drag-and-drop, copy-and-paste, no images will be inserted in the main area.

Steps to Reproduce:
1. Install Legacy gallery Backgrounds extension in version 6.1
2. Open Draw or Impress and click "gallery" in the side bar
3. choose "background" and try to add a background image into the main part

Actual Results:
It could not insert the background image into the main part

Expected Results:
It should work


Reproducible: Always


User Profile Reset: No



Additional Info:
This bug is reported by a user in Taiwan.  I've told him to use Areafill feature instead.  However I've also confirmed that the extension does not work.
Comment 1 Franklin Weng 2018-10-20 04:49:43 UTC
Reported by user in Taiwan.  Confirmed by me.

Original report: https://ask.libreoffice.org/zh-tw/question/169263/61ban-hua-lang-backgroundsgong-neng-cuo-wu-xun-xi/
Comment 2 Xisco Faulí 2018-10-23 10:27:58 UTC
it seems to be an older problem.
I can also reproduce it in

Version: 5.4.0.0.alpha1+
Build ID: 9feb7f7039a3b59974cbf266922177e961a52dd1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

but not in

Version: 5.3.0.0.alpha1+
Build ID: 4136757b4e51c4e6f7cb4132c95538a7f831ef2c
CPU Threads: 4; OS Version: Linux 4.15; UI Render: default; VCL: gtk3; Layout Engine: new; 
Locale: en-US (ca_ES.UTF-8); Calc: group
Comment 3 Xisco Faulí 2018-10-23 10:41:09 UTC
So it seems on Linux it stopped working somewhere in version 5.4 while on Window it stopped working later, in version 6.1, most likely related to the image handling refactoring...
Comment 4 Xisco Faulí 2018-10-23 10:59:18 UTC Comment hidden (obsolete)
Comment 5 Xisco Faulí 2018-10-23 11:07:27 UTC
@Andreas, @Heiko, forgot about my analysis in comment 4, it's completely wrong...
Comment 6 Xisco Faulí 2018-10-23 11:14:27 UTC
So, an open question, has it even worked on windows?

I can reproduce the problem back to 

Version: 5.2.0.0.alpha1+
Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e
CPU Threads: 16; OS Version: Windows 6.29; UI Render: default; 
Locale: en-GB (en_GB)

I think the extension is just wrong. It doesn't work on Win and it stopped working on Linux in LibreOffice 5.4... would be nice to know who the author is...
Comment 7 Heiko Tietze 2018-10-24 10:37:41 UTC
Will check this
Comment 8 Heiko Tietze 2018-11-09 12:59:46 UTC
I updated the extension to v1.1 and it should work well now with all current versions.
Comment 9 Heiko Tietze 2019-05-27 11:32:15 UTC
Issue is back (https://design.blog.documentfoundation.org/2018/08/08/whats-new-in-libreoffice-6-1/#comment-13861). Both available versions of the extension do not work with LibO 6.1.6.3 nor 6.2.4.2.
Comment 10 Volga 2019-06-02 09:45:29 UTC
See: bug 125601
Comment 11 Xisco Faulí 2019-06-04 10:29:44 UTC
*** Bug 125601 has been marked as a duplicate of this bug. ***