[apport] jackd crashed with SIGSEGV in pthread_cancel()

Bug #90874 reported by nuutpent
2
Affects Status Importance Assigned to Milestone
jack-audio-connection-kit (Ubuntu)
Invalid
Medium
MOTU

Bug Description

17:59:57.136 Patchbay deactivated.
17:59:57.181 Statistics reset.
17:59:57.431 Startup script...
17:59:57.432 artsshell -q terminate
17:59:57.496 MIDI connection graph change.
sh: artsshell: not found
17:59:57.702 Startup script terminated with exit status=32512.
17:59:57.714 JACK is starting...
17:59:57.715 jackd -R -p128 -t4900 -dalsa -ddefault -r48000 -p64 -n2 -D -C/dev/dsp -S
17:59:57.731 JACK was started with PID=5990 (0x1766).
17:59:57.936 Could not connect to JACK server as client. Please check the messages window for more info.
jackd 0.102.20
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... default|/dev/dsp|64|2|48000|0|0|nomon|swmeter|-|16bit
ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM /dev/dsp
ALSA: Cannot open PCM device alsa_pcm for capture. Falling back to playback-only mode
configuring for 48000Hz, period = 64 frames, buffer = 2 periods
ALSA: final selected sample format for playback: 16bit little-endian
You appear to be using the ALSA software "plug" layer, probably
a result of using the "default" ALSA device. This is less
efficient than it could be. Consider using a hardware device
instead rather than using the plug layer. Usually the name of the
hardware device that corresponds to the first soun
ALSA: cannot set period size to 64 frames for playback
ALSA: cannot configure playback channel
cannot load driver module alsa
18:00:02.708 JACK was stopped successfully.
18:00:03.809 MIDI connection change.

ProblemType: Crash
Architecture: i386
Date: Fri Mar 9 18:00:00 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/jackd
Package: jackd 0.102.20-1
PackageArchitecture: i386
ProcCmdline: jackd -R -p128 -t4900 -dalsa -ddefault -r48000 -p64 -n2 -D -C/dev/dsp -S
ProcCwd: /home/pentti
ProcEnviron:
 LANGUAGE=fi_FI:fi:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: jack-audio-connection-kit
Stacktrace:
 #0 0xb7f41400 in pthread_cancel () from /lib/tls/i686/cmov/libpthread.so.0
 #1 0x0804e80e in ?? ()
 #2 0x00000000 in ?? ()
StacktraceTop:
 pthread_cancel () from /lib/tls/i686/cmov/libpthread.so.0
 ?? ()
 ?? ()
Uname: Linux pentti 2.6.20-9-386 #2 Mon Feb 26 02:58:41 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
nuutpent (pentti-nuutinen) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report.

Changed in jack-audio-connection-kit:
assignee: nobody → motu
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:pthread_cancel () 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
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 jack-audio-connection-kit:
status: Unconfirmed → Needs Info
Revision history for this message
Sebastien Bacher (seb128) 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 jack-audio-connection-kit:
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.