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.
--
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`
*
On Tue, 13 Apr 2021 00:38:47 +0200 Pelle wrote:
> 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,
Package: lollypop
Version: 1.4.19-1
Severity: normal
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
4 matches
Mail list logo
