Ticket #180 (closed defect: fixed)

Opened 2 years ago

Last modified 17 months ago

Alsa name is not set when calling mididings throuhg gladish

Reported by: http://orlammd.pip.verisignlabs.com/ Owned by: -
Priority: major Milestone: 1
Keywords: Cc:

Description

When running mididings through gladish (in a term or not) I get the following error: dlvsym("snd_seq_set_client_name", "ALSA_0.9") failed.

And the mididings alsa name isn't set, which leads the client to be called client-XXX, and the bindings are lost, as it's not always the same name.

If I run gladish, then launch mididings from an outside term, there's no problem at all.

Change History

Changed 2 years ago by http://nedko.arnaudov.name/

After dlvsym() failure, dlerror() returns NULL string. LD_PRELOAD is "libalsapid.so". The libalsapid.so library constructor is called twice.

Changed 2 years ago by http://nedko.arnaudov.name/

ladishd outputs to its stdout/stderr

ERROR: ld.so: object 'libalsapid.so' from LD_PRELOAD cannot be preloaded: ignored.

Changed 2 years ago by http://nedko.arnaudov.name/

  • status changed from new to closed
  • resolution set to fixed

Changed 17 months ago by http://nedko.arnaudov.name/

  • milestone changed from 0.4 (preview 4) to 1
Note: See TracTickets for help on using tickets.