Bug 4788 - alsactl restore - код ошибки
: alsactl restore - код ошибки
Status: CLOSED WORKSFORME
: Sisyphus
(All bugs in Sisyphus/alsa-utils)
: unstable
: all Linux
: P5 major
Assigned To:
:
:
:
:
: 3459
  Show dependency tree
 
Reported: 2004-07-14 13:06 by
Modified: 2006-12-17 23:13 (History)


Attachments
alsa-utils-1.0.5-err-restore.patch (378 bytes, patch)
2004-07-14 13:42, Anton Farygin
no flags Details | Diff


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2004-07-14 13:06:40
в случае невозможности восстановить значения уровня громкости код возврата
alsactl равен 0, хотя должен от него отличаться (ошибка выполнения).
------- Comment #1 From 2004-07-14 13:42:14 -------
Created an attachment (id=490) [details]
alsa-utils-1.0.5-err-restore.patch

Патч, исправляющий это для alsa-utils-1.0.5
------- Comment #2 From 2004-07-14 14:41:31 -------
#alsa:

<gvy> halo
--> rider (~rider@altlinux.balabanovo.ru) has joined #alsa
<crimsun_> 'lo
<gvy> is there anyone who knows alsa-utils interdependencies relating return codes?
<gvy> there's a question whether thispatch breaks anything:
<gvy> https://bugzilla.altlinux.org/attachment.cgi?id=490&action=view
<gvy> it's for alsactl not to return 0 on "No state is present for card %s" error
<gvy> or "whether something relies on this behaviour"
<crimsun_> the err = 0 assignment is there to suppress the message
<crimsun_> let me look more closely
<gvy> thanks for the time
<crimsun_> yeah, it looks like you need to leave err = 0 assignment in there
<gvy> umm... but what relies upon it?
<gvy> rider, can you explain your problem with zero return code? (maybe
different understanding of the case being an error or not)
<rider> gvy: howto detect, saved or no values for card with id to
/etc/asound.state ?
<gvy> errr... how to differ between "we-have-saved-state" and
"no-state-for-this-card"?
<rider> gvy: ugu
<rider> gvy: only for card with id (for example: alsactl restore 0, or alsactl
restore 1... and more)
<crimsun_> I'm not sure why you'd want to remove that line
<crimsun_> according to Takashi's commit, you have the assignment because you
see a condition where you can't grab state for the card, so you'll fall out
regardless.
<crimsun_> if you have more questions, please direct them to alsa-devel
<gvy> crimsun_, to handle situation where no settings are available? (actually
I'm maintaining alsa userspace in ALT Linux, and rider maintains hotplug)
<crimsun_> either Jaroslav or Takashi can clarify the intent of that commit
<gvy> so should we mail them directly or via alsa-devel?
<crimsun_> gvy: where none are available seems to be the case. Use the
alsa-devel list.
<gvy> crimsun_, thanks!
<crimsun_> np

т.е. надо спросить tiwai@ в alsa-devel@...
------- Comment #3 From 2005-06-20 18:37:10 -------
Спросил ?
------- Comment #4 From 2005-06-23 13:52:51 -------
А меня там нет (vsu, а ты есть?).

Проверь 1.0.9, хотя подозреваю, что нифига не трогали.
------- Comment #5 From 2005-10-19 17:19:30 -------
надо всё-таки спросить их перед тем, как переворачивать.

Серёж, так ты подписан на alsa-devel@ или нет?
------- Comment #6 From 2006-04-05 13:15:52 -------
Так прикладывать или нет?  Мож в Daedalus забросить такую сборку и попросить
народ погонять?
------- Comment #7 From 2006-04-05 14:19:20 -------
Забрось. ты мантейнер - тебе решать ;)
------- Comment #8 From 2006-04-05 14:46:56 -------
Подновил, собирается.
------- Comment #9 From 2006-04-05 14:57:24 -------
1.0.11-alt0.4.1 уехало в Daedalus
------- Comment #10 From 2006-10-16 21:35:42 -------
Судя по отсутствию фидбэка -- никому оно уже не нужно... (если неправ,
test&report pls)