amarok crashed with SIGSEGV in EngineController::slotNewTrackPlaying()

Bug #376170 reported by Graham Stark
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Amarok
Won't Fix
High
amarok (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: amarok

I was copying a CD as ogg vorbis using Konqueror whilst using Amarok to play something else when this happened. The copying failed whilst Amarok itself kept running.

Hope this helps. Amarok is a great application, so thanks to you for helping with it.

Graham

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/amarok
Package: amarok 2:2.0.2mysql5.1.30-0ubuntu3
ProcCmdline: amarok -session 10c3cc676d000124196493200000040000140_1241982501_548565
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: amarok
StacktraceTop:
 ?? () from /usr/lib/libamaroklib.so.1
 EngineController::slotNewTrackPlaying ()
 EngineController::qt_metacall ()
 QMetaObject::activate ()
 Phonon::MediaObject::currentSourceChanged ()
Title: amarok crashed with SIGSEGV in EngineController::slotNewTrackPlaying()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: admin audio cdrom dialout floppy lpadmin plugdev sambashare scanner ve video www-data

Revision history for this message
Graham Stark (graham-stark) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:EngineSubject::newTrackPlaying (
EngineController::slotNewTrackPlaying (
EngineController::qt_metacall (this=0x2de15e0,
QMetaObject::activate (sender=0x2df23d0,
Phonon::MediaObject::currentSourceChanged (

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in amarok (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Changed in amarok (Ubuntu):
status: New → Triaged
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

A fix has been committed by the Amarok developers for Amarok 2.1.0.

Changed in amarok (Ubuntu):
status: Triaged → Fix Committed
Changed in amarok:
status: Unknown → Won't Fix
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fix released to Karmic.

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

Other bug subscribers

Remote bug watches

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