Bug 124873 - Warning when LibreOffice starts. The slf4j class is missing.
Summary: Warning when LibreOffice starts. The slf4j class is missing.
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.2.2.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-21 23:57 UTC by gordon.lack
Modified: 2019-04-22 10:11 UTC (History)
1 user (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 gordon.lack 2019-04-21 23:57:46 UTC
Description:
When I start up LibreOffice this appears:

[parent]: libreoffice LeagueTables.odt 
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

Looking at that link it should be simple to avoid this, since:

"This warning message is reported when the org.slf4j.impl.StaticLoggerBinder class could not be loaded into memory. This happens when no appropriate SLF4J binding could be found on the class path. Placing one (and only one) of slf4j-nop.jar slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar on the class path should solve the problem. 

LibreOffice should ship with a slf4j-nop.jar in program/classes/.

Steps to Reproduce:
1. Stat LibreOffice in a terminal
2.
3.

Actual Results:
The warning message appears

Expected Results:
No warning message should appear.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Julien Nabet 2019-04-22 08:42:44 UTC
Just to be sure, you're on Android?
If yes which version do you use?
Comment 2 gordon.lack 2019-04-22 10:11:42 UTC
Sorry. Forgot to add that bit.

This is on Linux (Kubuntu 18.10).

However, I've just found out that this isn't LibreOffice itself reporting this.

My other system (with the same set-up) doesn't report this.

The issue is actually caused by the Language Tool extension. Oddly, slf4j-api-1.7.25.jar is present on both systems, and found on both systems when opening an *.odt file.

I'll close this and look more into what is going on...