amarok crashed with SIGSEGV in QAbstractButton::QAbstractButton()

Bug #358619 reported by panton41
18
Affects Status Importance Assigned to Milestone
qt4-x11 (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: amarok

I clicked the Internet tab and Amarok crashed and now refuses to start again. I think this is deeper than just Amarok, however, because Ksystemguard is crashing with the same error.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/amarok
NonfreeKernelModules: nvidia
Package: amarok 2:2.0.2mysql5.1.30-0ubuntu2
ProcCmdline: amarok
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: amarok
StacktraceTop:
 QAbstractButton::QAbstractButton ()
 QToolButton::QToolButton ()
 ProgressBarNG::ProgressBarNG ()
 CompoundProgressBar::CompoundProgressBar ()
 StatusBar::StatusBar ()
Title: amarok crashed with SIGSEGV in QAbstractButton::QAbstractButton()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare scanner vboxusers video

Revision history for this message
panton41 (panton41) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:QAbstractButton (this=0x2ad3e60, dd=@0x2a7a1b0, parent=0x2ad3dd0)
QToolButton (this=0x2ad3e60, parent=0x2ad3dd0)
ProgressBarNG (this=0x2ad3dd0,
CompoundProgressBar (this=0x2ad3e60,
StatusBar (this=0x2aa2370,

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
affects: amarok (Ubuntu) → qt4-x11 (Ubuntu)
visibility: private → public
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Hi,
Is this still an issue for you in the final version of Kubuntu 9.04?
Thanks in advance.

Changed in qt4-x11 (Ubuntu):
importance: Medium → Low
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in qt4-x11 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
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.