Ubuntu
alsa-utils package

asoundconf crashed with ValueError in set_default_card()

Bug #263116 reported by Jordan
This bug report is a duplicate of:  Bug #271899: Bug in asoundconf. Edit Remove
56
Affects Status Importance Assigned to Milestone
alsa-utils (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: alsa-utils

I noticed after recent updates in Intrepid ( might have been after the switch from 2.6.26 to 2.6.27 ) that sound no longer works, I tried alsamixer but got an error saying something along the lines of 'file "default" not found' ( I no longer get the error and unfortunately did not save it ) I assumed that this meant that there was not defuault card set so I did "asoundconf list" which showed "Intel" then "asoundconf set-default-card Intel" which caused this crash.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/asoundconf
InterpreterPath: /usr/bin/python2.5
Package: alsa-utils 1.0.17-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/asoundconf set-default-card Intel
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
PythonArgs: ['/usr/bin/asoundconf', 'set-default-card', 'Intel']
SourcePackage: alsa-utils
Title: asoundconf crashed with ValueError in set_default_card()
Uname: Linux 2.6.27-2-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Jordan (jordanu) wrote :
Revision history for this message
vista killer (vistakiller) wrote :

i confirm this bug. Asoundconf always crash

Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :

Me too. When trying to set my Audigy2 Zs Pcmcia, I get the following Output:

Traceback (most recent call last):
  File "/usr/bin/asoundconf", line 430, in <module>
    exit_code(set_default_card(sys.argv[2]))
  File "/usr/bin/asoundconf", line 348, in set_default_card
    (j, k) = sep.split(i)
ValueError: need more than 1 value to unpack

Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :

Same here

# asoundconf list

Names of available sound cards:
ICH6

# asoundconf set-default-card ICH6

Traceback (most recent call last):
  File "/usr/bin/asoundconf", line 430, in <module>
    exit_code(set_default_card(sys.argv[2]))
  File "/usr/bin/asoundconf", line 348, in set_default_card
    (j, k) = sep.split(i)
ValueError: need more than 1 value to unpack

Revision history for this message
C de-Avillez (hggdh2) wrote :

Also got hit by it. Digging in I found the /usr/share/alsa/alsa.conf was shipped with two keywords separated by a tab (\t) instead of spaces:

 - defaults.pcm.file_format
 - defaults.pcm.file_truncate

It happens that 'sep.split()' will not recognise \t as a valid separator, so the error. This gives us two options to resolve the issue:

(1) update the libasound2 package: update /usr/share/alsa/alsa.conf, replacing the \t by spaces on the affected lines; this can be done manually right now to bypass the issue.

(2) update the alsa-utils package: fix asoundconf so that whitespace will be accepted as a separator. I personally think this is the best option but I do not know what the maintainers would like.

Setting as triaged, Medium importance -- does not seem to hit everybody (I do not know why), but it is probably someting that should be milestoned.

Changed in alsa-utils:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
C de-Avillez (hggdh2) wrote :

ah, forgot:

libasound2: 1.0.17a-0ubuntu2-ppa1 (Luke Yeavich's)
alsa-utils: 1.0.17-0ubuntu1

Revision history for this message
spotter (spotter-yucs) wrote :

bug still exists. bad as get notified to run asoundconf on upgrade.

hggdh's fix seems to fix it. unsure why it hasn't been fixed.

Revision history for this message
vista killer (vistakiller) wrote :

i have no more problem with this. I think the last update fix the bug

Revision history for this message
afriseun (carel-kenweb) wrote :

Got the same bug after updating when adding intrepid repositry.
Adding alsa-utils as per hggdh's post fixed my problem.

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

Other bug subscribers

Remote bug watches

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