alsactl: relocation error: alsactl: symbol snd_tlv_parse_dB_info, version ALSA_0.9 not defined in file libasound.so.2 with link time reference

Bug #278615 reported by EdD
2
Affects Status Importance Assigned to Milestone
alsa-utils (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04

When attempting to store alsa's state to a config file the following error occurs and the config file is not updated:e

Command: sudo alsactl -F -f /etc/asound.state store
Expected Output: None - just to return to the shell command line.
Expected Result: /etc/asound.state is updated with the current alsa settings
Actual Output: alsactl: relocation error: alsactl: symbol snd_tlv_parse_dB_info, version ALSA_0.9 not defined in file libasound.so.2 with link time reference
Actual Result: /etc/asound.state remains unchanged

A quick google lead me to this post (http://ubuntuforums.org/showthread.php?t=811901) which shows that there were 2 different 'alsactl' executables present in my system. I renamed /usr/sbin/alsactl to /usr/sbin/alsactl.bak to ensure that the only one in my path was /sbin/alsactl and retried the command 'sudo alsactl -F -f /etc/asound.state store' - this time it was successful and the config file was updated.

This is the first time I have filed a bug report so I hope I have included all the necessary information - I did check but couldn't see any bugs reports containing this information so thought I should raise it in case it is a bug.

Cheers,

Edd

Revision history for this message
Daniel T Chen (crimsun) wrote :

Self-compiled alsa-utils does not qualify for a bug report. Ubuntu has not shipped /usr/sbin/alsactl (but instead /sbin/alsactl) since dapper.

Changed in alsa-utils:
status: New → Invalid
Revision history for this message
EdD (edd-mredd) wrote :

Hi Daniel,

It's now so long ago that I can't remember whether I compiled and installed the ALSA source before experiencing this issue - from your comment I presume that I must have done if Ubuntu hasn't shipped like the since dapper. I'm afraid I can't even check now since I am now running Intrepid on the machine which had the problem.
So I'm guessing that there's not much more which can be done under this bug report - if so please feel free to close it as far as I am concerned.

Cheers,

Edd

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.