Blacklisting lost after a rescan
Bug #149457 reported by
KDontenville
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Exaile |
Fix Released
|
High
|
Adam Olsen | ||
Bug Description
After blacklisting any tracks from within a playlist, the blacklisting works until the next library scan. When the scan is complete the blacklisting is lost. For us, 100% reproducible .
Seems to happen whatever permissions are set on the music share and from a variety of versions and update states. Same happens on Gutsy. I think this has happened since before 2.10 as it has been mentioned to me at least once before over the last year by my family, just forgot to follow up ;-)
Exaile v2.10
Ubuntu Feisty
Samba Network music files
Local Library db.
Revision history for this message
| Adam Olsen (arolsen) wrote | #1 |
| Changed in exaile: | |
| assignee: | nobody → arolsen |
| importance: | Undecided → High |
| status: | New → Fix Committed |
Revision history for this message
| reacocard (reacocard) wrote | #2 |
| Changed in exaile: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is fixed in the latest repository version, and will be in the 0.2.11 release.