Bug 307284

Summary: Calling "stop" using the system tray icon stops and restarts the current song before fading out
Product: [Unmaintained] phonon-backend-gstreamer Reporter: Frank Schaefer <fschaefer.oss>
Component: generalAssignee: Harald Sitter <sitter>
Status: RESOLVED DUPLICATE    
Severity: normal CC: matej, myriam, romain.perier, tdfischer
Priority: NOR    
Version: 4.6.1   
Target Milestone: 4.7   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Frank Schaefer 2012-09-23 19:59:53 UTC
When I stop playing a local mp3 file using the system tray icon, playback stops and the song gets restarted before fading out.

Reproducible: Always

Steps to Reproduce:
1. Play local mp3 file
2. Right click on the Amarok icon in the system tray
3. Left click on "stop"
Actual Results:  
1. sound stops
2. song is restarted
3. fades out

Expected Results:  
fading out without stop and restart

I'm using KDE 4.9.1 and the gstreamer backend (Pulseaudio is desease !).
Comment 1 Myriam Schweingruber 2012-09-23 20:19:14 UTC
Could you please try the phonon-backend-vlc and see if you can reproduce this?
Comment 2 Frank Schaefer 2012-09-24 17:40:41 UTC
After further experiments, it seems that this only happens when stopping playback for the first time after system start. (NOTE: I already noticed this issue on my old system (KDE 4.7x) and I'm pretty sure it happened every time there...)

Using the the VLC-backend, there is no stop-restart issue, but fading-out doesn't work (volume doesn't change). Seems to be a separate bug...
Comment 3 Myriam Schweingruber 2012-09-24 22:41:13 UTC
Yes, that would be indeed a different bug. Reassigning to the phonon-backend-gstreamer component. Which exact version of that component do you use?
Comment 4 Frank Schaefer 2012-09-25 10:22:14 UTC
phonon-gstreamer-backend version is 4.6.1
Comment 5 Harald Sitter 2012-09-25 17:02:47 UTC
after the first time that happens amarok's enginecontroller gets hugely confused with states... would not be surprised if that is in fact an amarok bug
Comment 6 Matěj Laitl 2013-01-20 10:33:06 UTC
Definitely Amarok bug, duplicate of bug 312062, I'm handling it right now.

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