amarok crashed with SIGSEGV in SetCustomCoverAction::slotTriggered()

Bug #467864 reported by Kaustubh P on 2009-11-01
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Amarok
Confirmed
High
amarok (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: amarok

This same bug was present in Jaunty. I thought upgrading to Karmic would solve the issue, but it seems not. :| Could it be an error with the DB? Im using Kubuntu 9.10, with Amarok 2.2.0 I was trying to set a custom cover, and amarok crashed.

ProblemType: Crash
Architecture: i386
Date: Sun Nov 1 08:43:59 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/amarok
NonfreeKernelModules: nvidia
Package: amarok 2:2.2.0-0ubuntu2
ProcCmdline: /usr/bin/amarok
ProcEnviron:
 LANG=en_IN
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
SegvAnalysis:
 Segfault happened at: 0xb7397bc9 <_ZN20SetCustomCoverAction13slotTriggeredEv+233>: mov (%eax),%eax
 PC (0xb7397bc9) ok
 source "(%eax)" (0x00000019) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: amarok
StacktraceTop:
 SetCustomCoverAction::slotTriggered() ()
 BaseCoverAction::qt_metacall(QMetaObject::Call, int, void**)
 SetCustomCoverAction::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libamaroklib.so.1
 QMetaObject::activate(QObject*, int, int, void**) ()
 QMetaObject::activate(QObject*, QMetaObject const*, int, int, void**) () from /usr/lib/libQtCore.so.4
Title: amarok crashed with SIGSEGV in SetCustomCoverAction::slotTriggered()
Uname: Linux 2.6.31-14-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:2521): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Kaustubh P (thetuxracer) wrote :
Changed in amarok (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Jonathan Thomas (echidnaman) wrote :

Fixed in Amarok 2.2.1.

Changed in amarok (Ubuntu):
status: Triaged → Fix Released
Changed in amarok:
status: Unknown → Fix Released
Changed in amarok:
status: Fix Released → Invalid
Changed in amarok:
status: Invalid → Confirmed
Changed in amarok:
status: Confirmed → Unknown
Changed in amarok:
status: Unknown → Confirmed
Changed in amarok:
status: Confirmed → Fix Released
Changed in amarok:
status: Fix Released → Confirmed
Changed in amarok:
importance: Unknown → High
status: Confirmed → Fix Released
Changed in amarok:
status: Fix Released → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.