Bug 751056 - Ardour crashes at startup
Summary: Ardour crashes at startup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: liblrdf
Version: 16
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Anthony Green
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 752521 753678 753869 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-03 11:29 UTC by Paolo Patruno
Modified: 2011-11-19 05:56 UTC (History)
10 users (show)

Fixed In Version: liblrdf-0.5.0-1.fc16
Clone Of:
Environment:
Last Closed: 2011-11-19 05:56:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
librdf src rpm (342.39 KB, text/plain)
2011-11-03 14:31 UTC, Paolo Patruno
no flags Details

Description Paolo Patruno 2011-11-03 11:29:44 UTC
Description of problem:
ardour crash at startup:
raptor_general.c:240:raptor_init: fatal error: raptor_init() failed

problem reported to main stream
http://tracker.ardour.org/view.php?id=4437

Comment 1 Orcan Ogetbil 2011-11-03 11:49:37 UTC
Hi Paolo,
Did you configure your jack according to
   /usr/share/doc/jack-audio-connection-kit-1.9.7/README.Fedora
?

Comment 2 Paolo Patruno 2011-11-03 12:41:50 UTC
I have jackd running and working.
I do not think the problem derive from a jackd misconfiguration.

The error is in globals.cc in lrdf_init() :

ARDOUR::init (bool use_vst, bool try_optimization)
{
	(void) bindtextdomain(PACKAGE, LOCALEDIR);

	setup_enum_writer ();

	// allow ardour the absolute maximum number of open files
	lotsa_files_please ();

	lrdf_init();
	Library = new AudioLibrary;

	BootMessage (_("Loading configuration"));

	Config = new Configuration;

	if (Config->load_state ()) {
		return -1;
	}

I think that lrdf ( https://github.com/swh/LRDF ) is used to read LADSPA plugins ...
I am going to check more.
Paolo

Comment 3 Paolo Patruno 2011-11-03 14:29:36 UTC
rebuilding librdf with the last git version ( liblrdf-0.5.0 ) solve the problem.
the src rpm is attached.

Paolo

Comment 4 Paolo Patruno 2011-11-03 14:31:31 UTC
Created attachment 531566 [details]
librdf src rpm

Comment 5 Orcan Ogetbil 2011-11-03 23:51:34 UTC
I wonder if that is because of a faulty ladspa plugin. Could you try to uninstall your ladspa plugins to find which one triggers the crash?

Comment 6 Paolo Patruno 2011-11-04 08:01:34 UTC
Do you cannot reproduce the problem ?

I have only this installed:
ladspa.x86_64                        1.13-7.fc15                         @fedora
"This package contains the example plug-ins and tools from the LADSPA SDK."

 ls /usr/lib64/ladspa/
amp.so  delay.so  filter.so  noise.so  sine.so

I have the crash with a fresh new user so it do not depends from local user files.

Comment 7 Orcan Ogetbil 2011-11-04 11:47:37 UTC
No I cannot reproduce the problem. I made the RPM file, I think I would have noticed if it crashed at start. 

There are a bunch of ladspa plugins we have packaged for Fedora, but apparently you only have the base ladspa package installed, which comes with a minimal set of sample plugins in the /usr/lib64/ladspa/ directory.

Unfortunately, we cannot just update a library to trunk version in a stable branch of Fedora. However we can backport a fix from the trunk, but we need to know what was broken and how it is fixed, so we can make a patch.

Comment 8 Paolo Patruno 2011-11-04 17:53:27 UTC
> but we need to know what was broken and how it is fixed, so we can make a patch

I I think it will not so easy, if I understand well liblrdf-0.4 use raptor; liblrdf-0.5 use raptor2.

take a look at this on the lasts comments:
http://ardour.org/node/4454
azmeuk have the same problem, so I am not alone !

Paolo

Comment 9 Éloi Rivard 2011-11-06 14:11:49 UTC
Hi,
I confirm that I have the following issue trying to launch ardour with a Fedora 16 64bits just installed. It runs on a Dell Latitude 6520, with a Mackie ProFX8.

azmeuk@localhost:~$ ardour2 
Ardour 2.8.12
   (built using 10144 and GCC version 4.6.1 20110908 (Red Hat 4.6.1-9))
... ....
theme_init() called from internal clearlooks engine
/usr/share/themes/Adwaita/gtk-2.0/gtkrc:80: error: unexpected identifier `colorize_scrollbar', expected character `}'
Chargement du fichier de configuration de l'ihm par défaut /etc/ardour2/ardour2_ui_default.conf
Loading ui configuration file /etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
ardour: [INFO]: Ardour sera limité à 4096 fichiers ouverts
raptor_new_uri_for_rdf_concept called with Raptor V1 world object
raptor_general.c:240:raptor_init: fatal error: raptor_init() failedAbandon (core dumped)
azmeuk@localhost:~$

Comment 10 Manuel Traut 2011-11-09 18:40:56 UTC
*** Bug 752521 has been marked as a duplicate of this bug. ***

Comment 11 Manuel Traut 2011-11-09 18:52:35 UTC
ardour works also well for me if i use the liblrdf-0.5 (build from the source rpm, attached by Paolo).

Comment 12 david m 2011-11-09 21:30:56 UTC
Hi,

I have the same problem with Fedora 16 (32 bit) xfce spin. Ardour crashes at start up with:

Ardour 2.8.12
   (built using 10144 and GCC version 4.6.1 20110908 (Red Hat 4.6.1-9))
Copyright (C) 1999-2008 Paul Davis
Some portions Copyright (C) Steve Harris, Ari Johnson, Brett Viren, Joel Baker

Ardour comes with ABSOLUTELY NO WARRANTY
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is free software, and you are welcome to redistribute it 
under certain conditions; see the source for copying conditions.
theme_init() called from internal clearlooks engine
/usr/share/themes/Adwaita/gtk-2.0/gtkrc:80: error: unexpected identifier `colorize_scrollbar', expected character `}'
loading default ui configuration file /etc/ardour2/ardour2_ui_default.conf
Loading ui configuration file /etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
ardour: [INFO]: Ardour will be limited to 4096 open files
raptor_new_uri_for_rdf_concept called with Raptor V1 world object
Segmentation fault (core dumped)

It worked fine in Fedora 15, never had a problem.

Comment 13 Orcan Ogetbil 2011-11-10 02:29:32 UTC
Okay, I changed the component to liblrdf, since it contains the faulty code.

Did anyone contact the liblrdf developers yet to ask when they are planning to release 0.5.0?

Comment 14 david m 2011-11-10 10:14:41 UTC
Hi,

liblrdf in F16 is the same package as fedora 15, how could the same package that worked well in F15 cause a crash with the F16 version of Ardour2? It's all very strange.

On the face of it (and I am no developer), I would have to say the evidence points to changes in the F16 ardour package that don't work with liblrdf-0.4.

Comment 15 david m 2011-11-10 12:16:02 UTC
Hi Anthony,

Any ideas on when I can use ardour again? Or can you suggest a fix in the mean time?

Comment 16 Éloi Rivard 2011-11-10 12:32:09 UTC
(In reply to comment #14)
> Hi,
> 
> liblrdf in F16 is the same package as fedora 15, how could the same package
> that worked well in F15 cause a crash with the F16 version of Ardour2? It's all
> very strange.


Well, if liblrdf hasn't changed since Fedora 15, maybe Ardour2 did, and now uses some faulty code of liblrdf it didn't use before.

Comment 17 david m 2011-11-11 09:14:44 UTC
Hi,

There is an upgrade for Ardour that came out yesterday and I was able to run it from within it's own directory -so not using the broken F16 package.

It works ok for the moment, but I noticed that it segfaults when shutdown.

Hopefully The F16 package should be up and running soon.

Comment 18 Juan 2011-11-14 19:35:40 UTC
*** Bug 753869 has been marked as a duplicate of this bug. ***

Comment 19 Juan 2011-11-14 19:44:18 UTC
I can confirm that librdf 0.5 fixes the problem.

Comment 20 Orcan Ogetbil 2011-11-14 21:14:19 UTC
Hi all, just a quick update: I contacted the liblrdf developers, and accordingly the liblrdf-0.5.0 on github is considered stable. I will file an update this week (hopefully tonight), and then you guys can test and report.

david m, where is the new ardour upgrade? Their website still shows the 2.8.12 version.
   http://ardour.org/download

Comment 21 Fedora Update System 2011-11-15 02:32:48 UTC
liblrdf-0.5.0-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/liblrdf-0.5.0-1.fc16

Comment 22 david m 2011-11-15 07:20:59 UTC
Hi,

The update was posted on freecode (freshmeat) and I downloaded Ardour_x86-2.8.12_10146, to see if their version crashed too. I don't know if that's an upgrade or Freecode are a bit slow. 

The above binary package doesn't crash at startup and works ok-so it would be interesting to know what liblrdf version they are using.

I take it, it will be a while before there is an rpm for liblrdf-0.5.

Comment 23 david m 2011-11-15 07:43:02 UTC
Hi,

Ok got it, downloaded and installed liblrdf-0.5 i686 rpm from the above link and ardour now starts ok and works ok. Started ardour2 from command line and there is only one gtk warning message:

Gtk-WARNING **: EnableTranslation: missing action EnableTranslation

Comment 24 Daniel Karlsson 2011-11-15 08:48:56 UTC
*** Bug 753678 has been marked as a duplicate of this bug. ***

Comment 25 david m 2011-11-15 11:04:33 UTC
Hi,

A few people posted back-you can download the F16 liblrdf-0.5 rpm from the Fedora Update System comment link above-it sorted the problem for me.

Comment 26 Daniel Karlsson 2011-11-15 15:01:20 UTC
Confirming that Ardour is up and running with the F16 liblrdf-0.5 rpm on my system.

Comment 27 Fedora Update System 2011-11-16 00:29:30 UTC
Package liblrdf-0.5.0-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing liblrdf-0.5.0-1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-15955
then log in and leave karma (feedback).

Comment 28 Fedora Update System 2011-11-19 05:56:01 UTC
liblrdf-0.5.0-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


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