Summary: | Amarok stutters and hangs system before crashing | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Be <be.0> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | rdieter |
Priority: | NOR | Keywords: | drkonqi |
Version: | 2.8.0 | ||
Target Milestone: | 2.9 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | error when starting pavucontrol after quitting Amarok |
Description
Be
2016-06-15 17:20:35 UTC
First of all: you do not have debugging symbols installed for Amarok, so the backtrace is only partly useful. Please see https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Fedora on how to install debugging symbols for Amarok and it's dependencies on your distribution. Besides that, since you have kdelibs debugging symbols installed, it appears the crash happens in kdelibs, but for the backtrace to be fully useful, it would be nice to have a new one with all debugging symbols installed, including those for Amarok. FWIW: this is most likely a duplicate of bug 324786 Okay, I installed debugging symbols for Amarok. I'll attach a new backtrace when I get one, but I don't exactly know how to reproduce the issue. Created attachment 99668 [details]
error when starting pavucontrol after quitting Amarok
Hm, so this may have something to do with PulseAudio. It happened again and I left my computer for a while (after unplugging my speakers from my sound card). When I came back, Amarok had not crashed, but my system was taking a long time to respond to anything until I quit Amarok. I restarted Amarok and got a warning from Phonon saying that various outputs could not be found, including PulseAudio. Amarok wouldn't output any sound (maybe it was playing to my onboard sound card?) so I started pavucontrol to check if my USB sound card (an RME Babyface Pro in class compliant mode) got disconnected and PulseAudio wasn't detecting it, but pavucontrol showed the error in the attached screenshot. I ran 'pulseaudio -D' and restarted Amarok, then Amarok worked fine. so no crash anymore or should we still wait for a backtrace? Even if this is a pulseaudio issue, a backtrace would still be nice to have as it makes cornering the problem easier. Whatever was causing this, it hasn't been an issue since upgrading to Fedora 24. |