amarok crashed with SIGSEGV in QProgressDialog::setMaximum()

Bug #453897 reported by Alejandro Hamann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Amarok
Fix Released
High
amarok (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: amarok

The crash occurred when i was updating the cover manager.

ProblemType: Crash
Architecture: amd64
Date: Sat Oct 17 09:19:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/amarok
NonfreeKernelModules: nvidia
Package: amarok 2:2.2.0-0ubuntu2
ProcCmdline: /usr/bin/amarok
ProcEnviron:
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SegvAnalysis:
 Segfault happened at: 0x7ff6c3c7def4 <_ZN15QProgressDialog10setMaximumEi+4>: mov 0x248(%rax),%rdi
 PC (0x7ff6c3c7def4) ok
 source "0x248(%rax)" (0x200000248) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: amarok
StacktraceTop:
 QProgressDialog::setMaximum (this=0x147c190,
 CoverManager::slotArtistSelectedContinueAgain (
 CoverManager::qt_metacall (this=0x8ac07f0,
 QMetaObject::activate (sender=0x89043f0,
 SqlQueryMaker::qt_metacall (this=0x89043f0,
Title: amarok crashed with SIGSEGV in QProgressDialog::setMaximum()
Uname: Linux 2.6.31-13-generic x86_64
UserGroups: ICDT audio cdrom dialout fax floppy fuse plugdev sambashare staff users video voice

Revision history for this message
Alejandro Hamann (linkstat) wrote :
Changed in amarok (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Changed in amarok:
status: Unknown → Fix Released
Changed in amarok:
importance: Unknown → High
Revision history for this message
Rohan Garg (rohangarg) wrote :

Thanks for taking the time to report this bug. 9.10 reached end of life on April 30, 2011.
Please see this document for currently supported Kubuntu releases:
https://wiki.kubuntu.org/Releases

Unfortunately this means that there will be no more bugfixes for 9.10. It is also recommended that you upgrade, if you have not already.

Please feel free to report any other bugs you may find, and thanks for your understanding.

Changed in amarok (Ubuntu):
status: Triaged → Invalid
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.