Music player can get into a state where tapping on a track doesn't start playing it
Bug #1398323 reported by
Brendan Donegan
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Music App |
New
|
Undecided
|
Unassigned | ||
Bug Description
In the latest version of the music app (com.ubuntu.music 2.0.745), I can get the app into a state where it doesn't start playing tracks when you tap on them. To reproduce this we need to run the autopilot test suite a number of times: 'for i in `seq 10`; do autopilot3 run music_app -f xml -o music$i.xml; done'. At some point the tests should start failing and when we go to start a track in the music player (outside of autopilot running), then it loads the track in Now playing but the initial state of the track is Paused. Tapping on the Play button also does nothing.
Revision history for this message
| Victor Thompson (vthompson) wrote | #1 |
Revision history for this message
| Brendan Donegan (brendan-donegan) wrote Re: [Bug 1398323] Re: Music player can get into a state where tapping on a track doesn't start playing it | #2 |
To post a comment you must log in.
Hi Brendan! Thanks for the bug report! Do you know if rebooting helps this? Also, it'd be interesting to know if other audio playing apps stop working. I suspect something might be happening that is causing media-hub to refuse additional clients--or maybe there is a failure somewhere else on the audio stack.