Bug 403845 - Flatpak org.kde.Platform/x86_64/5.12 does not play audio from QML
Summary: Flatpak org.kde.Platform/x86_64/5.12 does not play audio from QML
Status: RESOLVED WORKSFORME
Alias: None
Product: flatpak-platform-plugin
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-01 21:49 UTC by Rinigus
Modified: 2019-02-23 17:41 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Rinigus 2019-02-01 21:49:37 UTC 
SUMMARY

I am developing an application that is using QML Audio for playing sounds. When compiled against org.kde.Platform/x86_64/5.11 into flatpak package, sounds play without any issues. With the upgrade to org.kde.Platform/x86_64/5.12, sound file does not play. 

While debugging, I can see that sound file is generated and set as a source to QML Audio. However, after a call to Audio play(), no sounds are produced. Also, while hooking to onPlaybackStateChanged of Audio, I see no changes in playback state. The corresponding changes are observed while sound is playing using 5.11 platform.

STEPS TO REPRODUCE
1. Install Pure Maps from Flathub
2. Go to Main menu/Preferences/Testing and hit Test

OBSERVED RESULT

No sound

EXPECTED RESULT

Test sentence pronounced


SOFTWARE/OS VERSIONS
Linux Gentoo, used through Flathub 
Qt Version: 5.12

ADDITIONAL INFORMATION

-
Comment 1 Rinigus 2019-02-19 10:07:41 UTC 
When testing against Qt 5.12 compiled on desktop, without flatpak layer, all works as expected. Here, I compiled Qt 5.12 from the source, installed all dependencies and run the application using Qt 5.12 libraries. 

So, it looks like something went wrong in flatpak platform, not in Qt 5.12 itself.
Comment 2 Rinigus 2019-02-22 06:45:29 UTC 
I have just updated the platform and now all works for me. Not sure what was changed, but this bug is not there anymore. I suggest to close it.
Comment 3 Patrick Silva 2019-02-23 17:41:06 UTC 
closing as per comment 2