jabref crashes on launch after liblog4j2-java upgrade from 2.8.2-2 to 2.10.0-1

Bug #1759872 reported by Liam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Jabref
Fix Released
Unknown
apache-log4j2 (Ubuntu)
Invalid
Undecided
Unassigned
jabref (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

JabRef crashes after upgrading liblog4j2-java upgrade from 2.8.2-2 to 2.10.0-1.

Downgrading liblog4j2-java 2.8.2-2 results in JabRef working again.

Please see upstream Debian bugs: 894106 and 893251.

Not sure if this bug should be filed against liblog4j2-java rather than jabref.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: jabref 3.8.2+ds-2
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 29 16:37:30 2018
InstallationDate: Installed on 2017-06-15 (287 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: jabref
UpgradeStatus: Upgraded to bionic on 2018-02-22 (35 days ago)

Revision history for this message
Liam (liam-smit) wrote :
Changed in jabref:
status: Unknown → Confirmed
Revision history for this message
Liam (liam-smit) wrote :

Upgrading to Jabref 4.1 works with the new version of log4J.

Jabref 4.1 works with openJDK 1.8 but not 1.9.

Changed in jabref:
status: Confirmed → Fix Released
Changed in jabref (Ubuntu):
status: New → Fix Released
affects: log4j → apache-log4j2 (Ubuntu)
Changed in apache-log4j2 (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.