Bug 1136351 - jackd assertion failed
Summary: jackd assertion failed
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: jack-audio-connection-kit
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brendan Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-02 12:05 UTC by Peter H. Jones
Modified: 2015-12-02 16:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 03:41:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
abrt compressed tar (190.89 KB, application/octet-stream)
2014-09-02 12:05 UTC, Peter H. Jones
no flags Details
gdb traceback of "jackd -d alsa" (4.81 KB, text/plain)
2014-09-02 23:49 UTC, Peter H. Jones
no flags Details
gdb of jackd as normal user (2.38 KB, text/plain)
2014-09-03 04:17 UTC, Peter H. Jones
no flags Details

Description Peter H. Jones 2014-09-02 12:05:50 UTC
Created attachment 933732 [details]
abrt compressed tar

Description of problem:
"jackd -vd alsa" gives an assertion faied messages, then dumps core

Version-Release number of selected component (if applicable):
jack-audio-connection-kit-1.9.9.5-8.fc21.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Become root
2. jackd -vd alsa

Actual results:
assertion failed message

Expected results:
jack server should start

Additional info:
abrt backtrace (attached)

Comment 1 Peter H. Jones 2014-09-02 23:49:38 UTC
Created attachment 933915 [details]
gdb traceback of "jackd -d alsa"

Got it with just "jackd -d alsa"

Comment 2 Brendan Jones 2014-09-03 02:59:26 UTC
I am wondering why you are running jackd as root. Is there a specific reason for doing this?

Comment 3 Peter H. Jones 2014-09-03 04:17:46 UTC
Created attachment 933942 [details]
gdb of jackd as normal user

Tried as normal user. I don't seem to get the backtrace, but then I get messages about not running with RT.

Comment 4 Brendan Jones 2014-09-03 04:32:13 UTC
Maybe if you follow this guide you can sort out your RT. Particular /etc/security/limits.d

https://fedoraproject.org/wiki/JACK_Audio_Connection_Kit

Comment 5 Fedora End Of Life 2015-11-04 15:12:04 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-12-02 03:41:25 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.