FS#35841 - [liblo] 0.27-1 error while loading DSSI plugins.

Attached to Project: Arch Linux
Opened by Rasto (kerny) - Tuesday, 18 June 2013, 07:31 GMT
Last edited by Ray Rashif (schivmeister) - Wednesday, 12 February 2014, 07:05 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ray Rashif (schivmeister)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

With liblo 0.27-1 I get an error while loading DSSI plugins. Version 0.26-1 works without a problem.

For example with hexter I get:
liblo error: lo_send, lo_message_add, or lo_message_add_varargs called with mismatching types and data at
gui_main.c:283, exiting.

Additional info:
* package version(s)
0.27-1
* config and/or log files etc.


Steps to reproduce:

[kerny@arch ~]$ hexter

jack-dssi-host: OSC URL is:
osc.udp://localhost:19710/dssi/hexter/hexter/chan00

host: Ready
hexter_gtk starting (pid 2280)...
liblo error: lo_send, lo_message_add, or lo_message_add_varargs called with mismatching types and data at
gui_main.c:283, exiting.
This task depends upon

Closed by  Ray Rashif (schivmeister)
Wednesday, 12 February 2014, 07:05 GMT
Reason for closing:  Fixed
Additional comments about closing:  Newer liblo released with sobump, no apparent bugs, all link-level packages rebuilt.
Comment by Ray Rashif (schivmeister) - Sunday, 23 June 2013, 19:46 GMT
I'm not able to reproduce this, but then again I'm on i686. I will need one more reproduction from an x86_64 user before I can confirm this as upstream, most probably something related to this: http://sourceforge.net/mailarchive/message.php?msg_id=31087188

So let's wait a couple days and see what the developer does. I'll report upstream if nothing progresses.
Comment by Ray Rashif (schivmeister) - Wednesday, 03 July 2013, 20:26 GMT
Hi Rasto

Could you get the development version of liblo and see if you can reproduce the problem?
Comment by Rasto (kerny) - Sunday, 07 July 2013, 20:06 GMT
I just tried with development version, the bug is still there.

with hexter I get:

jack-dssi-host: OSC URL is:
osc.udp://localhost:16917/dssi/hexter/hexter/chan00

host: Ready
hexter_gtk starting (pid 5772)...
liblo error: lo_send, lo_message_add, or lo_message_add_varargs called with mismatching types and data at
gui_main.c:283, exiting.
Comment by Ray Rashif (schivmeister) - Sunday, 07 July 2013, 21:09 GMT
  • Field changed: Category (Packages: Extra → Upstream Bugs)
  • Field changed: Severity (Low → Medium)
Alright, I think you would be a better fit to file the bug report since you can reproduce the problem:

http://sourceforge.net/p/liblo/bugs/

Remember to cite the last known working version. Please do link the report here, thanks.
Comment by Ray Rashif (schivmeister) - Saturday, 26 October 2013, 14:02 GMT
Upstream has indeed relegated their stable version to the previous release, so will be forcing a downgrade. Rebuilt both dssi and liblo, will move from staging to extra.

"(Several bugs found on 64-bit, please don't use in production. Maintainers of projects that use liblo, please test and report any bugs found.)"

From http://liblo.sourceforge.net/ about 0.27 (thanks to kerny for the heads-up)
Comment by Ray Rashif (schivmeister) - Saturday, 26 October 2013, 14:49 GMT
Please test and confirm that things work as before.
Comment by speps (archspeps) - Saturday, 26 October 2013, 19:03 GMT
No guys, this is not a bug.
Hexter is explicitly linked against liblo, so @Rasto, to solve your starting issue with hexter you just need to _rebuild_ it against liblo 0.27.

No downgrade was really needed here.

@Ray, please revert all changes. P.S. next time please assign this kind of bugs also to myself ;)
Comment by Ray Rashif (schivmeister) - Saturday, 26 October 2013, 19:43 GMT
Speps, I can't possibly assign you to reports for [extra], but I'll be sure to add you to the notify list next time, thanks. Anyway, dssi was already rebuilt after your previous notice before 10/10: https://projects.archlinux.org/svntogit/packages.git/log/trunk?h=packages/dssi&showmsg=1

Would have been good if I had some feedback. Anyway, downgrade has been pushed, and upstream has turned 0.27 into a testing release from a stable one due to possibly unrelated issues (compare release notes and front page warning).

For the sake of demystifying this bug report, run dssi 1.1.1-4 and liblo 0.27 along with a rebuilt hexter if you haven't updated yet. The issue was not dssi, but hexter itself. Just to have closure -- I'm not reverting the downgrade unless there's significant demand for 0.27.
Comment by speps (archspeps) - Saturday, 26 October 2013, 23:50 GMT
You're right Ray, thanks. The notify list is a good solution ;)

I knew you did already rebuild dssi time ago as it was necessary to let any executable (like jack-dssi-host) linked against liblo to work. In the same way hexter, that uses liblo directly, needed a rebuild in order to work against 0.27. There's a discussion on liblo ML dealing with this issue, and it is well explained [1].

The issue itself seems harmless, but Steve decided to revert his last stable to 0.26 while it was not deeply clear.
Btw, since upstream suggest to get sticky on 0.26, I'm ok in leaving things as they are now.

I have no reason for requesting an upgrade to 0.27 (unless the wish of not rebuilding again all I have on my machine depending on liblo ;))

[1] http://sourceforge.net/mailarchive/forum.php?thread_name=A4C0D349-C7C6-48C1-A866-FB5D09AF080D%40osculator.net&forum_name=liblo-devel
Comment by Ray Rashif (schivmeister) - Sunday, 27 October 2013, 10:03 GMT
Thanks, that makes it all clearer. In normal cases, only a known change in API/ABI (soname bump) would require a rebuild. In this case, though, there's an issue specific to x64 (unknown change to API?). All packages built against liblo x86_64 needs to be rebuilt, is that correct?

The following packages in [extra] link against liblo:

ardour
dssi
ecasound
rosegarden

And in [community]:

dssi-vst
qtractor
xjadeo

Of those: rosegarden, qtractor and xjadeo were updated after liblo 0.27 was made available. Chances are these three _may_ also need to be rebuilt.
Comment by Allan McRae (Allan) - Wednesday, 12 February 2014, 06:33 GMT
This looks fixed. Can the bug be closed?
Comment by Ray Rashif (schivmeister) - Wednesday, 12 February 2014, 07:04 GMT
Yes, thanks for the bump, it is a leftover.

Loading...