Summary: | Double click on cdda track in collection than Amarock has crashed. | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | ergo |
Component: | Playback | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | andresbajotierra, apasotti, aumuell, valeriodean |
Priority: | NOR | ||
Version: | 2.2.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
ergo
2010-03-22 20:48:29 UTC
*** Bug 231828 has been marked as a duplicate of this bug. *** According to the backtrace, this could be caused by 3 different issues: #8 0x00007f0b700c0dd6 in malloc_printerr (action=3, str=0x7f0b70182790 "double free or corruption (out)", ptr=<value optimized out>) at malloc.c:6217 #9 0x00007f0b700c574c in *__GI___libc_free (mem=<value optimized out>) at malloc.c:3716 #10 0x00007f0b72a9fa6b in ?? () from /usr/lib/tls/libnvidia-tls.so.1 #11 0x00007f0b5c628221 in ?? () from /usr/lib/xine/plugins/1.26/xineplug_inp_cdda.so - A bug in the glib library (which should be fixed already in your Ubuntu version) - A problem with the nVidia graphics drivers. - A problem with Phonon and the Xine library when reading audio CDs (bug 207579) Try updating your Ubuntu packages and your nVidia drivers. Regards *** Bug 231815 has been marked as a duplicate of this bug. *** Not related to media devices at all. Just realized: you're testing with 2.2? Please try to reproduce with 2.3.0 at least. *** Bug 232713 has been marked as a duplicate of this bug. *** Mass closing NEEDSINFO bugs with no comment for at least 31 days. Dear reporter, thanks for your feedback. For efficient bug triaging we need not only one report but also constant feedback about the status of an issue, at least when we ask for it. If your request is still valid in our latest release in your opinion (2.3.1 beta 1) DO NOT REOPEN THIS BUG but file a fresh one instead. Developers need clean bug reports to be able to work efficiently. Provide at least a step-by-step guide on how to reproduce the issue, a backtrace in case of a crash and debug output if appropriate. And remember: * One issue per bug. Small, clean bug reports are best to work on. * Search for duplicates. Hint: we have useful categories for that. :) -> RESOLVED INVALID |