View Issue Details

IDProjectCategoryView StatusLast Update
0003932ardourbugspublic2012-05-23 15:07
Reporterbmdaugherty Assigned To 
Status acknowledgedResolutionopen 
Product Version3.0-alpha3 
Target Version3.0 
Summary0003932: Creating a master bus automatically with "use separate channels for monitoring" engaged causes seg fault.
DescriptionArdour3 Alpha3 downloaded package from Reproducable on ubuntu 32-bit acer netbook, as well as on ubuntu 64-bit macpro. Both machines are "up to date" meaning that the ubuntu update manager is happy, not that im using bleeding edge ppas or anything like that.

Upon first run of Ardour3a3 I was prompted to select if I wanted 'separate channels for monitoring' or something like that. I checked this option and proceeded to create a new session, but the system crashes with a segmentation fault. Both machines exhibit identical behavior.

The only way I can get A3a3 to recover is to create a new session and under the "more options for this session" uncheck the "create master bus" option. This will allow Ardour to start and you can disable the separate monitoring feature. You can then start A3a3 with defaults set.
Additional InformationBACKTRACE (standard -d) =

BACKTRACE (valgrind -v) =

My standard procedure is to configure the interface with alsamixer, then I configure jackd with the gui control and start jack. Then I start Jackd, then I start Ardour3 so this may be an issue with interfacing with jack and routing tables.

While Las and I were working, he said that the standard backtrace as well as the valgrind backtrace were not helpful so below is the verbose output of jackd


Hopefully this is helpful. Let me know if i need to run more tests on either machine.
TagsNo tags attached.



2011-04-12 02:34

reporter   ~0010546

Nothing new, but at least I can reproduce this issue. (should I select "confirmed" now?" I'm new to mantis and new to this whole bug tracking process)

Ubuntu 10.10 (32bit)
jackd version 0.118.0
jackd -R -d dummy (or alsa)

Steps to reproduce:

1. Create a new project or open an existing one.
2. Preferences:Audio: enable: "use a monitor bus"
3. close Ardour.
4. start Ardour
5. create new project with default preferences.

segfault can either be prevented by disabling "use a monitor bus" on step 2 or on step 5:
select: I'd like more options for this session
unselect: Create master bus (or enter 0 in the field).

let me know if you need more information.


2011-07-10 14:55

administrator   ~0011028

Last edited: 2011-07-10 16:48

is this still an issue with alpha9 ? I cant reproduce this here.


2011-07-10 19:30

reporter   ~0011041


Yes, I can still reproduce this issue.

Steps to reproduce: (copied from invalidname's note)

1. Create a new project or open an existing one.
2. Preferences:Audio: enable: "use a monitor bus"
3. close Ardour.
4. start Ardour
5. create new project with default preferences.

The "select separate channels for monitoring" prompt is gone from the session control, but following the steps outlined in invalidname's report, I can reproduce the issue in 64-bit alpha9. I will report back as to the status of the 32-bit build.


2011-07-10 23:46

reporter   ~0011050

yes, I can reproduce this on 32bit as well.
ubuntu 10.10, 32bit,
2.6.33-29-realtime 0000001-Ubuntu SMP PREEMPT RT Wed Aug 4 20:14:20 UTC 2010 i686 ardour3 alpha9 32bit

This time I ran ardour 5 times, giving me 4 different error messages when crashing. see error output here:

Issue History

Date Modified Username Field Change
2011-04-03 16:29 bmdaugherty New Issue
2011-04-03 19:26 cth103 cost => 0.00
2011-04-03 19:26 cth103 Target Version => 3.0-beta1
2011-04-12 02:34 invalidName Note Added: 0010546
2011-07-10 14:55 paul Note Added: 0011028
2011-07-10 14:55 paul Status new => feedback
2011-07-10 16:48 paul Note Edited: 0011028
2011-07-10 19:30 bmdaugherty Note Added: 0011041
2011-07-10 23:46 invalidName Note Added: 0011050
2011-11-15 17:18 cth103 Target Version 3.0-beta1 => 3.0-beta2
2012-01-10 20:46 cth103 Target Version 3.0-beta2 => 3.0-beta3
2012-02-14 17:20 paul Target Version 3.0-beta3 => 3.0 beta4
2012-04-23 22:06 cth103 Status feedback => acknowledged
2012-05-23 15:07 cth103 Target Version 3.0 beta4 => 3.0