amarok crashed with SIGSEGV in QMetaObject::activate()

Bug #344699 reported by Laurent Claessens
6
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: amarok

This is an automatic bug report. Here is the output when I launch amarok in a terminal (Jaunty, up to date)

09:18:24 ~ >$ amarok
amarok(5292) Phonon::KdePlatformPlugin::createBackend: using backend: "Xine"
Object::connect: No such slot MainWindow::showStatistics() in /build/buildd/amarok-2.0.2mysql5.1.30/amarok-2.0.2/src/MainWindow.cpp:692
Object::connect: (receiver name: 'MainWindow')
QLayout: Attempting to add QLayout "" to MainWindow "MainWindow", which already has a layout
link XMLID_7_ hasn't been detected!
link XMLID_7_ hasn't been detected!
Couldn't resolve property: radialGradient3986
link XMLID_7_ hasn't been detected!
link XMLID_7_ hasn't been detected!
Couldn't resolve property: radialGradient3986
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
QWidget::insertAction: Attempt to insert null action
amarok(5292) Plasma::Applet::save: saving to "1"
amarok(5292) Context::ContextView::setContainment: "" Line: 599
amarok(5292) Plasma::ThemePrivate::config: using theme for app "amarok"
amarok(5292) Plasma::Applet::save: saving to "2"
amarok(5292) Plasma::Applet::save: saving to "3"
amarok(5292) Plasma::Applet::save: saving to "4"
amarok(5292) CurrentTrack::dataUpdated: CurrentTrack::dataUpdated
link XMLID_5_ hasn't been detected!
Couldn't resolve property: radialGradient3709
link XMLID_9_ hasn't been detected!
link XMLID_9_ hasn't been detected!
amarok(5292) Context::ColumnContainment::insertInGrid: "" Line: 603
<unknown program name>(5291)/: Communication problem with "amarok" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

My version of amarok is given by :
09:23:17 ~ > apt-cache policy amarok
amarok:
  Installé : 2:2.0.2mysql5.1.30-0ubuntu1
  Candidat : 2:2.0.2mysql5.1.30-0ubuntu1
 Table de version :
 *** 2:2.0.2mysql5.1.30-0ubuntu1 0
        500 http://be.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/amarok
Package: amarok 2:2.0.2mysql5.1.30-0ubuntu1
ProcCmdline: amarok
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_BE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: amarok
StacktraceTop:
 ?? () from /usr/lib/kde4/amarok_containment_context.so
 ?? () from /usr/lib/kde4/amarok_containment_context.so
 ?? () from /usr/lib/kde4/amarok_containment_context.so
 QMetaObject::activate () from /usr/lib/libQtCore.so.4
 QMetaObject::activate () from /usr/lib/libQtCore.so.4
Title: amarok crashed with SIGSEGV in QMetaObject::activate()
Uname: Linux 2.6.28-10-generic i686
UserGroups: admin sudo

Revision history for this message
Laurent Claessens (moky-math) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:Context::ColumnContainment::insertInGrid (this=0x9487830,
Context::ColumnContainment::addApplet (this=0x9487830,
Context::ColumnContainment::qt_metacall (this=0x9487830,
QMetaObject::activate () from /usr/lib/libQtCore.so.4
QMetaObject::activate () from /usr/lib/libQtCore.so.4

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in amarok:
importance: Undecided → Medium
C de-Avillez (hggdh2)
visibility: private → public
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This should be fixed in the Amarok 2.1 betas.

Changed in amarok (Ubuntu):
status: New → Fix Released
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.