Ubuntu
mediathekview package

start not possible, opfenjfx missing but is installed

Bug #1876662 reported by LAZA on 2020-05-04

This bug report is a duplicate of: Bug #1853366: mediathekview 13.0.6-1 does not support openjfx 11. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	mediathekview (Ubuntu)	New	Undecided	Unassigned

Bug Description

$ mediathekview
===========================================
JavaFX wurde nicht im klassenpfad gefunden.
Stellen Sie sicher, dass Sie ein Java JRE ab Version 8 benutzen.
Falls Sie Linux nutzen, installieren Sie das openjfx-Paket ihres Package-Managers,
oder nutzen Sie eine eigene JRE-Installation.
===========================================

openjfx 11.0.2 is installed
opdenjdk-11-jre-headless 11.0.7 is installed

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mediathekview 13.0.6-1
ProcVersionSignature: Ubuntu 4.15.0-1080.90-oem 4.15.18
Uname: Linux 4.15.0-1080-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Mon May 4 08:07:03 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-kbl+X28
InstallationDate: Installed on 2019-10-04 (212 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38
PackageArchitecture: all
SourcePackage: mediathekview
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

LAZA (laza74) wrote on 2020-05-04:

Dependencies.txt Edit (14.4 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (312 bytes, text/plain; charset="utf-8")

Revision history for this message

Juhani Numminen (jsonic) wrote on 2020-05-04:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #1853366, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.