| Summary: | Amarok crashes when adjustnig volume | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Ben <bwbees0> |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 2.5-git | ||
| Target Milestone: | 2.6 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Ben
2012-05-24 02:43:22 UTC
Is this reproducible? It looks like a duplicate of bug 230991 Hi Myriam, My apologies for not getting to this sooner. I was out of town for work when your note arrived and I have just gotten to my home email. You asked if this was reproducible. The crash happened twice in a row the day I reported it. So far today, Amarok is not misbehaving. So perhaps this is an intermittent occurrence. Curiously after the first crash, the crash reporting tool did not like the backtrace that was created. The crash reporting tool said there was not enough information for the report to be useful. I was in the process of filling out a manual bug entry when Amarok crashed again while I was turning up the volume. The second crash report contained useful information and is the one that was submitted with the bug report. I am not versed in reading crash reports -- that is something I need to learn how to do someday. I looked over bug 230991 and I can't tell one way or the other. I don't have a Magnatunes account though if that helps any. Let me know if you have any questions and I will see what I can do to get you some answers. Thanks in advance, Ben On Thu, 2012-05-24 at 06:25 +0000, Myriam Schweingruber wrote: > https://bugs.kde.org/show_bug.cgi?id=300539 > > Myriam Schweingruber <myriam@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Version|unspecified |2.5-git > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Myriam Schweingruber <myriam@kde.org> --- > Is this reproducible? It looks like a duplicate of bug 230991 > Don't worry, it doesn't depend on Magnatune but on the collections management, that other bug report just happened to be triggered with the Magantune collection. If you get a crash again without a valid backtrace you could try running amarok in gdb with the options -d --nofork to see if the resulting backtrace is better. I close this for now, but please do not hesitate to reopen it if it happens again. Hi Myriam,
Thanks for the tip to use gdb. I should have thought of that!
Have a nice weekend,
Ben
On Fri, 2012-05-25 at 20:35 +0000, Myriam Schweingruber wrote:
> https://bugs.kde.org/show_bug.cgi?id=300539
>
> Myriam Schweingruber <myriam@kde.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEEDSINFO |RESOLVED
> Resolution|WAITINGFORINFO |WORKSFORME
>
> --- Comment #3 from Myriam Schweingruber <myriam@kde.org> ---
> Don't worry, it doesn't depend on Magnatune but on the collections management,
> that other bug report just happened to be triggered with the Magantune
> collection.
>
> If you get a crash again without a valid backtrace you could try running amarok
> in gdb with the options -d --nofork to see if the resulting backtrace is
> better.
>
> I close this for now, but please do not hesitate to reopen it if it happens
> again.
>
|