Reprinted-NovolumecontrolGStreamer... found

-NovolumecontrolGStreamer... found -- Linux general technology-Linux technology and application information. For more information, see the following. [I = s] This post was last edited by lixiao0555

My fc8 may be in English after installation. First, I had a question about the input method. After searching in the forum, I found the answer, and then I was unable to use the sound for normal users, but it can be under root.
First, I suspect there is a problem with the configuration file of my common users. To determine the root cause of the problem, I create a common account under root. The problem persists. Scratching your head, google, but menu options are English, search out is also English, finally in the http://www.linuxquestions.org/qu... vices-found-459527/found a buddy of the problem and I am the same, shunteng touch melon, in his blog: http://linux.dsplabs.com.au/no-v... -the root cause of the problem is found in the bug-on-ubuntu-p31. Thanks and their selflessness have made me feel the pleasure of solving problems. Really, the installation of Thanks in linux, the happiest thing in the learning process is to find help from many people when you encounter problems. Thank you very much. I would like to thank the table for reprinting the text of kmail buddy here. It doesn't matter if it is in English. It can be understood in general with stardict.
No volume control GStreamer... found-no sound on Ubuntu

Introduction

I was introduced to Linux via RedHat distributions, such Fedora and CentOS. With Fedora you tend to learn a lot because so many things are broken! I also used Novell's openSuSE for a while. I found it to be much more polished than Fedora. suSE provided des Yast configuration utility: a central GUI application where you simply click and things just work, I. e. no need for editing of configuration files. suSE is however quite chunky, I. e. it is quite hungry for system resources. very recently, I have installed Ubuntu. I have heard Ubuntu users Praising it, while users of other distros were ridiculing it for the lack of development tools. Well, since installing it... I have been impressed and I started praising it too :). ubuntu is targeted for the end users as a desktop environment. it is very polished, things just work. it is quick and compact. installing extra Debian packages is not a problem. synaptic package manager handles it flawlessly. that said however, there have been a few errors cropping in here and there, especially to do with user management and user permissions. one such error, No volume control GStreamer plugins and/or devices found, prevents users from accessing the audio device. note however, that the above error is caused by a Gnome bug and is most likely distribution independent. in this article, I will present a number of approaches to getting around this bug.

Problem description

After installing Ubuntu both my soundcards worked... Initially. then one day I have rebooted, logged back in and clicked on the Gnome volume control (shell: gnome-volume-control) icon on the top bar. the icon had a red sign over it, as shown below, indicating that no audio devices were accessible.

Screenshot: broken Gnome mixer volume control (disabled)

After clicking on the mixer icon the following error was produced,

The volume control did not find any elements and/or devices to control.
This means either that you don't have the right GStreamer plugins installed,
Or that you don't have a sound card configured.
You can remove the volume control from the panel by right-clicking the speaker
Icon on the panel and selecting "Remove From Panel" from the menu.

Also shown in the screenshot below.

Error: broken Gnome mixer volume control

Subsequent attempts to open Gnome volume control resulted in another error.

No volume control GStreamer plugins and/or devices found.

Here is the actual screenshot of this error message.

Error: broken Gnome mixer volume control 2

Fixing the problem

The above errors occur simply because the current user, in this case the user kamil, does not have permissions to access the audio device (s ). the reason why a user looses these permissions is unclear to me. fixing it will be easy however. first, lets have a look at permissions for the ALSA devices. if you are unfamiliar with audio architecture on Linux checkout the basic introduction in the following post lsof | grep snd-how to free a Linux sound device. type the command below at the shell.

Ls-la/dev/snd #©2007 dsplabs.com. au

If the above command fails, I. e. it produces the following error

Ls:/dev/snd: No such file or directory

Then it has been suggested on the Launchpad's Bug forum that the Ubuntu linux modules package: linux-ubuntu-modules-2.6.22-14-386 may be missing. To check if this package is installed on your system run dpkg as follows.

Dpkg-l linux-ubuntu-modules-2.6.22-14-386

If this specific version is not presnet then you will get the following error message.

No packages found matching linux-ubuntu-modules-2.6.22-14-386.

Have a look if any version is installed by using this command.

Dpkg-l linux-ubuntu-modules -*

I got the following output on one of our PCs.

Desired = Unknown/Install/Remove/Purge/Hold
| Status = Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/Err? = (None)/Hold/Reinst-required/X = both-problems (Status, Err: uppercase = bad)

|/Name Version
++-========================================================= ====================================
Ii linux-ubuntu-modules-2.6.22-14-38 2.6.22-14.37
Ii linux-ubuntu-modules-2.6.22-14-ge 2.6.22-14.37

Description
-============================================== ====================================
Ubuntu supplied Linux modules for version 2.6.22 on i386
Ubuntu supplied Linux modules for version 2.6.22 on x86/x86_64

If you do not have it installed, simply install it using apt-get and that may solve your audio problems!

Sudo apt-get install linux-ubuntu-modules-2.6.22-14-386

Note that the above modules are precompiled for a specific kernel version and thus will require a reboot after installation. if the above hasn't helped, then read-on. the ls-la/dev/snd command produced the following output on my computer.

Total 0
Drwxr-xr-x 2 root 180.
Drwxr-xr-x 12 root 13860 ..
Crw-rw ---- 1 root audio 116, 8 controlC0
Crw-rw ---- 1 root audio 116, 7 pcmC0D0c
Crw-rw ---- 1 root audio 116, 6 pcmC0D0p
Crw-rw ---- 1 root audio 116, 5 pcmC0D1c
Crw-rw ---- 1 root audio 116, 4 pcmC0D2p
Crw-rw ---- 1 root audio 116, 3 seq
Crw-rw ---- 1 root audio 116, 2 timer

Which means that my audio device has been detected and ALSA drivers for it have been loaded. as you can see in the above output only the root user and members of the audio group have permissions to access ALSA devices. A bug caused the user kamil to be removed from audio group, and hence kamil has no longer access to the audio devices on his system! A very crude fix to this problem is to allow unrestricted access to these devices to all users and groups using the following command.

Sudo chmod-R a + rwx/dev/snd #©2007 dsplabs.com. au
// The focus is here. Note R, In uppercase

This is obviusly not a very good practice. the only reason you wowould do this is if you were in a real hurry to get the audio going or to check if the permissions and group memberships are causing your audio headaches. lets have a look at the permissions now.

Ls-la/dev/snd

The output below shows that everyone can access the ALSA devices.

Total 0
Drwxrwxrwx 2 root 180.
Drwxr-xr-x 12 root 13860 ..
Crwxrwxrwx 1 root audio 116, 8 controlC0
Crwxrwxrwx 1 root audio 116, 7 pcmC0D0c
Crwxrwxrwx 1 root audio 116, 6 pcmC0D0p
Crwxrwxrwx 1 root audio 116, 5 pcmC0D1c
Crwxrwxrwx 1 root audio 116, 4 pcmC0D2p
Crwxrwxrwx 1 root audio 116, 3 seq
Crwxrwxrwx 1 root audio 116, 2 timer

Clicking the mixer applet pops-up the mixer for my ALSA device without any problems.

Screenshot: Gnome volume control now works!

For non-ALSA devices (I. e. OSS devices) the above fix wowould look like this:

Sudo chmod a + rwx/dev/audio *#©2007 dsplabs.com. au
Sudo chmod a + rwx/dev/dsp *

However, a proper fix to the above problem is to (re) add the user in question to the audio group. This can be done from shell as follows.

Sudo usermod-g kamil-a-G audio kamil #©2007 dsplabs.com. au

Important, make sure you do include the-a switch in the command above, otherwise the user kamil will be a member of the kamil and audio groups only!



If this happens, logout and re-login, then check what groups you are still a member of by using the following command.

Groups

If the output of the above command contains most of the following groups, in some order, then you are fine.

Kamil, audio, adm, uucp, dialout, cdrom, floppy, dip, video, plugdev, plugin, netdev, lpadmin, powerdev, admin

On the other hand if the list is a lot shorter, like is shown below,

Kamil audio

Then you will have to restore the original group allocation, as discussed by Chris Collins in the Restore Default Ubuntu Groups post, I. e. by running the following command (remember to change the group kamil and user kamil in the command below to appropriate group and user for you; kamil group entries are in green and kamil user entries are in blue ).

Sudo usermod-g kamil-G kamil, audio, adm, uucp, dialout, cdrom, floppy, dip, video ,\
Plugdev, plugin, netdev, lpadmin, powerdev, admin kamil #©2007 dsplabs.com. au

Another logout and re-login will be required for the permission changes to take effect. note that if you have installed non-base packages that create new groups then use the Administrator profile list of groups contained in/etc/gnome-system-tools/users/profiles file in the above command instead, i. e.

Cat/etc/gnome-system-tools/users/profiles

Use the list in the last line of the output (notice the non-standard fuse group ).

[Unprivileged]
Name = Unprivileged
Name [es] = Usuario sin privilegios
Shell =/bin/bash
Home-prefix =/home
Uid-min = 1000
Uid-max = 6000

[Desktop]
Name = Desktop user
Name [es] = Usuario del escritorio
Default = 1
Shell =/bin/bash
Home-prefix =/home
Uid-min = 1000
Uid-max = 6000
Groups = cdrom, floppy, dialout, tape, dip, adm, plugdev, fax, audio, audio, fuse, lpadmin, video

[Administrator]
Name = Administrator
Name [es] = Administrador
Shell =/bin/bash
Home-prefix =/home
Uid-min = 1000
Uid-max = 6000
Groups = cdrom, floppy, dialout, tape, dip, adm, plugdev, fax, audio, audio, fuse, admin, lpadmin, video

The changed command looks as follows.

Sudo usermod-g kamil-G kamil, cdrom, floppy, dialout, tape, dip, adm, plugdev, fax ,\
Audio, audio, fuse, admin, lpadmin, video kamil #©2007 dsplabs.com. au

An alternative to the use of usermod shell command is the sudo users-admin Gnome GUI user and group management tool. this tool is located under System» Administration» Users and Groups in your top bar. it can also be started from shell using the following command.

Sudo users-admin

This is what the users-admin tool looks like.

Screenshot: user-admin

Select the appropriate user and click the Properties button.

Screenshot: user-admin permissions

Now, make sure that the Use audio devices option is checked. beaware the latest Ubuntu release (7.10 gutsy) ships with Gnome users-admin tool version that has a few bugs and its use may cause you some grief. one last thing, a very good reference to read if you are having audio device issues on Linux is: Comprehensive Sound Problem Solutions Guide.

Good luck!

Did you find the above information useful and interesting? If so, please support this site by using the blog directory links at the bottom of this page. Thanks for your support!

If you have any Linux related problems or questions then please feel free to post them on our Linux Forums: http://linux.dsplabs.com.au/forums.