Void Linux discussion
 help / color / mirror / Atom feed
From: Duncaen <over...@googlemail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: how to enable pulseaudio/alsa
Date: Thu, 5 Nov 2015 04:02:48 -0800 (PST)	[thread overview]
Message-ID: <1386dc70-28be-46fc-8c4d-7fcf95f8fbad@googlegroups.com> (raw)
In-Reply-To: <c32be2cc-b72f-4ef0-b247-c99d789dc69e@googlegroups.com>

[-- Attachment #1.1: Type: text/plain, Size: 1071 bytes --]

The pulseadio service is confusing and not needed, its used if you want a 
system wide pulseadio daemon and that is definitely not the preferred way 
of running pulse.
Normally pulse should start automatically in your desktop session if its 
required, if that doesn't work, maybe `start-pulseaudio-x11 &` in your 
xinitrc helps.

Am Mittwoch, 4. November 2015 22:15:24 UTC+1 schrieb Muddmaker:
> I want to bump this because I am having a very similar problem. However, 
> it showed up once I switched my DE from MATE to Cinnamon. My audio was 
> working just fine beforehand, and it has stopped working now. I have added 
> pulseaudio as a service, and my problem is the same, as if there is no 
> audio device connected.
> On Sunday, November 1, 2015 at 5:42:13 AM UTC-8, tuxracer wrote:
>> So, I installed alsa and pulseaudio and alsa plugin then made simlink 
>> /etc/sv/alsa to /var/service and /etc/sv/pulseaudio to /var/service as well 
>> but system is not detecting any soundcard. alxamixer returns blank and 
>> nothing to configure. What went wrong?

[-- Attachment #1.2: Type: text/html, Size: 1366 bytes --]

  reply	other threads:[~2015-11-05 12:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-01 13:42 tuxracer
2015-11-01 14:03 ` tuxracer
2015-11-01 14:06 ` tuxracer
2015-11-04 21:15 ` Muddmaker
2015-11-05 12:02   ` Duncaen [this message]
2015-11-07  5:26 ` Muddmaker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1386dc70-28be-46fc-8c4d-7fcf95f8fbad@googlegroups.com \
    --to="over..."@googlemail.com \
    --cc="void..."@googlegroups.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).