Description of problem: The fluidsynth-dssi plugin is not functional from Rosegarden as it will not allow sound fonts to be loaded or voices to be selected. Other dssi plugins work correctly. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Start qjackctl 2. Start Rosegarden 3. For any track, in Track Parameters panel on left select Device -> Synth plugin 4. In Instrument parameters press "<no synth>" button 5. A "Synth Plugin" dialog will appear. As "Plugin:" select FluidSynth DSSI plugin 6. Try to press "Editor" button at bottom of dialog Actual results: Nothing happens Expected results: A dialog appears that allows you to load and select Soundfonts Additional info: 1. In the past this error could be fixed by editing /etc/hosts and removing the ::1 line. However this no longer works. 2. Tried to test fluidsynth-dssi from command line without Rosegarden: jack-dssi-host fluidsynth-dssi.so jack-dssi-host: Warning: DSSI path not set jack-dssi-host: Defaulting to "/usr/local/lib64/dssi:/usr/lib64/dssi:/usr/local/lib/dssi:/usr/lib/dssi:/home/kecskebak/.dssi" Cannot lock down 107335194 byte memory area (Cannot allocate memory) jack-dssi-host: OSC URL is: osc.udp://localhost.localdomain:15662/dssi/fluidsynth-dssi/FluidSynth-DSSI/chan00 host: Ready fsd-gui starting (pid 1933)... Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. liblo error: lo_send, lo_message_add, or lo_message_add_varargs called with mismatching types and data at FluidSynth-DSSI_gtk.c:350, exiting.
This bug appears to be a problem with the latest version of liblo - liblo 0.27 - rather than with Fluidsynth. It has been reported on the Archlinux bugtracker here: https://bugs.archlinux.org/task/35841 According to that report problem with this version of liblo appears to be x86_64 only.
I can confirm "yum downgrade liblo" fixes the issue. Therefore the problem is an issue with liblo 0.27.
Hi, thanks for the bug report. Did you (or anyone) by any chance report this issue to upstream liblo?
Hi Orcan! Yes, I've filed a bug upstream: https://sourceforge.net/p/liblo/bugs/32/ All the best,Dave
Thanks Dave. Much appreciated
(In reply to Orcan Ogetbil from comment #5) I just had the following reply from Stephen Sinclair upstream: "Hi, this is a known problem. Should be fixed in master branch. There is no 2.7.1, only 0.27, but perhaps I should do a bug-fix release soon."
Thank you Dave, for your work. Let us wait a couple days. If they do not make a release, I will backport the fix from the trunk to the RPM package.
Seems to be affecting sooperlooper as well. See bug 994850
I've just been mailed by the upstream maintainter - Stephen Sinclair: "Can you please verify that this is fixed in master?" I don't know how to do this, but if Orcan can make an rpm using upstream master I'll be very happy to test it.
Hi Dave, Sorry for the late response. Here is an RPM using the latest git checkout. Could you take it from koji and give it a try when you get a chance? http://koji.fedoraproject.org/koji/taskinfo?taskID=5892275 Thanks!
Thanks for getting back to me. I tested the liblo-0.27-2.1.fc19.x86_64.rpm package in koji this morning and sadly it didn't work. Dialog boxes still failed to appear for DSSI plugins in Rosegarden.
That's my experience as well... So the liblo is not fixed after all. Maybe we should bump the epoch in the RPM and downgrade liblo in Fedora.
According to the SF ticket, the issue is resolved by the recent fix. From what I observe, it works on my machine. Could you verify http://koji.fedoraproject.org/koji/taskinfo?taskID=5899142
Works for me too!!! Many, many thanks for your help to get this fixed Orcan. I was worried that soon I wouldn't be able to use Rosegarden so I'm very relieved.
Great! Please keep using this build in the short run. I will submit a proper package as an update, hopefully in a week (I have two trips lined up, so I won't have time very soon).
Will do - enjoy your trips, and thanks again!
liblo-0.27-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/liblo-0.27-3.fc20
liblo-0.27-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/liblo-0.27-3.fc19
Package liblo-0.27-3.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing liblo-0.27-3.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20121/liblo-0.27-3.fc20 then log in and leave karma (feedback).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
liblo-0.27-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
liblo-0.27-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.