[apport] amarokapp crashed with SIGSEGV

[anengel]

Binary package hint: amarok

during system startup ... maybe after amarok update??
not sure thought.

ProblemType: Crash
Architecture: i386
Date: Thu Mar 29 22:39:58 2007
Disassembly: 0xb726b1ed:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/amarokapp
Package: amarok 2:1.4.5-0ubuntu6
PackageArchitecture: i386
ProcCmdline: amarokapp
ProcCwd: /home/engel
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: amarok
Stacktrace: #0 0xb726b1ed in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Uname: Linux Himmel 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Andrew Ash (ash211)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is missing. Could you please add the crash report that you received? It will be found in '/var/crash/'. This will allow us to better troubleshoot your bug. If it doesn't exist there, 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.

[Apport retracing service (apport)]

StacktraceTop:?? ()

[anengel (mail-a-engel)]

hello andrew,

here we go. i hope that's the corresponding crash report you asked for.
the problem might have been provoked by adding another sound card beside the already working on-board card.
if you have some more questions don't hesitate to contact me again.

thanks for your support

andreas

[Andrew Ash (ash211)]

Thanks for including that report, Andreas. Unfortunately, it doesn't include a stacktrace at the bottom so it's not much good to us. If possible now, please try to get a trace <http://wiki.ubuntu.com/DebuggingProgramCrash> and attach the file to the bug report. This will greatly help us in tracking down your problem. Thanks

[anengel (mail-a-engel)]

as i understand the debugging description page you entered the problem will have to recur to get useable informations.
since the crash disapeared (maybe one of the last updates solved the issue?) i can't figure out how to give you the information you asked for.
maybe it's best to colse that ticket. if i run into similar problems again (not only for amarok but for any application) at least i know how to give you apropriate and detailed information now.

[Andrew Ash (ash211)]

That's correct. Hopefully the next time it crashes, apport, the program that caught the crash the first time, will be able to catch more detailed information. Otherwise, thanks for the bug report!