Bug 124699 - Configuring with --disable-report-builder causes warnings about registry when LO starts
Summary: Configuring with --disable-report-builder causes warnings about registry when...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Dev-related
  Show dependency treegraph
 
Reported: 2019-04-12 08:55 UTC by How can I remove my account?
Modified: 2023-08-10 03:05 UTC (History)
0 users

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 How can I remove my account? 2019-04-12 08:55:43 UTC
Description:
Just our of laziness, and to perhaps make my build a bit faster, I tend to use --disable-report-builder on Linux (even if I don't use --without-java).

This apparently leads to a lot of warnings when I start LibreOffice, like:

> warn:configmgr:15052:5622621:configmgr/source/xcuparser.cxx:908: ignoring modify of unknown set member node "StarOffice XML (Base) Report" in "file:///Users/tml/lo/osx/instdir/LibreOfficeDev.app/Contents/Resources/../Resources/registry/res/fcfg_langpack_en-US.xcd"

and

> warn:configmgr:21616:21616:configmgr/source/xcuparser.cxx:908: ignoring modify of unknown set member node "SunReportBuilder" in "file:///ssd1/lo/fedora/instdir/p\
rogram/../share/registry/res/registry_sv.xcd"

I spent five minutes on pondering whether we ould just get rid of the --disable-report-builder option and couple building the report builder to building with Java, but nah, apparently it needs to be a separate choice.

Steps to Reproduce:
.

Actual Results:
.

Expected Results:
.


Reproducible: Always


User Profile Reset: No



Additional Info:
.
Comment 1 How can I remove my account? 2019-04-12 08:57:15 UTC
The same warnings also show up when building --without-java but not mentioning --disable-report-builder.
Comment 2 QA Administrators 2023-08-10 03:05:33 UTC
Dear Tor Lillqvist,

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

MassPing-UntouchedBug