[SOLVED] pulseAudio/alsa no longer working...

BW-userx · 10-31-2016, 12:39 PM

I was going along watching a video in VLC then when I went to open a different video I get this message.

VLC

Quote:

Audio output failed:
The audio device "default" could not be used:
Connection refused.

I had already loaded mplayer to play a list.m3u in my Music Directory, it was still up but paused, so I un=paused it I can hear music,

Quote:

Playing Music/./17 - Diamonds (Duet with Herb A6.mp3.
Audio only file format detected.
Load subtitles in Music/./
==========================================================================
Opening audio decoder: [mpg123] MPEG 1.0/2.0/2.5 layers I, II, III
AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000->176400)
Selected audio codec: [mpg123] afm: mpg123 (MPEG 1.0/2.0/2.5 layers I, II, III)
==========================================================================
AO: [pulse] 44100Hz 2ch s16le (2 bytes per sample)
Video: no video
===== PAUSE =====
A: 118.3 (01:58.3) of 232.0 (03:52.0) 0.4%

But, when I run mplayer to play a different file, in another terminal it again gives me errors.

Code:

userx@SlackDaddy~>> mplayer "Music/1 - Sonic Youth with James Tenney - ..mp3"
MPlayer 1.2.1-5.3.0 (C) 2000-2016 MPlayer Team

Playing Music/1 - Sonic Youth with James Tenney - ..mp3.
libavformat version 56.40.101 (internal)
Audio only file format detected.
Load subtitles in Music/
==========================================================================
Opening audio decoder: [mpg123] MPEG 1.0/2.0/2.5 layers I, II, III
AUDIO: 44100 Hz, 2 ch, s16le, 160.0 kbit/11.34% (ratio: 20000->176400)
Selected audio codec: [mpg123] afm: mpg123 (MPEG 1.0/2.0/2.5 layers I, II, III)
==========================================================================


AO: [pulse] Init failed: Connection refused
Failed to initialize audio driver 'pulse'
Could not open/initialize audio device -> no sound.
Audio: no sound
Video: no video


Exiting... (End of file)

the only thing I did was run a few slackbuilds, deleted everything in my /tmp directory etc ... prior to me noticing this,

I just hit enter on the terminal running the mplayer that was working, now it is no longer putting out sound either, I lost sound on Slack 14.2 ~ Halloween mishaps.

BW-userx · 10-31-2016, 01:01 PM

Code:

bash-4.4# chmod +x /etc/rc.d/rc.pulseaudio
bash-4.4# /etc/rc.d/rc.pulseaudio restart
Stopping PulseAudio:  /bin/killall pulseaudio
Starting system PulseAudio daemon:  /usr/bin/pulseaudio --system --disallow-module-loading &

sounds is back, BUT
now that I set this up by giving rc.pulseaudio executable permissions it gets started at boot, when it wasn't(?) but still worked.
so what am I to expect now after I reboot this ?

it was not actually a fix because I have no idea why it stopped.

bassmadrigal · 10-31-2016, 01:11 PM

In the top of the rc.pulseaudio file, it states:

Code:

# In this mode, a single system instance of PulseAudio will be shared by
# multiple local users.
#
# Please note:  this is not generally the best way to use PulseAudio!
# Normally pulseaudio will start automatically as-needed with an instance
# per audio user.  Unless you really need to use system mode you should leave
# this script non-executable.

Likely this was just a hiccup of pulseaudio. If you would've rebooted, it likely would've brought your sound back without you needing to do anything to the rc.pulseaudio file. Personally, I would remove the execute bit from the file and see what a reboot does.

You probably could've also just killed pulse (pulseaudio --kill) and then restart it (pulseaudio --start) to fix your problem, although, I'm not sure if it would work since you're now using system mode. It might work, it might not. I've never toyed with it.

BW-userx · 10-31-2016, 01:36 PM

Quote:

Originally Posted by bassmadrigal

In the top of the rc.pulseaudio file, it states:

Code:

# In this mode, a single system instance of PulseAudio will be shared by
# multiple local users.
#
# Please note:  this is not generally the best way to use PulseAudio!
# Normally pulseaudio will start automatically as-needed with an instance
# per audio user.  Unless you really need to use system mode you should leave
# this script non-executable.

Likely this was just a hiccup of pulseaudio. If you would've rebooted, it likely would've brought your sound back without you needing to do anything to the rc.pulseaudio file. Personally, I would remove the execute bit from the file and see what a reboot does.

You probably could've also just killed pulse (pulseaudio --kill) and then restart it (pulseaudio --start) to fix your problem, although, I'm not sure if it would work since you're now using system mode. It might work, it might not. I've never toyed with it.

I've never toyed with this either it usually just works. I've never ran into this problem before, and I am in a state of right now unable to reboot for a few hours so I was looking for a (quick) fix without having to reboot. and hopefully a why did it do that so I can try to prevent it from happening again.

I'll remove the x from the rc.xx file. before I reboot in a few... see if I gets back should, prob will, but again, still does not find that why did it happen so I can try to prevent it from happening again. if it was in fact a hiccup, well then that is what it was.

thanks.

kingbeowulf · 10-31-2016, 02:00 PM

Pulseaudio "vanishes' for me on occassion, especially when shutting down vncserver (tigervnc). Instead of rc.pulseaudio, as your normal logged in user, all you need to (usually) do is:

Code:

$ pulseaudio --start

It seems pulseaudio is a bit brittle when rocking a few X windows.

BW-userx · 10-31-2016, 02:01 PM

Quote:

Originally Posted by kingbeowulf

Pulseaudio "vanishes' for me on occassion, especially when shutting down vncserver (tigervnc). Instead of rc.pulseaudio, as your normal logged in user, all you need to (usually) do is:

Code:

$ pulseaudio --start

It seems pulseaudio is a bit brittle when rocking a few X windows.

put that in my note book and thanks

bassmadrigal · 10-31-2016, 02:12 PM

Quote:

Originally Posted by BW-userx

I've never toyed with this either it usually just works. I've never ran into this problem before, and I am in a state of right now unable to reboot for a few hours so I was looking for a (quick) fix without having to reboot. and hopefully a why did it do that so I can try to prevent it from happening again.

I'll remove the x from the rc.xx file. before I reboot in a few... see if I gets back should, prob will, but again, still does not find that why did it happen so I can try to prevent it from happening again. if it was in fact a hiccup, well then that is what it was.

thanks.

You could check /var/log/messages, dmesg, and/or /var/log/syslog to see if any provide any error messages related to pulse.

Code:

grep pulse /var/log/{messages,syslog}
dmesg | grep pulse

BW-userx · 10-31-2016, 02:16 PM

Quote:

Originally Posted by bassmadrigal

You could check /var/log/messages, dmesg, and/or /var/log/syslog to see if any provide any error messages related to pulse.

Code:

grep pulse /var/log/{messages,syslog}
dmesg | grep pulse

I have rebooted so a lot of info prob got lost, but after deleting everything in /tmp

Code:

Failed to connect to socket /tmp/dbus-ddKr2aKDZ3: Connection refused

/var/log/syslog:Oct 31 12:57:42 SlackDaddy pulseaudio[1329]: [pulseaudio] pid.c: Failed to open PID file
 '/tmp/pulse-FJC6SkzvMY69/pid': No such file or directory

i got a few of them but I got sound so .....

bassmadrigal · 10-31-2016, 02:29 PM

If I remember right, pulse relies on files in /tmp/, so if you clear that while pulse is running, it will likely break. If you did this before, it is likely the cause of your problem.

BW-userx · 10-31-2016, 02:33 PM

Quote:

Originally Posted by bassmadrigal

If I remember right, pulse relies on files in /tmp/, so if you clear that while pulse is running, it will likely break. If you did this before, it is likely the cause of your problem.

first time completely clearing /tmp but I bet you a pumpkin you're right.
got a few things back in tmp after reboot

Quote:

userx@SlackDaddy~>> ls /tmp
gpg-9yKZZM hb.1655 hb.1867 ksocket-root ssh-0Q2CW9P8iZJz
hb.1640 hb.1863 kde-root pulse-FJC6SkzvMY69

so I'll put that in my note boot too.

bassmadrigal · 10-31-2016, 02:53 PM

If you want to clear your tmp, it's best to use something that won't kill files from a certain period of time (see below) or have it cleared on shutdown (maybe add an entry to /etc/rc.d/rc.local_shutdown, which might need to be created if it isn't already there). The following command will remove anything over 7 days old:

Code:

find /tmp -mindepth 1 -mtime +7 -delete

BW-userx · 10-31-2016, 03:11 PM

Quote:

Originally Posted by bassmadrigal

If you want to clear your tmp, it's best to use something that won't kill files from a certain period of time (see below) or have it cleared on shutdown (maybe add an entry to /etc/rc.d/rc.local_shutdown, which might need to be created if it isn't already there). The following command will remove anything over 7 days old:

Code:

find /tmp -mindepth 1 -mtime +7 -delete

it was one of them dang this is getting cluttered looking, after installing a few slackbuilds ,, it is temp don't need them ?? oh well . . I'll find out, del everything in tmp moods ... thanks for the commands ..

drgibbon · 10-31-2016, 06:21 PM

Pulseaudio seems temperamental to me. Every now and then I have to

Code:

killall pulseaudio

(sometimes a few times) to get sound working (I get the connection refused error messages also).

FTIO · 11-01-2016, 09:59 AM

Looks like pulseaudio is turning our linux system(s) into good ol' windows systems by having to 'reboot' when one burps or blinks more than twice in 30 seconds. (yeah, I know, hating on poor pulseaudio again ain't I).

BW-userx · 11-01-2016, 11:06 AM

Quote:

Originally Posted by FTIO

Looks like pulseaudio is turning our linux system(s) into good ol' windows systems by having to 'reboot' when one burps or blinks more than twice in 30 seconds. (yeah, I know, hating on poor pulseaudio again ain't I).

NNAAAAAAAHHHH you're miss informed
I deleted everything in my /tmp while using it so when I went to watch another movie the file it was using was no longer there.