Bug 426356

Summary:	Poor video performance in Flatpak images
Product:	[Applications] digikam	Reporter:	jgoerzen
Component:	Bundle-FlatPak	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	metzpinguin
Priority:	NOR
Version First Reported In:	7.0.0
Target Milestone:	---
Platform:	Flatpak
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	7.2.0
Sentry Crash Report:

Description jgoerzen 2020-09-10 00:11:50 UTC

Hi,

I am running the latest Flatpak digikam, which identifies with version 7.0.0-rc in Flatpak, and in Help->About as 7.0.0 with a build date of Sept. 7, 2020.  (Not sure why 7.0.0 release or 7.1.0 isn't in flatpak).

Anyhow, I have a Pixel 2 XL and a Pixel 4a.  Both can capture 4K video with H.264.  This video plays back fine in my Debian buster system using VLC.  My bideo card is an nVidia GTX 1070.  I am using the Nouveau open-source nvidia drivers.  When playing on the host system with vlc, vlc comments "Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so".    This also worked fine on the older version of Digikam included in buster.

Since I have upgraded to the digikam flatpak, however, this 4K video cannot play smoothly.  There is significant skipping and jumping in the video playback.

The nouveau_drv_video.so file used by vlc is in the Debian package mesa-va-drivers.

I don't know if a missing nouveau_drv_video.so is the cause of this problem, but it might be a reasonable place to start.



SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Debian buster
(available in About System)
KDE Plasma Version: n/a
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION

Comment 1 Maik Qualmann 2020-09-10 05:48:38 UTC


*** This bug has been marked as a duplicate of bug 382582 ***

Comment 2 jgoerzen 2020-09-11 03:15:59 UTC

You folks are the experts, but just FYI: It's possible that it's a duplicate of #382582, but as Digikam standalone was working fine, I'm less than 100% convinced.

Comment 3 jgoerzen 2020-09-15 13:40:35 UTC

For future travelers: conversation moved to https://github.com/flathub/org.kde.digikam/issues/11 where a workaround has been identified.