View Issue Details

IDProjectCategoryView StatusLast Update
0006560MMW v4Playlist / Searchpublic2010-12-22 21:48
Reporterrusty Assigned To 
PriorityurgentSeverityminorReproducibilitysometimes
Status closedResolutionduplicate 
Product Version4.0 
Target Version4.0Fixed in Version4.0 
Summary0006560: Art & Details view: Deleting search results causes CD contents to appear
DescriptionThis bug is hard to explain, so I'll just give the repro steps:

0) Insert a CD
1) Click classical collection
2) Search entire library for beatles via search bar
3) Search entire library for cars via search bar
4) Search entire library for mozart via search bar
--> There are now a couple of entries in the search bar history
5) In the search bar, enter help (without pressing ENTER)
--> Search results appear for help
6) then press backspace to delete each letter
--> The contents of the Classical collection re-appear
--> ~10 seconds later, an 'Unknown' set of tracks appear for the CD inserted at 0) !!

Strangely, this only seems to happen in Artwork + Details mode (it doesn't occur in Details mode).
TagsNo tags attached.
Fixed in build1337

Relationships

duplicate of 0006962 closedpetr Art View jumps around 
related to 0006623 closedpetr Art & Details View: fails to refresh sometimes 

Activities

jiri

2010-10-19 20:12

administrator   ~0020868

Not sure if this is related to Search only, but assigning to Ludek to review.

rusty

2010-11-01 20:00

administrator   ~0021116

I just found another instance in which this occurs. At startup the Classical music node shows X tracks in AA+Details node.

After another ~10 seconds, the CD contents appear!

Ludek

2010-12-20 20:57

developer   ~0021970

Last edited: 2010-12-20 20:58

I cannot reproduce :-/

I would need to know more details:
1. Is it related to skinned or skinless version?
2. Is it related to a kind of CD (e.g. with/without CD-Text)
3. Is it related to a CD-Drive?
4. Couldn't it be caused by auto-run somehow? i.e. how long the CD is inserted in the drive?

Ludek

2010-12-20 21:00

developer   ~0021971

Last edited: 2010-12-20 21:16

Oh, I've just realized that I can consistenlty reproduce it in build 1334, but I cannot reproduce in build 1337 so I suspect it was somehow fixed by fixing another issue.

Resolving.

rusty

2010-12-21 17:57

administrator   ~0022018

Most likely a dup of 0006962. Need to retest.

rusty

2010-12-22 21:48

administrator   ~0022049

Verified 1339.