+++ This bug was initially created as a clone of Bug #994832 +++

Version-Release number of selected component:
alsa-utils-1.0.27.2-2.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf --initfile=/lib/alsa/init/00main rdaemon
crash_function: _IO_vfprintf_internal
executable:     /usr/sbin/alsactl
kernel:         3.10.4-300.fc19.x86_64
runlevel:       unknown
uid:            0

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 _IO_vfprintf_internal at vfprintf.c:1635
 #1 ___vsnprintf_chk at vsnprintf_chk.c:63
 #2 vsnprintf at /usr/include/bits/stdio2.h:77
 #3 syslog_ at utils.c:112
 #4 cerror_ at utils.c:154
 #5 set_control at state.c:1325
 #6 set_controls at state.c:1512
 #7 load_state at state.c:1746

--- Additional comment from david on 20130808T05:44:28 ---

Created attachment 784221 [details]
File: backtrace

--- Additional comment from david on 20130808T05:44:30 ---

Created attachment 784222 [details]
File: cgroup

--- Additional comment from david on 20130808T05:44:32 ---

Created attachment 784223 [details]
File: core_backtrace

--- Additional comment from david on 20130808T05:44:34 ---

Created attachment 784224 [details]
File: dso_list

--- Additional comment from david on 20130808T05:44:36 ---

Created attachment 784225 [details]
File: environ

--- Additional comment from david on 20130808T05:44:40 ---

Created attachment 784226 [details]
File: exploitable

--- Additional comment from david on 20130808T05:44:43 ---

Created attachment 784227 [details]
File: limits

--- Additional comment from david on 20130808T05:44:46 ---

Created attachment 784228 [details]
File: maps

--- Additional comment from david on 20130808T05:44:48 ---

Created attachment 784229 [details]
File: open_fds

--- Additional comment from david on 20130808T05:44:50 ---

Created attachment 784230 [details]
File: proc_pid_status

--- Additional comment from david on 20130808T05:44:52 ---

Created attachment 784231 [details]
File: var_log_messages

--- Additional comment from superquad.vortex2 on 20130921T01:07:13 ---

\070", '\000' <repeats 43 times>, "`\301\326\037\377\177\000\000P\301\326\037\377\177\000\000n\306+\312\070\000\000\000"...
#4  0x000000000040b2b7 in cerror_ (fcn=fcn@entry=0x412708 <__FUNCTION__.9591> "set_control", line=line@entry=1325, cond=<optimized out>, fmt=fmt@entry=0x412860 "failed to obtain info for control #%d (%s)") at utils.c:154
        ap = {{gp_offset = 16, fp_offset = 0, overflow_arg_area = 0x0, reg_save_area = 0x3f5df7a6c0}}
#5  0x00000000004098d1 in set_control (handle=0x98d550, control=0x982140, maxnumid=maxnumid@entry=0x7fff1fd6c83c, doit=doit@entry=1) at state.c:1325
        ctl = 0x7fff1fd6c0e0
        info = 0x7fff1fd6bfc0
        i = <optimized out>
        next = 0x9821f8
        numid1 = <optimized out>
        iface = SND_CTL_ELEM_IFACE_MIXER
        iface1 = <optimized out>
        name1 = <optimized out>
        numid = 3
        type = <optimized out>
        count = <optimized out>
        device = 0
        device1 = <optimized out>
        subdevice = 0
        subdevice1 = <optimized out>
        name = 0x982240 "Analog Mic Boost Capture Enum"
        index1 = <optimized out>
        index = 0
        value = 0x982300
        comment = 0x982370
        idx = <optimized out>
        err = -2
        set = <optimized out>
        id = 0x9820d0 "3"
        __FUNCTION__ = "set_control"


post the output of alsa-info.sh and  asound.state

--- Additional comment from rdieter.edu on 20131206T18:50:41 ---

Created attachment 833703 [details]
alsa-info.sh output

--- Additional comment from rdieter.edu on 20131206T18:51:46 ---

Created attachment 833714 [details]
asound.state as requested

--- Additional comment from bitlord0xff on 20131217T00:29:33 ---

I maybe commented on a wrong bug ( bug #1018513 ), but saw a segfault of alsactl in dmesg, and found same version of alsa-utils (but probably different problem), later tried to play with systemctl start/stop/restart alsa-{store,restore,state}.service and state triggered this crash, it was shown in abrt, and when I tried to report it:

--- Running report_uReport ---
This problem has already been reported.
https://retrace.fedoraproject.org/faf/reports/155999/
https://bugzilla.redhat.com/show_bug.cgi?id=994832


3.12.5-301.fc20.x86_64
alsa-utils-1.0.27.2-3.fc20.x86_64


[   32.782439] alsactl[695]: segfault at 76 ip 00007f53f8c87d76 sp 00007fff4b77a120 error 4 in libc-2.18.so[7f53f8c3f000+1b4000]
[24244.921302] alsactl[10457]: segfault at 76 ip 00007fd93915ed76 sp 00007fff68ced480 error 4 in libc-2.18.so[7fd939116000+1b4000]

--- Additional comment from superquad.vortex2 on 20131221T03:22:13 ---

 rdaemon   <card>  like daemon but do the state restore at first


I guess this occur after you update the alsa-driver changes the controls name

the control saved by the old driver "Analog Mic Boost Capture Enum" when boot with alsactl rdaemon 

the new driver use  'Internal Mic Boost Volume'

--- Additional comment from hongjiu.lu on 20131222T15:22:12 ---

Also happened to me on Fedora 20 upgrade from Fedora 17.
Many names are changed.

--- Additional comment from alanh on 20131228T01:39:52 ---

The crash is caused by cerror_() in utils.c calling syslog_() without initializing the va_list ap. This uninitialized arg list is passed to vsnprintf() which causes the crash.

The va_start(ap, fmt) needs to be moved outside the if block, like it is in the error_() function. This bug is also in the dbg_() function.

This will at least prevent the crash, though not the error it's trying to log.

--- Additional comment from alanh on 20131228T01:56:19 ---

Created attachment 842552 [details]
Proposed patch

--- Additional comment from jkysela on 20131229T19:08:21 ---

Thanks, I commited your patch to upstream and I will prepare the Fedora fix ASAP.

http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=f4be3f88b6e80e3f3ea19ba5784cff49ab6e6277

--- Additional comment from updates on 20140106T15:51:16 ---

alsa-utils-1.0.27.2-3.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/alsa-utils-1.0.27.2-3.fc19

--- Additional comment from updates on 20140106T16:02:29 ---

alsa-utils-1.0.27.2-4.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/alsa-utils-1.0.27.2-4.fc20

--- Additional comment from updates on 20140107T09:50:52 ---

Package alsa-utils-1.0.27.2-3.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing alsa-utils-1.0.27.2-3.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-0359/alsa-utils-1.0.27.2-3.fc19
then log in and leave karma (feedback).

--- Additional comment from updates on 20140109T07:40:17 ---

alsa-utils-1.0.27.2-4.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.