Bug 92692 - "W: Unknown node under /registry/extlang: deprecated W: Unknown node under /registry/grandfatered", when switching UI language
Summary: "W: Unknown node under /registry/extlang: deprecated W: Unknown node under /r...
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.0.0.2 rc
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-12 16:59 UTC by Thomas Hackert
Modified: 2017-07-02 07:08 UTC (History)
3 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 Thomas Hackert 2015-07-12 16:59:42 UTC
Hello @ll,
while triaging some of bugzilla's bugs, I discovered the following:

1. Start LO from command line
2. Go to "Tools – Options – Language Settings – Language"
You will now see
<quote>
W: Unknown node under /registry/extlang: deprecated
W: Unknown node under /registry/grandfathered: comments
W: Unknown node under /registry/grandfathered: comments
</quote>
on the command line.
3.. Close the Options dialogue and quit LO
Now you will see
<quote>
Usage information:
StartModule;.uno:OptionsTreeDialog;1
StartModule;.uno:Quit;1
Usage information end
thackert@morpheus:~$ LO/instdir/5000rc3/opt/libreoffice5.0/program/soffice
W: Unknown node under /registry/extlang: deprecated
W: Unknown node under /registry/grandfathered: comments
W: Unknown node under /registry/grandfathered: comments
Usage information:
StartModule;.uno:OptionsTreeDialog;1
StartModule;.uno:Quit;1
Usage information end
</quote>
there.

Not sure, if I have chosen the right component and severity. If not, feel free to change :)

OS: Debian Testing AMD64
LO: Version: 5.0.0.3
Build ID: f79b5ba13f5e6cbad23f8038060e556217e66632
Locale: de-DE (de_DE.UTF-8)
(parallel installed, following the instructions from https://wiki.documentfoundation.org/Installing_in_parallel/Linux, and with Germanophone lang- as well as helppack).

If you need any further information, feel free to ask :)
Thomas.
Comment 1 David Tardon 2015-07-13 08:05:12 UTC
These 'Unknown node' warnings come from liblangtag, not libreoffice itself. And they are harmless.
Comment 2 Nadav Har'El 2015-09-02 10:40:02 UTC
I also see the same problem when running Libreoffice on an existing document:

$ libreoffice --version
LibreOffice 4.4.5.2 40(Build:2)
$ libreoffice niqqudless.odt
W: Unknown node under /registry/extlang: deprecated
W: Unknown node under /registry/grandfathered: comments
W: Unknown node under /registry/grandfathered: comments

This might not be an urgent or important bug, but printing irrelevant and scary messages is definitely a bug... You're saying that "liblangtag" prints these messages; Is there a way libreoffice can force liblangtag not to print them? Can libreoffice do something different in the input it gives liblangtag? Can libreoffice avoid using liblangtag to avoid these messages? Doing one of these things will be more productive than closing this issue as "not a bug". Many users will likely be worried/suspicious after seeing these messages.
Comment 3 David Tardon 2015-09-07 10:36:39 UTC
(In reply to Nadav Har'El from comment #2)
> This might not be an urgent or important bug, but printing irrelevant and
> scary messages is definitely a bug...

But we are not the upstream of liblangtag. So it is irrelevant if printing these messages is a bug or not: it is not OUR bug.

> You're saying that "liblangtag" prints
> these messages; Is there a way libreoffice can force liblangtag not to print
> them?

Maybe. Disable all warnings in liblangtag (and there might be some that have actually some importance), if it is possible. Or patch these concrete ones out, but that only works with the bundled library.

> Can libreoffice do something different in the input it gives
> liblangtag?

This is not input from libreoffice. It comes from parsing liblangtag's own data file.

> Can libreoffice avoid using liblangtag to avoid these messages? Doing one of these things will be more productive than closing this issue as
> "not a bug".

Seriously? To stop using a library because it prints a harmless warning is "productive"? I am speechless.

> Many users will likely be worried/suspicious after seeing these messages.

IMHO users of this kind should not run libreoffice from command line.
Comment 4 Michael Stahl (allotropia) 2015-11-03 15:36:53 UTC
it looks like the upstream liblangtag bug tracker is here:

https://bitbucket.org/tagoh/liblangtag/issues

oh i've got an account there already...

filed this enhancement request:

https://bitbucket.org/tagoh/liblangtag/issues/14/need-more-control-over-error-warning
Comment 5 Thomas Hackert 2015-11-05 18:37:01 UTC
Hello Michael, *,

(In reply to Michael Stahl from comment #4)
> it looks like the upstream liblangtag bug tracker is here:
> 
> https://bitbucket.org/tagoh/liblangtag/issues
> 
> oh i've got an account there already...
> 
> filed this enhancement request:
> 
> https://bitbucket.org/tagoh/liblangtag/issues/14/need-more-control-over-
> error-warning

sorry for the relay, too less time at the moment to answer early ... :(
Thanks for reporting it upstream :) So this means, it is fixed upstream. I hope, I will see the fix in one of the next liblang versions in Debian ... ;)
Thanks again and have a nice evening
Thomas.
Comment 6 Eike Rathke 2015-11-10 18:31:36 UTC
FYI, liblangtag 0.5.8 handles these 'deprecated' and 'comments' elements and doesn't display the warning anymore. Upgraded internal liblangtag with https://gerrit.libreoffice.org/gitweb?p=core.git;a=commit;h=4b6e7da25f837349e10929b0258059398be8106d
Comment 7 aemm 2017-07-02 07:08:08 UTC
liblangtag 0.5.8 is still not be a part of Ubuntu LTS 16.04.02 repository. It seems its not yet stable enough... after 2 years... for a LTS...