| Summary: | Amarok seems to crash randomly, after minutes or days of play, with no particular trigger. | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Gene Garrison <gene> |
| Component: | general | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | grimm |
| Priority: | NOR | ||
| Version First Reported In: | 2.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Gene Garrison
2010-02-18 03:32:11 UTC
This is not a problem in Amarok, but with your glibc version, please upgrade your system, this has been corrected since quite some time. I strongly suggest you activate the kubuntu-upgrades repository and also get a newer Amarok. See also http://kubuntu.org/news/amarok-2.2.2 Thanks, for the feedback, Myriam. I think i now understand how to read the
crash report to tell what actually caused the crash.
I have added the "Unsupported Updates" backport repository, so we'll see what
happens.
I'm trying to help you folks out as best i can. Unfortunately i'm a hardware
engineer, not a software engineer. :)
- GeneG
On Thursday 18 February 2010 12:07:23 am Myriam Schweingruber wrote:
> https://bugs.kde.org/show_bug.cgi?id=227463
>
>
> Myriam Schweingruber <myriam@kde.org> changed:
>
> What |Removed |Added
> ---------------------------------------------------------------------------
> - Status|UNCONFIRMED |RESOLVED
> Version|unspecified |2.2.0
> Resolution| |FIXED
>
>
>
>
> --- Comment #1 from Myriam Schweingruber <myriam kde org> 2010-02-18
> 09:07:18 --- This is not a problem in Amarok, but with your glibc version,
> please upgrade your system, this has been corrected since quite some time.
> I strongly suggest you activate the kubuntu-upgrades repository and also
> get a newer Amarok. See also http://kubuntu.org/news/amarok-2.2.2
>
*** Bug 232880 has been marked as a duplicate of this bug. *** *** Bug 234271 has been marked as a duplicate of this bug. *** |