Bug 362468

Summary:	With Gstreamer backend, playback stops when encountering broken or missing files
Product:	[Unmaintained] phonon-backend-gstreamer	Reporter:	tamius.han
Component:	general	Assignee:	Daniel Vrátil <dvratil>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	matej, myriam, romain.perier, sitter, tdfischer
Priority:	NOR	Keywords:	triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description tamius.han 2016-04-29 10:52:29 UTC

If the next song on my playlist is a broken or a missing file, Amarok will stop playing music. Most of the time, this issue is often resolved by skipping to the next song, though sometimes Amarok will just hang and freeze when that happens.

This only happens when using Gstreamer backend. (Phonon-VLC doesn't have this problem, but it also doesn't have ReplayGain so ...)

Reproducible: Always

Steps to Reproduce:
1.a) delete a file that's on the playlist
1.b) Rename a random non-mp3 file to .mp3 (to simulate a broken mp3 file) and put it on the playlist

Actual Results:  
When Amarok attempts to play a broken or a missing file, it stops playing music.

Expected Results:  
Amarok should skip the broken/missing files like it does with Phonon-VLC.

Comment 1 Myriam Schweingruber 2016-04-29 16:56:20 UTC

Please report backend related issues to the backend, since this is not an Amarok problem, but a backend one. The mere fact it is not reproducible with the vlc backend should have given the hint where the problem is ...
Now which exact phonon-backend-gstreamer versions is this about? I strongly suspect this is already reported, though

Comment 2 tamius.han 2016-05-01 21:03:43 UTC

I'll check if the bug was filled with the backend, then. 

(Gstreamer version is 4.9.0)

Comment 3 Andrew Crouthamel 2018-09-26 22:09:16 UTC

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 set the bug status 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!

Comment 4 Andrew Crouthamel 2018-10-27 02:42:57 UTC

Dear Bug Submitter,

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!