public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: thelma@sys-concept.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] alsamixer - no sound
Date: Sat, 16 Dec 2023 16:16:17 -0700	[thread overview]
Message-ID: <25001d2e-3a52-49b2-841c-f4c8a25ebc11@sys-concept.com> (raw)
In-Reply-To: <20231216150358.2116011d@tux2.localnet>


On 12/16/23 16:03, Jigme Datse wrote:
> On Sat, 16 Dec 2023 13:19:30 -0700
> thelma@sys-concept.com wrote:
> 
>> After recent upgrade I have no sound.
> 
> This seems like something that just happens, so that's not that
> unusual.
> 
>> Running as root:  alsamixer
>> XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by
>> uid 1000! (This could e.g. happen if you try to connect to a non-root
>> PulseAudio as a root user, over the native protocol. Don't do that.)
> 
> I'm sure you have an answer that says this, but this message says it
> all, though maybe a bit obscurely...  The directory `/run/user/1000` is
> not owned by the user ID `(uid 0)` but by `uid 1000`.  You are running
> the command as uid 0, or root.  Which you acknowledge you're doing.  It
> says the important thing at the end `Don't do that.`.
> 
> You need to run it as the user who is logged in to X (or Wayland).
> 
>> Does dir: /run/user/1000
>> should be own by "root:root"  or user on the system?
> 
> This is a temporary directory which is created on login (I believe
> that's when it gets created).  Don't change the ownership of it.  The
> problem is the user you are running the command as, isn't correct.
> 
>> When I run:
>> chown root:root /run/user/1000
>>
>> alsamixer
>> ALSA lib
>> /var/tmp/portage/media-plugins/alsa-plugins-1.2.7.1-r1/work/alsa-plugins-1.2.7.1/pulse/pulse.c:242:(pulse_connect)
>> PulseAudio: Unable to connect: Access denied
> 
> Probably because your user 1000 is trying to access something that only
> root can access.  But it's not entirely clear.  The changing ownership
> of /run/user/1000 to root, will break *lots* of things.  Especially
> don't do that.
> 
>> cannot open mixer: Connection refused
> 
> I hope you got this sorted.

Yes, I changed back
chown user:user /run/user/1000

I run:
chmod o+w /var/lib/alsa/asound.state

but still can not save setting, running "alsamixer" as user will
I can select correct sound card but pressing escape does not preserve the changes.

Besides in message log I see:

[pulseaudio] protocol-native.c: Denied access to client with invalid authentication data.
pulseaudio[28829]: [autospawn] lock-autospawn.c: Cannot access autospawn lock.
pulseaudio[30032]: [autospawn] lock-autospawn.c: Cannot access autospawn lock.
pulseaudio[4497]: [pulseaudio] x11wrap.c: X11 I/O error handler called
pulseaudio[4497]: [pulseaudio] x11wrap.c: X11 I/O error exit handler called, preparing to tear down X11 modules


  reply	other threads:[~2023-12-16 23:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-16 20:19 [gentoo-user] alsamixer - no sound thelma
2023-12-16 20:57 ` thelma
2023-12-16 21:11   ` Jude DaShiell
2023-12-16 21:25     ` thelma
2023-12-16 22:02 ` Vít Smolík
2023-12-16 22:23   ` thelma
2023-12-16 23:03 ` Jigme Datse
2023-12-16 23:16   ` thelma [this message]
2023-12-16 23:33 ` [gentoo-user] " Nuno Silva
2023-12-16 23:54   ` thelma
2023-12-17  3:00     ` Nikos Chantziaras
2023-12-17  3:31       ` thelma
2023-12-17 10:39         ` Hoël Bézier
2023-12-17  0:05   ` thelma

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=25001d2e-3a52-49b2-841c-f4c8a25ebc11@sys-concept.com \
    --to=thelma@sys-concept.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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