Bug#986862: lollypop: Filename args doesn't work when Lollypop is already running

[Pelle]

On 13/04/2021 01:41, Andreas Ronnquist wrote:

Thanks for your report - I can reproduce the problem to some extent.
What if you run the command and include the full path to the file?
Does this change things?

I tried specifying the path in various ways to Lollypop:

 * `lollypop foo.mp3`
 * `lollypop ~/foo.mp3`
 * `lollypop $HOME/foo.mp3`
 * `lollypop /home/pelle/foo.mp3`

I thought I'd narrowed down a specific path formatting issue.

I ran those commands again, just to check, but now they gave a different result. Then I tried running `lollypop /home/pelle/foo.mp3` over and over again, and this resulted in foo.mp3 being played about 10% of the time, and a random track the rest of the time. The behaviour appears to be nondeterministic.

What settings to you have for playback? Anything exotic, like
"Continuous playback", "Automatic playback (random)" or "Automatic
playback (similar)"?

No, none of those are enabled. I haven't changed the default playback settings.

OpenPGP_0x3A57CE276008178F.asc
Description: OpenPGP public key

OpenPGP_signature
Description: OpenPGP digital signature