[apport] amarokapp crashed with SIGSEGV

Bug #93875 reported by Søren Holm
4
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: amarok

apparently happenend during logout. Don't actually know.

ProblemType: Crash
Architecture: i386
Date: Mon Mar 19 22:52:28 2007
Disassembly: 0xb6784a05:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/amarokapp
Package: amarok 2:1.4.5-0ubuntu6
PackageArchitecture: i386
ProcCmdline: amarokapp
ProcCwd: /home/sgh
ProcEnviron:
 PATH=/home/sgh/bin:/home/sgh/arm-elf-tools/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: amarok
Stacktrace: #0 0xb6784a05 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Uname: Linux phoenix 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Søren Holm (sgh) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report.

Changed in amarok:
assignee: nobody → kubuntu-team
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in amarok:
status: Unconfirmed → Needs Info
Revision history for this message
Andrew Ash (ash211) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in amarok:
assignee: kubuntu-team → nobody
status: Needs Info → Rejected
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.