skype is terminated immediately after start in jaunty

[pierreblueher]

/usr/bin/skype.real: relocation error: /usr/bin/skype.real: symbol snd_pcm_hw_params_get_channels_min, version ALSA_0.9.0rc4 not defined in file libasound.so.2 with link time reference

[benste (benste)]

Mine starts fine but doesn't handle pulseaudio in a right way, it always mutes the internal mic

benste@VAIO-FE31M:~$ skype
ALSA lib pcm_bluetooth.c:1569:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_bluetooth.c:1569:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_bluetooth.c:1569:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_bluetooth.c:1569:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_bluetooth.c:1569:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_bluetooth.c:1569:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)

[John Dong (jdong)]

The original bug reporter's error is caused by an API change in ALSA 1.0.19 (using TheMuso's PPA perhaps)?

[pierreblueher (pierre-blueher)]

yeah thats right. unfortunately i cannot remove the installations without removing other crucial parts of the system. is there another possibility?

>The original bug reporter's error is caused by an API change in ALSA
>1.0.19 (using TheMuso's PPA perhaps)?
>
>--
>skype is terminated immediately after start in jaunty
>https://bugs.launchpad.net/bugs/351070
>You received this bug notification because you are a direct subscriber
>of the bug.
>
>Status in Medibuntu: New
>
>Bug description:
>/usr/bin/skype.real: relocation error: /usr/bin/skype.real: symbol
>snd_pcm_hw_params_get_channels_min, version ALSA_0.9.0rc4 not defined in file
>libasound.so.2 with link time reference

[John Dong (jdong)]

You must either force-downgrade of all sound related packages to jaunty, or wait for Skype to release updated binaries against Alsa 1.0.19 I'm afraid.

[sgtbug (sgtbug)]

will the oss version work then?

[Mingming Ren (portis25)]

There's a workaround: download 32bit libasound2, libasound2-plugins packages, unpack them, move the libs to the corresponding lib32 directory. It works for me.

[Maxim Levitsky (maximlevitsky)]

This issue seems very strange.

If I download alsa 1.0.19, but don't install its 32 bit compat library, but directly unpack it and put libasound there, everyting works.

I suspect that dpkg strips out some symbols from this library?

[Ludovico Cavedon (cavedon)]

The solution is define USE_VERSIONED_SYMBOLS when compiling libasound.

http://thread.gmane.org/gmane.linux.alsa.devel/61476

[Jared Wiltshire (jaredwiltshire)]

@Maxim Levitsky
The libasound.so.2.0.0 file in the libasound2 i386 package has the symbols in it. However the libasound.so.2.0.0 from the lib32asound amd64 package doesnt have the symbols.

[Rolf Leggewie (r0lf)]

The problem is triggered from mixing several sources of packages. Several hints on what needs to be done were given. This isn't really an issue the packagers can do anything about.