Bug 352721 - Amarok start playing on resume
Summary: Amarok start playing on resume
Status: REPORTED
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 4.8.3
Platform: Other Linux
: NOR normal
Target Milestone: 4.8
Assignee: Harald Sitter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-15 01:24 UTC by Yichao Yu
Modified: 2021-03-09 22:36 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yichao Yu 2015-09-15 01:24:38 UTC
When resuming from standby amarok always start playing the current list even if it was not before going in to sleep.

Depending on the setting, it might pause after sometime but I'm always seeing this on resume.


Reproducible: Always
Comment 1 Myriam Schweingruber 2015-09-15 12:14:22 UTC
Go to your settings Menu -> Configure Amarok -> Playback and remove the tick to "Resume play on start". 

Not a bug, just a wrong setting on your system. It works perfectly fine here.
Comment 2 Yichao Yu 2015-09-15 12:33:32 UTC
> Go to your settings Menu -> Configure Amarok -> Playback and remove the tick to "Resume play on start".

That setting is never selected to begin with and Amarok is never closed when I put my computer on standby. (And I didn't try enabling it when looking for an option to workaround it since looks like it can only make it worse)

The option that partly works around it is "Pause playback on suspend". However, even then the playback is still started for a short time on resume.

I realize that this is probably not something new in amarok 2.8.0 since it was not upgraded recently (and I've used it with no problem since late April until a few days before). It might be related to the upgrade of other kde (or non-kde) components. Amarok does seems to be the only software that has issue when I resume from standby so if anyone has idea why amarok is getting a wrong signal, we can see which part is not behaving as expected.
Comment 3 Myriam Schweingruber 2015-09-15 12:36:01 UTC
Then we need much more information about your system, in particular the KDE release, which phonon backend you use and the version of it.
Comment 4 Yichao Yu 2015-09-15 12:41:08 UTC
Sure.

The system is ArchLinux with testing enabled.

Amarok 2.8.0-6
kdebase-runtime 15.08.0-1

Phonon (-qt4 4.8.3) backend: 1) vlc (0.8.2); 2) gstreamer (4.8.2)

Linux kernel: 4.2
Comment 5 Myriam Schweingruber 2015-09-15 12:44:13 UTC
(In reply to Yichao Yu from comment #4)

> Phonon (-qt4 4.8.3) backend: 1) vlc (0.8.2); 2) gstreamer (4.8.2)
>
Erm, you can use only one backend at a time, which exact one does this problem happen with? And did you switch backend and try with the other one (KDE needs to be restarted when switching the backend)? Since all sound output is not done by Amarok, but by Phonon, this is important to test.
Comment 6 Yichao Yu 2015-09-15 12:56:20 UTC
> Erm, you can use only one backend at a time, which exact one does this problem happen with?

I list them in the order listed under the backend settings. Unless amarok has it's own setting somewhere else, I think the first one would be used. I list both of them just to provide more complete information.

> Since all sound output is not done by Amarok, but by Phonon, this is important to test.

I didn't know phonon also control the restart of the playback. I've just tested with vlc and it seems to have the same problem. I'll switch the backend to gstreamer and test again.

None of the phonon-qt4* packages are upgraded recently so it's probably still something else. Let's see if I can change the product to phonon first.
Comment 7 Yichao Yu 2015-09-15 13:08:20 UTC
Switching phonon (Qt4) backend doesn't help.

I also tried to disable the media player applet in the systemtray and it didn't help.

I've also noticed that when vlc autostarted after resuming, amarok didn't start automatically at the same time.
Comment 8 Justin Zobel 2021-03-09 22:36:55 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.