On Thu, 23 May 2019 23:10:47 +0200 Matthias Seidel <matthias.sei...@hamburg.de> wrote:
> Hi Rory, > > Am 23.05.19 um 10:24 schrieb Rory O'Farrell: > > I am using AOO 4.2.0 Rev 1859149 2019-05-12_15:10:46 Rev 1859151, running > > in Xubuntu 18.04.2 (latest updates) > > > > When I start openoffice4 in a terminal, opening a blank Writer file gives: > > > > 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. > > How exactly do you start AOO from terminal? > I cannot reproduce this output on my Xubuntu 18.04.2 with > AOO420m2(Build:9821) - Rev. 1859149 2019-05-12_15:10:46 - Rev. 1859151 > (German version). > > Do you have any extensions installed? > > Regards, > > Matthias In a terminal I type "openoffice4" (no quotes). I get the main screen to select the various OO components, and when I select Writer I get the SLF4J messages I quoted. I do not get the messages with other OO components. The "error" does not interfere with writing/editing. Extensions I have installed are Alternative searching 1.4.2 Basic IDE tools 1.3.0 Bookmarks menu 1.0.15 Bookmarks Menu extension 0.6.2 Cross Reference manager 4.0.0 Dictionnaires francais 5.3 English Spelling and Hyphenation dictionaries and thesaurus 2019.05.01 LanguageTool 4.5.1 MRI - UNO Object Inspection Tool 1.3.4 Oracle Report Builder 1.2.1 Test of missing font 1.4.5 TimeStampBackup 1.1.8 VisibleBookmarks 1.2.7 Word Count StatusBar Control 0.0.2 Writer's Tools 1.9.1 Zotero LibreOffice Integration 5.0.14 Some of these were installed to obtain printouts of their code, and are not actually needed for my daily work. If I have time tomorrow I'll try a clean install on a spare computer with no extensions of version 1859756 2019-05-22 Rory. e > > > > > > > The url in the error message tells: > > > > Failed to load class org.slf4j.impl.StaticLoggerBinder > > 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. > > > > SINCE 1.6.0 As of SLF4J version 1.6, in the absence of a binding, SLF4J > > will default to a no-operation (NOP) logger implementation. > > > > If you are responsible for packaging an application and do not care about > > logging, then placing slf4j-nop.jar on the class path of your application > > will get rid of this warning message. Note that embedded components such as > > libraries or frameworks should not declare a dependency on any SLF4J > > binding but only depend on slf4j-api. When a library declares a > > compile-time dependency on a SLF4J binding, it imposes that binding on the > > end-user, thus negating SLF4J's purpose. > > > > ------------- > > > > I should say that version works OK for large text editing (70k words) and > > preparation of Impress presentations (100 slides, containing approx 200 > > illustrations, from which custom slideshow of about 60 slides will be > > selected). > > > > > -- Rory O'Farrell <ofarr...@iol.ie> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
