Description of problem: Noticed lots of this in /var/log/messages: Sep 19 12:51:31 prf alsactl[875]: /usr/sbin/alsactl: state_lock:121file /var/lib/alsa/asound.state lock error: Too many open files Sep 19 12:51:31 prf alsactl[875]: /usr/sbin/alsactl: state_lock:121file /var/lib/alsa/asound.state unlock error: Too many open files # lsof | grep alsactl alsactl 875 root 1021uw REG 8,5 11 400253 /var/lib/alsa/asound.state.lock alsactl 875 root 1022uw REG 8,5 11 400253 /var/lib/alsa/asound.state.lock alsactl 875 root 1023uw REG 8,5 11 400253 /var/lib/alsa/asound.state.lock YES! Those are just the LAST 3 lines of: # lsof | grep alsactl | wc 1038 9342 127413 Version-Release number of selected component (if applicable): # rpm -qa | grep alsa libalsa-data-1.0.27.2-3.mga4 alsa-utils-1.0.27.2-2.1.mga4 lib64alsa-oss0-1.0.25-4.mga4 lib64alsa2-devel-1.0.27.2-3.mga4 lib64alsa-plugins-pulseaudio-1.0.27-3.mga4 lib64alsa-plugins-1.0.27-3.mga4 libalsa2-1.0.27.2-3.mga4 alsa-plugins-pulse-config-1.0.27-3.mga4 lib64alsa2-1.0.27.2-3.mga4 How reproducible: no idea. just discovered. Steps to Reproduce: 1. no idea. just using the system. 2. 3. Reproducible: Steps to Reproduce:
After running mga5 13 days... Last 3... alsactl 948 root 285u REG 0,18 11 8838 /run/lock/asound.state.lock alsactl 948 root 286u REG 0,18 11 8838 /run/lock/asound.state.lock alsactl 948 root 287u REG 0,18 11 8838 /run/lock/asound.state.lock # lsof | grep alsactl | wc 302 2718 35770
after 32 days: alsactl 948 root 1021u REG 0,18 11 8838 /run/lock/asound.state.lock alsactl 948 root 1022u REG 0,18 11 8838 /run/lock/asound.state.lock alsactl 948 root 1023u REG 0,18 11 8838 /run/lock/asound.state.lock
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Problem still present in mga5. In fact, alsactl added six more locks in 20 minutes. Don't know what's causing this since I had no sound playing during this time... # lsof | grep alsactl [...] alsactl 927 root 160u REG 0,18 11 592 /run/lock/asound.state.lock alsactl 927 root 161u REG 0,18 11 592 /run/lock/asound.state.lock root@prf ~ 09:10:12 # # lsof | grep alsactl [...] alsactl 927 root 166u REG 0,18 11 592 /run/lock/asound.state.lock alsactl 927 root 167u REG 0,18 11 592 /run/lock/asound.state.lock root@prf ~ 10:30:03 #
Version: 4 => 5
CC: (none) => pkg-bugsAssignee: bugsquad => mageia
Hi Pierre, Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja
CC: (none) => marja11
No reply, so closing as OLD since Mageia 5 is no longer maintained.
Status: NEW => RESOLVEDResolution: (none) => OLD