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

Package:
lollypop
Source:
lollypop
Submitter:
Pelle
Date:
2022-04-18 17:36:14 UTC
Severity:
normal
Tags:
#986862#5
Date:
2021-04-12 22:38:47 UTC
From:
To:
Dear Maintainer,

Running `lollypop foo.mp3` will open up Lollypop and play foo.mp3, unless
Lollypop is already running, in which case Lollypop will switch to a random
track. I expected the command `lollypop foo.mp3` to play foo.mp3, even when
Lollypop is already open.
#986862#10
Date:
2021-04-12 23:41:05 UTC
From:
To:
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?

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

/Andreas
gusnan@debian.org
#986862#15
Date:
2021-04-13 09:14:16 UTC
From:
To:
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.
No, none of those are enabled. I haven't changed the default playback
settings.
#986862#22
Date:
2022-04-13 14:09:22 UTC
From:
To:
Hi -

As you might have noticed, upstream has closed the forwarded bug of this
one - but I don't really find the problem solved for me.

Could you please try with 1.4.31 which I just uploaded to unstable, and
see how it affects your use case?

I'm guessing that you still run into problems.
#986862#27
Date:
2022-04-13 20:11:03 UTC
From:
To:
The issue is still there.