Bug 2026792 - Ardour6 freezes in Fedora 35
Summary: Ardour6 freezes in Fedora 35
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: ardour6
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-25 20:14 UTC by Bob Dubois
Modified: 2023-09-18 04:28 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:59:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
ardour-output-stdout (20.72 KB, text/plain)
2021-11-25 20:14 UTC, Bob Dubois
no flags Details

Description Bob Dubois 2021-11-25 20:14:19 UTC
Created attachment 1843630 [details]
ardour-output-stdout

Description of problem:
Ardour6.6.9 is broken in Fedora 35. I upgraded from 34 and Ardour is no longer working properly.
Installed a clean Fedora Jam 35 in a VM to replicate the issue, and it's exactly the same.

Actions taken:
Started ardour6 from CLI
Opened existing project or started new project
Do anything in the GUI, like starting a playback, clicking in the timeline, ...
Ardour freezes.

When starting a project or opening an existing project, a ton of error messages are dropped on the CLI (see attached).


Version-Release number of selected component (if applicable):
6.6.9

How reproducible:

Steps to Reproduce:
1.Start Ardour6 on Fedora 35
2.open new or existing project
3.check STDOUT output

Actual results:
Ardour hangs

Expected results:


Additional info:

Comment 1 Guido Aulisi 2021-11-26 07:58:38 UTC
I can see some problems with lv2 plugins, klaviatur.lv2 and newtonator.lv2 which seem to have broken definition files.

Can you try without those plugins?

Also what backend are you using? Also, jack, pipe wire-jack?
There were some problems with pipe wire in the past, you should try with jack too.

Comment 2 Bob Dubois 2021-11-26 08:14:52 UTC
Using jack emulated by pipewire, as should be default in Fedora 35 if I'm not wrong.

Removed broken plugins and Ardour is now running (not sure which functionality I lost without those plugins).

Funky output of lilv on the STDOUT remains however!

Comment 3 Bob Dubois 2021-11-26 09:11:16 UTC
Ignore previous comment:
Ardour still not working after removal of the broken plugins.

Comment 4 Guido Aulisi 2021-11-26 09:19:54 UTC
Please try with jack-audio-connection-kit too.

Comment 5 Bob Dubois 2021-11-26 12:44:10 UTC
Flipping from pipewire back to jack is not so easily done, IMHO. Correct me if I'm wrong.
installing Jack conflicts with pipewire-jack.
Uninstalling pipewire-jack drags all music apps with it down the drain...

Comment 6 Guido Aulisi 2021-11-26 12:47:20 UTC
Yes, it's not easy, this is a problem IMHO.

Maybe you can try adding --allowerasing to def

Comment 7 Bob Dubois 2021-11-26 12:59:04 UTC
that would make the problem worse...
So: going away from pipewire in F35 isn't the solution and Ardour doesn't behave normally.
Not even in the LiveCD, try it out please to see if you can replicate the issue in the LiveCD of F35 Jam.
Just start Ardour from CLI and see the ton of errors being logged.

Comment 8 Bob Dubois 2021-11-26 13:03:49 UTC
update:
- new test in LiveCD, errors do get logged on stdout but Ardour is working in this environment (ON pipewire).
- Ardour on my desktop: errors on stdout, ardour crashes when starting a track or selecting a track. Process ArdourGUI at 100%, GUI totally frozen.

Comment 9 Guido Aulisi 2021-11-26 13:14:10 UTC
If I run
dnf install jack-audio-connection-kit --allowerasing

I get:

Dependencies resolved.
==============================================================================================================
 Package                                     Architecture    Version                  Repository         Size
==============================================================================================================
Installing:
 jack-audio-connection-kit                   x86_64          1.9.19-1.fc35            fedora            531 k
Installing dependencies:
 libffado                                    x86_64          2.4.4-5.fc35             fedora            842 k
 libxml++                                    x86_64          2.42.1-2.fc35            fedora            101 k
Removing dependent packages:
 pipewire-jack-audio-connection-kit          x86_64          0.3.40-1.fc35            @updates          492 k

Transaction Summary
==============================================================================================================
Install  3 Packages
Remove   1 Package

Comment 10 Bob Dubois 2021-11-26 13:26:07 UTC
ok done so, with pulseaudio as well.
Jack server cannot be started because pipewire is still occupying the HW...

Device reservation request with priority 2147483647 denied for "Audio0": org.freedesktop.DBus.Error.UnknownMethod (Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1)
Failed to acquire device name : Audio0 error : Method RequestRelease is not implemented on interface org.freedesktop.ReserveDevice1
Audio device hw:USB cannot be acquired...
Jack: ~JackDriver
Cannot initialize driver
Jack: no message buffer overruns
Jack: JackPosixThread::Stop
Jack: JackPosixThread::ThreadHandler : exit
JackServer::Open failed with -1
Jack: Succeeded in unlocking 107341340 byte memory area
Jack: JackShmMem::delete size = 0 index = 0
Jack: ~JackDriver
Jack: Succeeded in unlocking 1196 byte memory area
Jack: JackShmMem::delete size = 0 index = 1
Jack: Cleaning up shared memory
Jack: Cleaning up files
Jack: Unregistering server `default'
Failed to open server
14:24:37.562 JACK was stopped
14:24:39.557 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

Comment 11 Bob Dubois 2021-11-26 13:33:06 UTC
Switched to ALSA backend for Ardour instead of Jack. No more freezes of Ardour.
Now need to get my head around how to get sound out of it but it certainly is pipewire-jack that was giving trouble.

Comment 12 Bob Dubois 2021-11-29 08:01:43 UTC
alsa backend is equally unstable. Track playback results in freezes after a while. Slightly different behavior than with jack, equally unusable.

Comment 13 Sebastián Samaniego 2022-05-25 21:38:26 UTC
I just want to add that this bug also happened to me on Ardour 6.9.0 and Fedora 36. Ardour is not able to play back sound, and always crashed immediately after clicking on the timeline.

$ ardour6
WARNING: Your system has a limit for maximum amount of locked memory!
         This might cause Ardour to run out of memory before your system runs
         out of memory. You can view the memory limit with 'ulimit -l', and it
         is normally controlled by /etc/security/limits.conf

Ardour6.9.0 (compilado usando 6.9 y versión de GCC 12.0.1 20220125 (Red Hat 12.0.1-0))
Ardour: [INFO]: Your system is configured to limit Ardour to 524288 open files
Ardour: [INFO]: Cargando el archivo de configuración del sistema /etc/ardour6/system_config
Ardour: [INFO]: Cargando el archivo de configuración de usuario /home/sebastian/.config/ardour6/config
Ardour: [INFO]: CPU vendor: AuthenticAMD
Ardour: [INFO]: AVX-capable processor
Ardour: [INFO]: AVX with FMA capable processor
Ardour: [INFO]: CPU brand: AMD Ryzen 3 3200G with Radeon Vega Graphics    
Ardour: [INFO]: Using AVX and FMA optimized routines
Ardour: [INFO]: Loading plugin meta data file /usr/share/ardour6/plugin_metadata/plugin_tags
Ardour: [INFO]: Loading plugin statistics file /home/sebastian/.config/ardour6/plugin_metadata/plugin_stats
Ardour: [INFO]: Cargando el archivo de configuración de interfaz de usuario predeterminado /etc/ardour6/default_ui_config
Ardour: [INFO]: Cargando el archivo de configuración de interfaz de usuario /home/sebastian/.config/ardour6/ui_config
Ardour: [INFO]: Loading 452 MIDI patches from /usr/share/ardour6/patchfiles
Gtk-Message: 17:32:59.736: Failed to load module "pk-gtk-module"
Ardour: [INFO]: Cargando el archivo de color /usr/share/ardour6/themes/dark-ardour.colors
Ardour: [INFO]: Loading ui configuration file /etc/ardour6/clearlooks.rc
Ardour: [INFO]: Loading bindings from /etc/ardour6/ardour.keys
Loading ui configuration file /etc/ardour6/clearlooks.rc
Found nothing along /home/sebastian/.config/ardour6/templates:/usr/share/ardour6/templates
error: failed to open file /usr/lib64/lv2/avldrums.lv2/manifest.ttl (No existe el fichero o el directorio)
lilv_world_load_file(): error: Error loading file `file:///usr/lib64/lv2/avldrums.lv2/manifest.ttl'
lilv_world_load_bundle(): error: Error reading file:///usr/lib64/lv2/avldrums.lv2/manifest.ttl
error: failed to open file /usr/lib64/lv2/ADLplug.lv2/manifest.ttl (No existe el fichero o el directorio)
lilv_world_load_file(): error: Error loading file `file:///usr/lib64/lv2/ADLplug.lv2/manifest.ttl'
lilv_world_load_bundle(): error: Error reading file:///usr/lib64/lv2/ADLplug.lv2/manifest.ttl
Scanning folders for bundled LV2s: /usr/lib64/ardour6/LV2
error: failed to open file /usr/lib64/lv2/avldrums.lv2/manifest.ttl (No existe el fichero o el directorio)
lilv_world_load_file(): error: Error loading file `file:///usr/lib64/lv2/avldrums.lv2/manifest.ttl'
lilv_world_load_bundle(): error: Error reading file:///usr/lib64/lv2/avldrums.lv2/manifest.ttl
error: failed to open file /usr/lib64/lv2/ADLplug.lv2/manifest.ttl (No existe el fichero o el directorio)
lilv_world_load_file(): error: Error loading file `file:///usr/lib64/lv2/ADLplug.lv2/manifest.ttl'
lilv_world_load_bundle(): error: Error reading file:///usr/lib64/lv2/ADLplug.lv2/manifest.ttl
Set cursor set to default

Comment 14 Nils Philippsen 2022-11-07 10:56:52 UTC
Hi, sorry for not spotting this earlier. A new major version of Ardour has been published in the meantime, I've submitted updates for it which should hit testing repositories soon. Would you please try if the problem persists in that version? Thanks!

Comment 15 Ben Cotton 2022-11-29 17:24:14 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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
'version' of '35'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 16 Ben Cotton 2022-12-13 15:59:44 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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

Comment 17 Red Hat Bugzilla 2023-09-18 04:28:35 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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