Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 166818 - alsa-lib - complaints from installation scripts
alsa-lib - complaints from installation scripts
Product: Fedora
Classification: Fedora
Component: alsa-lib (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Martin Stransky
Depends On:
  Show dependency treegraph
Reported: 2005-08-25 23:25 EDT by Michal Jaegermann
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: "alsa-lib-1.0.9rf-3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-30 07:47:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2005-08-25 23:25:13 EDT
Description of problem:

While installing an update to alsa-lib I got few times (on x86_64 with
libraries for different architectures):

Version 0.4

Usage: ainit user_name start|stop [--version] [--help]

Looking at installation scriplets that likely meand that
/var/run/console/console.lock was found but not with an expected content.

BTW, a script like /etc/hotplug/usb/usbcam looks for console.lock file
in few different places.

Version-Release number of selected component (if applicable):
Comment 1 Martin Stransky 2005-08-29 06:23:40 EDT
Which version of pam do you have?
Could you please attach the /var/run/console/console.lock file?
Comment 2 Michal Jaegermann 2005-08-29 11:39:11 EDT
> Which version of pam do you have?

pam-0.80-7 at this moment. It was installed on 25 Aug 2005.

> Could you please attach the /var/run/console/console.lock file?

I am afraid that there is nothing to attach.  Such file does not exist.
'find /var -name console.lock' does not report it somewhere else either.
At least current alsa-lib package scripts have a check for this contigency
but this means that /usr/bin/ainit will not run.  No idea what practical
effects this will have.  Why it is important that during an de/installation
ainit runs for whomever happens to be listed in console.lock, if such thing
does exist, and not just simply for root?  "Random User" cannot install.
Comment 3 Martin Stransky 2005-08-30 07:47:55 EDT
If you run ainit for root, only root will be able to use sound card. So I added
check for configuration reloading for the current user, which is using
soundcard. If you are root, you can use the soundcard anyway.

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