Comment 8 for bug 396268

I backed up .gconf/apps/banshee-1/ .config/banshee-1/ and .cache/banshee-1/ (There were no /apps/banshee or .config/banshee files on my system).

I then tried `gconftool-2 --recursive-unset /apps/banshee /apps/banshee-1` but that does not seem to have made any difference. It still takes about 5 seconds of 100% cpu before the UI updates after I click on anything.

I then tried just deleting all the files:

$ rm -r .config/banshee-1
$ rm -r .cache/banshee-1
$ rm -r .gconf/apps/banshee-1

And banshee was responsive (once it had started, ps -ef reported that there was 9 seconds of time used by banshee after starting up).

I've restored it, and it is unresponsive again. I have only 62 items in my music library. However I have 20 podcast feeds, with a total of 1699 items. I don't know if that would overly stress banshee? I would hope not.

Given that turning off all gconf settings didn't help, do you have any other ideas?