Summary: | amarok mysql disabled update collection | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | nospam |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | oleg.atamanenko+kde |
Priority: | NOR | ||
Version: | 2.2.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
nospam
2009-10-26 20:41:37 UTC
Sorry, but your backtrace is not useful, as you are lacking debugging symbols. If you can reproduce this bug, please check here on how to get a valid backtrace: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports (In reply to comment #1) I'll try to reproduce this, just installed 200mbytes of dbg packages. :) The mysql auth had a problem (typo in password), so the problem may lie around where someone enables mysql support with incorrect auth credentials. Closing for lack of feedback. Please reopen this report only if you can reproduce it in the upcoming Amarok 2.2.1 with a valid backtrace. *** Bug 233500 has been marked as a duplicate of this bug. *** ok, so this is the first report, but the other has the advantage of being still open. :) *** This bug has been marked as a duplicate of bug 236237 *** |