amarok crashed with SIGSEGV in start_thread()

[shaikailash]

Binary package hint: amarok

Amarok was simply scanning a new collection and crashed.
Sadly it's only one of the many crashes I'm having since the upgrade from kubuntu 9.04 to kubuntu 9.10.
Amarok version 2.2, KDE version 4.3.2

ProblemType: Crash
Architecture: amd64
Date: Fri Oct 30 20:33:05 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/amarok
NonfreeKernelModules: nvidia
Package: amarok 2:2.2.0-0ubuntu2
ProcCmdline: /usr/bin/amarok
ProcEnviron:
 LANGUAGE=it_IT:it:en_GB:en
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x7f74453279d4: callq *0x38(%rax)
 PC (0x7f74453279d4) ok
 source "*0x38(%rax)" ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: amarok
StacktraceTop:
 ?? () from /usr/lib/libxine.so.1
 start_thread () from /lib/libpthread.so.0
 clone () from /lib/libc.so.6
 ?? ()
Title: amarok crashed with SIGSEGV in start_thread()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Jonathan Thomas (echidnaman)]

Could you install libxine1-dbg and phonon-dbg and try to get another backtrace? Thanks in advance.

[shaikailash (steve-doc-brown)]

After a lot of crashes and problems, I decided to format and make a fresh installation of Kubuntu 9.10. Now it works really well without any problem, a completely different system.
I could say that the real bug is the upgrade from a previous version to a new release, it's always like this with problem for almost every user.
My advice is to do only one release a year, and fix in a better way all the problem.
Thank you

[Harald Sitter (apachelogger)]

Closing bug since it can not be reproduce anymore.