amarok crashed with SIGSEGV in pthread_mutex_unlock()

[lord_dingo]

Binary package hint: amarok

amarok crasched

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 30 20:40:24 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/amarok
NonfreeKernelModules: binfmt_misc joydev snd_hda_codec_realtek coretemp hwmon_vid lp parport snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss iptable_filter snd_seq_midi snd_rawmidi ip_tables x_tables snd_seq_midi_event snd_seq snd_timer snd_seq_device asus_atk0110 snd soundcore snd_page_alloc psmouse serio_raw intel_agp nvidia usbhid ohci1394 ieee1394 sky2
Package: amarok 2:2.1.90-0ubuntu1
ProcCmdline: amarok -session 1014e98d8d4000125405392700000018770029_1254332077_785099
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x7f2258a226d6 <pthread_mutex_unlock+38>: addb $0x0,(%rax)
 PC (0x7f2258a226d6) ok
 source "$0x0" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: amarok
StacktraceTop:
 pthread_mutex_unlock () from /lib/libpthread.so.0
 g_main_context_prepare () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_iteration ()
 QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
Title: amarok crashed with SIGSEGV in pthread_mutex_unlock()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

[Shang Wu (shangwu)]

Could you provide us the steps on how to reproduce this?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as requested 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!