@Jim, I've looked at lp:1442927 and the test failures started with vivid image #158 [1] which included the new media-hub3 package [2]. This bug is easily reproducible if the previous button (which does a "seek" to 0 in this case) is pressed very soon after hitting the pause button. You can look through the various logs listed in the image 158 tests [1], but it doesn't appear as though anything obvious is being output. Do you think it's possible that media-hub is still processing something related to the "pause" action/request that is being interrupted by the "seek to 0" action or is otherwise preventing the seek from occurring?
@Jim, I've looked at lp:1442927 and the test failures started with vivid image #158 [1] which included the new media-hub3 package [2]. This bug is easily reproducible if the previous button (which does a "seek" to 0 in this case) is pressed very soon after hitting the pause button. You can look through the various logs listed in the image 158 tests [1], but it doesn't appear as though anything obvious is being output. Do you think it's possible that media-hub is still processing something related to the "pause" action/request that is being interrupted by the "seek to 0" action or is otherwise preventing the seek from occurring?
1 - http:// ci.ubuntu. com/smokeng/ vivid/touch/ mako/158: 20150401. 1:20150210/ 12560/music_ app/ people. canonical. com/~ogra/ touch-image- stats/158. changes
2 - http://