When you add an audio file in editor mode the absolute path of the file is shown and you can play the audio file. When the vocabulary file is saved the absolute path of the audio is converted to a relative which is the expected behaviour. But when the vocabulary file is loaded the relative path is not handled correctly and the audio file can't be played. When clicking the play button following error message is on the console: GStreamer; Unable to pause - "file:Assets/au02834218_ew_0001.mp3" GStreamer; Unable to pause - "file:Assets/au02834218_ew_0001.mp3" Error: "Could not open resource for reading." Parley Version 2.1.0
I found this change which might be related https://git.reviewboard.kde.org/r/129992/diff/3/
The bug is already mentioned here: https://mail.kde.org/pipermail/kde-edu/2017-March/013344.html
Is your Parley version from the KDE Applications 17.04 package? You could check Dolphin version number, but applications do not need to come from the same package.
Yes 17.04 package. From Neon user packages.
Created attachment 107232 [details] fixes relative paths handling in reader if (QUrl::fromLocalFile(currentElement.text()).isRelative()) ... did not work because the url has a scheme and a scheme means it's not relative. My knowledge of Qt is veeeery limited, so I hope the patch makes sense.
added patch to review board https://git.reviewboard.kde.org/r/130224/
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!