Initial Mirage Scan never finishes if Mirage and Banshee scan at once

[GoogleCodeExporter]

What steps will reproduce the problem?
1. load up banshee with mirage
2. tell banshee where music library is
3. let auto scan on banshee and mirage happen simultaneously

What actually happens when you follow these steps?

Just loaded up the current version, and when I told Banshee where my music was
it started two processes. It began to catalog and scan my library, and mirage
began a full library scan. Banshee finished up in a few minutes, however Mirage
kept running and running, and the status bar never settled into a percentage,
just went back and forth, not giving how much to go %, etc.... After about
18hrs I finally stopped it and closed. Re-opened this morning and asked it to
rescan Mirage. Now I have a status bar and 5 finished, looks like it will
finish up fine. So the problem was at the initial setup and media scan, should
probably have Banshee finish the library scan before Mirage starts in.  

Also, maybe not an issue, but wanted to know if I add songs and re-scan Mirage,
if it will only scan new songs, or the whole thing again. It would be nice if
it knew to just do new additions.

S*

What would you expect to happen when you follow them? probably scan the
library first, then go to mirage scan next

What version of the product are you using? On what operating system? 1.5.2
(Beta), Ubuntu KK 9.10

Please provide any additional information below.

Original issue reported on code.google.com by skotty...@gmail.com on 13 Jan 2010 at 10:54

[GoogleCodeExporter]

Original comment by bertrand.lorentz@gmail.com on 30 Jan 2010 at 4:29

• Changed title: Initial Mirage Scan never finishes if Mirage and Banshee scan at once
• Added labels: Product-Mirage

[GoogleCodeExporter]

I made the same finding with current stable release of Ubuntu 9.10 Karmic
0.5.0-2 Banshee-extension mirage with Banshee 1.5.1-1.

I executed the mirage scan of collection after collection was imported and scan 
was
running for approx 20 hours before I discovered the scanning was repeating the
process and I killed it. Restarting Banshee fixed this 

Original comment by odin.hog...@gmail.com on 10 Feb 2010 at 6:39