this post was submitted on 06 Feb 2025
10 points (85.7% liked)
techsupport
2580 readers
9 users here now
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Run it in a terminal and pipe the output to a text file.
~/> ardour > output.log
Something like above. That will give you the text output up to the crash and hopefully have useful information like an error code or fault warning.
Will this work even if it just freezes and technically never really crashes? Thanks this might be the light at the end of the tunnel. Would be grand if that gives the hint on how to make this work!
Yes, the output is continuous as it runs and if it crashes it just stops putting out data. The cool thing is you can capture the error codes and back end details so you can often gain an insight to what is failing and why. It may have something like a device not being ready or a library failing to load, but because the range of possible errors is so large the developers may not have a GUI way of showing them. I would recommend taking each of the last few lines one at a time and searching them in your favourite search engine with ardour at the front, like "ardour ERR: glibc not found" or something like that. If someone has the same issue they may have found a solution that works for you.