[apport] kxineplayer crashed with SIGSEGV in pthread_mutex_lock()

Bug #115310 reported by dan
2
Affects Status Importance Assigned to Milestone
kmplayer (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: kmplayer

don't know

ProblemType: Crash
Architecture: i386
Date: Thu May 17 21:48:15 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/kxineplayer
Package: kmplayer-base 0.9.4-0ubuntu2
PackageArchitecture: i386
ProcCmdline: kxineplayer -wid 31457858 -f /home/dan/.kde/share/apps/kmplayer/xine_config -vo xv,sdl,x11 -ao alsa -cb kaffeine/KMPlayerCallback-0 -c
ProcCwd: /home/dan
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kmplayer
StacktraceTop:
 pthread_mutex_lock ()
 xine_event_send () from /usr/lib/libxine.so.1
 ?? ()
 ?? ()
 ?? ()
Uname: Linux dan-desktop 2.6.20-15-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 GNU/Linux
UserGroups: admin audio cdrom dialout dip floppy lpadmin mail plugdev scanner video

Revision history for this message
dan (environ314+ubuntu) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0
xine_event_send (stream=0x0, event=0xb6ffb1bc) at events.c:80
XEventThread::run (this=0x8071b10) at /build/buildd/kmplayer-0.9.4/./src/xineplayer.cpp:981
QThreadInstance::start (_arg=0x80719b4) at kernel/qthread_unix.cpp:119
start_thread () from /lib/tls/i686/cmov/libpthread.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. However, this bug is a duplicate of bug 104019 and is being marked as such. Feel free to submit any future bugs you may find.

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.