On 26/04/2011 02:29, Kamus wrote:
> Which version of banshee do you use? by the way, I tried to reproduce
> ths issue here with banshee 2.0 included in Ubuntu Natty but it works
> fine for me (tried to run three instances of banshee in a terminal)
>
> ** Changed in: banshee (Ubuntu)
> Importance: Undecided => Low
>
I reckon this is a duplicate of Bug #766303, where multiple Banshee instances
launched at the same time did not detect each other and all tried to lock the
sqlite database at the same time.
duplicate 766303
To reliably reproduce this issue, you can do "banshee & banshee & banshee &"
which will launch three instance at once (timing is important). It may be that
only multiprocessor machines can reproduce this bug -- I haven't actually tried
on any other machine apart from my laptop running a Core 2 Duo.
On 26/04/2011 02:29, Kamus wrote:
> Which version of banshee do you use? by the way, I tried to reproduce
> ths issue here with banshee 2.0 included in Ubuntu Natty but it works
> fine for me (tried to run three instances of banshee in a terminal)
>
> ** Changed in: banshee (Ubuntu)
> Importance: Undecided => Low
>
I reckon this is a duplicate of Bug #766303, where multiple Banshee instances
launched at the same time did not detect each other and all tried to lock the
sqlite database at the same time.
duplicate 766303
To reliably reproduce this issue, you can do "banshee & banshee & banshee &"
which will launch three instance at once (timing is important). It may be that
only multiprocessor machines can reproduce this bug -- I haven't actually tried
on any other machine apart from my laptop running a Core 2 Duo.
--
Kind regards,
Loong Jin