I actually have 3 user accounts on this OS, two user accounts and a root account. The 2 user accounts have great behavior of sound control. The root account has no sound control at all. There is an error about not being able to use sound control system while in root account, but I have to go back to root and record and post that error (sorry I posted in this manner in the hope someone may have been thru this particular problem and could tell of a 'simple fix').

thanks in advance for any help! More info forthcoming.

OK, boot behavior is with sound, but when boot completes there is a static (sound turning off?) and when hovering over the speaker in the main panel there is a note that shows which says 'Not connected to the PulseAudio server'. Any efforts to connect to this server are unsuccessful. Any help would be appreciated! Again, thanks in advance.

what do you mean by "sound control", what kind?

perhaps a look into alsatools would make things easier, specifically alsamixer for example, but there are others (alsa) too..

Sounds like your root account is just for admin purposes, as it should be, no need for sound whilst doing admin - check your 'groups' as a user & as root, likely root isn't in the 'audio' group.

(Enter groups at the command line to see which groups each is in.)

https://www.linux.com/topic/desktop/...-groups-linux/

1 members found this post helpful.

Blind people aren't allowed to be root on their own PCs?

on command line listed available capabilities for user currently logged in. So, switched to root account and root showed simply 'root'. Can one assume that root being root has access to all capabilities?

It's a perfectly logical and reasonable assumption, yet bad when it comes to sound (and a few other things) with Linux. Root is supposedly the superuser, but often is not really. Sometimes root cannot. Predicting whether and when is something I've never found a handle on.

Then they would be using a distro tailored to suit their purpose.

https://opensource.com/life/15/8/acc...blind-disabled

I'm getting the feeling here that the original poster is using a desktop environment logged in as root. IMO this is the wrong approach for either scenario..

If OP really want to access root, he should do this through a terminal emulator (su or su -) in a desktop environment logged in as a regular user. That way, he can have sound when using root. Alternatively, without knowing how braille works, he should try to access root in getty, not in desktop.

https://pjb.com.au/blin/

You don't have to do that. There are plenty of tools that can be used in any distro..

That is exactly the case. On my PCLinuxOS system, my user account is in the groups
but the root user isn't in any groups except "root".

Exactly.

Also, I don't think OP is blind or otherwise disabled.
Mrmazda was just driving home a point (which I don't agree with).

Without trying to break down the multiple points I was making, what you must be meaning is I shouldn't be the ultimate authority over my own property.

However, anything else amounts to governance by group rather than a sovereign.

Wrong thread?

Ps. I don't remember root needing to be in any other groups than root.

No — you can reconfigure almost any distro to work as you want it to. But the developers are the ultimate authorities over the default behaviour. PCLinuxOS thinks you shouldn't listen to music as root, Slackware thinks you should manage your own dependencies, and so on. If you don't like a policy, don't whine — change it or change your distro.

1 members found this post helpful.