Summary: | startup, scanning, after update | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Sebastian Insua-Summerhays <im.hanz> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 2.2.2 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Sebastian Insua-Summerhays
2010-01-14 14:54:24 UTC
Please type the following three commands in a konsole, in that order: export QT_NO_GLIB=1 export MALLOC_CHECK_= amarok -d --nofork If this solves the problem, then it is the glibc bug 196207. You should make sure to have a patched glibc version, then. It started working again. I've no idea why... :/ (In reply to comment #2) > It started working again. I've no idea why... :/ After having used the commands I told you or just like this? |