Bug 4788 - alsactl restore - код ошибки
Summary: alsactl restore - код ошибки
Alias: None
Product: Sisyphus
Classification: Development
Component: alsa-utils (show other bugs)
Version: unstable
Hardware: all Linux
: P5 major
Assignee: Michael Shigorin
QA Contact: qa-sisyphus
Depends on:
Blocks: 3459
  Show dependency tree
Reported: 2004-07-14 13:06 MSD by Anton Farygin
Modified: 2006-12-17 23:13 MSK (History)
3 users (show)

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Farygin 2004-07-14 13:06:40 MSD
в случае невозможности восстановить значения уровня громкости код возврата
alsactl равен 0, хотя должен от него отличаться (ошибка выполнения).
Comment 1 Anton Farygin 2004-07-14 13:42:14 MSD
Created attachment 490 [details]

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

<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
<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
<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 Anton Farygin 2005-06-20 18:37:10 MSD
Спросил ?
Comment 4 Michael Shigorin 2005-06-23 13:52:51 MSD
А меня там нет (vsu, а ты есть?).

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

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