Summary: | After pausing, waiting a while, then unpausing, no sound is output even though the progress slider resumes moving | ||
---|---|---|---|
Product: | [Applications] Elisa | Reporter: | Talya <myjunkmailbox2801> |
Component: | general | Assignee: | Matthieu Gallien <matthieu_gallien> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | dwt, john.kizer, kai-dev, nate |
Priority: | NOR | ||
Version First Reported In: | 25.04.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
URL: | https://bugreports.qt.io/browse/QTBUG-135851 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Talya
2025-04-27 09:32:49 UTC
I can confirm this bug. Pausing for more than roughly 10-15s causes it. Letting it "play" afterwards for some time can fix the issue after a few more seconds, but I encountered cases where it took longer than I was willing to wait/it switched to the next track first. The system journals do not contain any meaningful information besides the regular song metadata output in ffmpeg style. I first noticed the bug when updating from 24.12.3-1 to 25.04.0-1, but today it remains unfixed in 25.04.1-1 (newest release for my Fedora 42 stable). File/Stream/Decoder tested: FLAC, 44.1kHz *** This bug has been marked as a duplicate of bug 503408 *** I can reproduce on Fedora KDE 42 with Elisa built from today's git master. Thanks! okay so now that this bug is no longer considered duplicate, what further info is needed? Looking at this again and thinking about the upstream Qt source of that other bug report, I checked the Qt bug tracker again - and found that this one is actually an upstream issue in QtMultimedia as well: https://bugreports.qt.io/browse/QTBUG-135851 So, as a user I'd say the only additional thing you could do is to add any log outputs that might show something not seen before, or contribute any code ideas if you might have them :-) so did the bug just disappear or is it just my endpoint that's acting nice today? Yes, updating QtMultimedia from 6.9.1-1 to 6.9.2-1 resolves the issue. great! someone with a QT account should probably close the report on their end. |