jackd crashes on startup with free() assertion
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| jackd2 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Seems to happen regardless of what arguments I give to jackd. E.g.:
mycroft@lop-nor:~$ jackd
jackdmp 1.9.7
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2011 Grame.
jackdmp 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
Cleaning up leftover debug module: DeviceManager
*** glibc detected *** jackd: free(): invalid pointer: 0x00007f9b6e40cb20 ***
======= Backtrace: =========
...
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: jackd2 1.9.7~dfsg-1ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Thu Oct 6 15:00:20 2011
ExecutablePath: /usr/bin/jackd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/bin/jackd -P10 -dalsa -r44100 -p1024 -n2 -D -Chw:1 -Phw:1 -zs -R -h
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
Signal: 6
SourcePackage: jackd2
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
free () from /lib/x86_
Title: jackd crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to oneiric on 2011-09-20 (16 days ago)
UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev postgres sambashare
modified.
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #869420, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.