Comment 64 for bug 68187

Should this bug be closed while the error persists? "quite likely not" doesn't indicate to me that it isn't. If it's genuinely confirmed that the problem exists in something that is not Amarok, then a link to the correct bug would be useful so ongoing issues can be tagged to it with an indication that it impacts Amarok which apparently depends on it.