LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 02-28-2021, 02:59 PM   #1
upnort
Senior Member
 
Registered: Oct 2014
Distribution: Slackware
Posts: 1,893

Rep: Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143
Current bug? "file /var/lib/alsa/asound.state lock error: No such file or directory"


I am testing updating 14.2 to Current on a Lenovo T400. With rc.alsa executable I always see the following error:

Code:
file /var/lib/alsa/asound.state lock error: No such file or directory
Both the directory and file exist. 0755 permissions and root:root ownership.

Using alsactl -L avoids the errors.

Both aplay and speaker-test function fine.

Booting with rc.alsa not executable also works.

What is causing the error?

Is rc.alsa needed any more?

Thanks.
 
Old 03-01-2021, 06:12 PM   #2
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 732

Rep: Reputation: 479Reputation: 479Reputation: 479Reputation: 479Reputation: 479
Quote:
Originally Posted by upnort View Post
I am testing updating 14.2 to Current

[snip]

Booting with rc.alsa not executable also works.

What is causing the error?

Is rc.alsa needed any more?

Thanks.
On a system born as -current (not upgraded from 14.2) rc.alsa is not executable, so my guess is that it's not needed but perhaps left there for those who have special alsa needs.

chris
 
Old 03-01-2021, 07:08 PM   #3
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,268

Rep: Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859
In the alsa-utils package for -current, rc.alsa is not executable. It has 644 permissions (rw-r--r--). I think, like with rc.pulseaudio, you are to leave it not executable unless you have a reason to change it.
 
Old 03-02-2021, 02:22 PM   #4
upnort
Senior Member
 
Registered: Oct 2014
Distribution: Slackware
Posts: 1,893

Original Poster
Rep: Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143
If there is no upstream remedy then perhaps the rc.alsa script should be modified to using the -L option.
 
Old 03-02-2021, 03:21 PM   #5
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,268

Rep: Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859
Quote:
Originally Posted by upnort View Post
If there is no upstream remedy then perhaps the rc.alsa script should be modified to using the -L option.
Possibly, or maybe the script should be modified to create the file. I'm not sure if one is better than the other.

However, since it isn't executable by default, it might be left as an exercise to the admin if they decide to make it executable.
 
Old 03-02-2021, 04:13 PM   #6
upnort
Senior Member
 
Registered: Oct 2014
Distribution: Slackware
Posts: 1,893

Original Poster
Rep: Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143
On a system updated from 14.2 the files already exist.

While admins should always have final opinion, this is broken and I'd like to find an appropriate cure. Either there is a bug in the alsa code or the rc.alsa script should be modified to use -L.

A quick test in a fresh install VM indicates the lock file no longer exists. No stderr spew. Next time I update one of my test systems from 14.2 I'll delete the lock file and test rc.alsa.

Last edited by upnort; 03-02-2021 at 04:18 PM.
 
Old 03-02-2021, 04:24 PM   #7
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,268

Rep: Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859Reputation: 5859
Quote:
Originally Posted by upnort View Post
On a system updated from 14.2 the files already exist.

While admins should always have final opinion, this is broken and I'd like to find an appropriate cure. Either there is a bug in the alsa code or the rc.alsa script should be modified to use -L.

A quick test in a fresh install VM indicates the lock file no longer exists. No stderr spew. Next time I update one of my test systems from 14.2 I'll delete the lock file and test rc.alsa.
So, it seems to be broken on just a 14.2 -> -current upgrade but works without error on a fresh -current install? If so, maybe the package and rc.alsa file don't need changes, but the CHANGES_AND_HINTS.TXT or UPGRADE.TXT should cover whatever needs to be changed to prevent the issue.
 
Old 03-02-2021, 06:02 PM   #8
upnort
Senior Member
 
Registered: Oct 2014
Distribution: Slackware
Posts: 1,893

Original Poster
Rep: Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143Reputation: 1143
I completed another test run. Deleting the /var/lib/alsa files, directory, and /etc files/links does nothing to stop the stderr spew. Doesn't matter whether rc.alsa is +x.

This will be nominally frustrating for some users. The only cure I have found is using the -L option.

Last edited by upnort; 03-02-2021 at 06:04 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: How To Fix “E: Could not get lock /var/lib/dpkg/lock” Error On Ubuntu LXer Syndicated Linux News 0 11-24-2019 05:33 AM
[SOLVED] Bacula error message:Could not stat "/var/lib/bacula/bacula.sql": ERR=No such file or directory Learnix Linux - Server 2 11-18-2013 10:39 AM
open lock file /var/lib/postfix/master.lock: cannot open file: Permission denied gabsik Linux - Server 6 08-30-2012 09:39 PM
deian yum lock [ ERR] Reading state information E: Could not get lock /var/lock/aptit jayakumar01 Linux - Server 1 12-05-2011 11:26 AM
Compromised? Files "/usr/lib.hwm", "/usr/lib.pwd", "/usr/lib.pwi" Klaus Pforte Linux - Security 4 09-28-2004 11:33 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:12 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration