On Sun, May 13, 2018 at 07:27:43PM +0200, c01d wrote: > Package: jabref > Version: 3.8.1+ds-3 > Severity: important > > Dear Maintainer, > > * What led up to the situation? > > Starting jabref. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > Starting jabref. > > * What was the outcome of this action? > > A lot of errors related to missing javafx. > > * What outcome did you expect instead? > > A running instance.
Hello c01d, Thank you for the bug report. It's not clear to me whether you are requesting an update to 4.2, in which case there is already an open bug regarding the upgrade [1] - and which is not trivial due to new reverse dependencies - or you are reporting a bug about the existing state of jabref with respect to openjdk-9 [2] or something else? The version you're reporting in stretch doesn't depend on javafx, so I'm not sure why you're seeing issues there. Are you perhaps trying to run a version from upstream and running into [3], the lack of openjfx in Debian starting with openjdk-9? I am able to start jabref from stretch (the version listed above) inside a clean stretch chroot without any problems, and there is nothing related to javafx installed. A stack trace of the javafx exception you're seeing would be helpful. Also, since it looks like your system is running testing, perhaps you could try installing the current version from testing/unstable, which 3.8.2+ds-3 [4]. Thank you, tony [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877718 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893138 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850921 [4] https://packages.debian.org/source/unstable/jabref
signature.asc
Description: PGP signature
