Gnome-volume-control won't start

Hello all,
Since last update I can not start gnome-volume-control:
[romain@arch ~]$ gnome-volume-control
ERROR:misc.c:52:get_page_num: code should not be reached
Abandon
Am I the only to have the problem? How to solve it?
Regards,
Kab

Whoa! Finally someone is having the same problem as I. Unfortunately I have no solution for it
I'm using OSS since I hade trouble getting the sound to work with ALSA, maybe that is a part of the problem.
Last edited by tsvensson (2009-09-17 19:49:05)

Similar Messages

[SOLVED] PulseAudio Volume Control won't start anymore

Hi!
As described in the title, PulseAudio Volume Control won't start from one day to another.
I have no clue where this could come from or what I could have done wrong to create this issue.
Here is how it looks like:
When I start it, it seems to be loading but after some time it just disappears and nothing happens.
I also have the same looking issue with KMix and Google Music Manager.
Do any of you have an idea where this could be coming from?
Thanks for your help :-)
Last edited by StefanMu (2014-01-10 01:15:24)

Rasi wrote:StefanMu, you are not giving enough details. Have there been any updates, that are pulse or gtk related. What versions do you have installed of gtk, gtkmm, libpulse, pavucontrol. Are all of those repository packages, or is something built from AUR? Any custom repositories?
Hi, and thanks for your reply. Here are the details:
gtk:
[root@ACDCROCKS-ARCH_LINUX miniclip22]# pacman -Qi gtk
Name : gtk
Version : 1.2.10-13
Description : GTK+ is a multi-platform toolkit (v1)
gtkmm:
[root@ACDCROCKS-ARCH_LINUX miniclip22]# pacman -Qi gtkmm
Name : gtkmm
Version : 2.24.4-1
Description : C++ bindings for gtk2
Architecture : x86_64
URL : [url]http://www.gtkmm.org/[/url]
libpulse:
[root@ACDCROCKS-ARCH_LINUX miniclip22]# pacman -Qi libpulse
Name : libpulse
Version : 4.0-6
Description : A featureful, general-purpose sound server (client library)
Architecture : x86_64
pavucontrol:
[root@ACDCROCKS-ARCH_LINUX miniclip22]# pacman -Qi pavucontrol
Name : pavucontrol
Version : 2.0-2
Description : A GTK volume control for PulseAudio
Architecture : x86_64
They are all repository packages, NOT from the AUR. As previously mentioned, this is a fresh install, so I don't have any custom repositories. Any help is appreciated. Thanks in advance!
Last edited by miniclip22 (2013-12-28 18:42:12)

Gnome Volume Control

Im having problems with changing the volume of any of outputs PCM, master. When I wan't to scroll up on Volume control applet and Volume Control Aplication gnome-volume-control Left chanel always drops to 0 and than slowly rises with a lot of jumps up and down. This jumping exists if I grab slider to. So...
Its really anoying cause when using scroll whell on applet I have to scrool many times to get max volume if starting volume vas even 70%.
So question ofcourse is how to fix this left chanell jumping.
BTW I now use GNOME 2.24 but this was present in 2.22 to.
BTW when I was using Ubuntu this problem didn't occur. So its gnome+arch problem.
Last edited by christooss (2008-10-22 21:32:27)

And to me too.
The sound chip sucks anyway: CM6501, module snd-usb-audio.
Seems like multi-channel controllers are the culprit:
Simple mixer control 'Speaker',1
Capabilities: pvolume pswitch pswitch-joined
Playback channels: Front Left - Front Right - Rear Left - Rear Right - Front Center - Woofer - Side Left - Side Right
(from amixer)

When unlocking my iphone with the camera slide, my volume controls won't work on video playbacks. However, if I unlock the phone normally and open the camera roll I am able to watch my videos and control the volume. Anyone else notice this?

When unlocking my iphone 5 with the camera slide, my volume controls won't work on video playbacks. However, if I unlock the phone normally and open the camera roll I am able to watch my videos with the control of the volume. Anyone else notice this?
Thank you.

Who can help me what are the symbols of a moon and a lock with a partial circle around it not allowing me to turn on or off my phone

1st Gen IPod Touch Volume Controls won't come up after a few minutes

I've got a first gen IPod touch and ever since I upgraded to the OS 3 family I've had a problem where after a few minutes of playing a video, if I tap the screen to bring up the volume controls, nothing happens. If I tap the screen in the first few minutes, the controls come up fine but after a few minutes a screen tap does nothing. Returning to the home screen and re-launching the video player didn't work either. I was turning the unit off and back on to correct the problem but after reading that a new "feature" of OS 3 pertained to volume control and headphone detection I tried a new tactic. When the volume controls would not display, I unplugged my headphones (the video paused when I did this) and plugged the headphones back in and the volume controls display auto-magically and would appear on with a screen tap for a few minutes then I was back in the same situation. Is there anyway a setting could be created to disable headphone detection and the "features" that it brings? The headphones work fine when the volume controls won't display so it doesn't feel like a headphone problem. Thanks.

To The Apple Discussion Boards!
Except for your keyboard & mouse, disconnect all devices from your computer & repair disk & permissions from your Tiger DVD.
Repairing permissions from the Tiger DVD
Boot up from your Tiger Install DVD while holding down the "c" key.
Select the language you wish to use, and then choose "Disk Utility" from the menu bar.
Your HD should appear in a panel on the left hand side of the window which opens. Select it and then click on the "repair disk" button in the right hand section of the window.
If Disk First aid is able to complete the repair now click on the "Repair permissions" button.
Once this process has been completed restart your computer.
http://docs.info.apple.com/article.html?artnum=25751 About Disk Utility's Repair Disk Permissions feature

Gnome Volume Control High CPU Usage

I have an interesting problem.
When I boot into Arch, my CPU usage is farly low. Jumping around 0 - 10% or so.
But as soon as I open up Gnomes Volume Control window. Cpu usage jumps up to 50 - 60% and stays there, No matter if the windows open or not.
My front channel is also at 0% on boot, so I normally go into the Volume Control to bring that up.
I noticed using alsamixer in the terminal will prevent the cpu usage from going so high. But if I open Gnome's Volume Manager, I have to log out, and log back in to get cpu usage back to normal. Is there anyway to avoid this or fix this issue?

This seems to be a known bug. http://www.google.com/search?hl=en&q=gn … h&aq=f&oq=

Os X Yosemite Volume Control Won't Work

Since upgrading I've had serious issues with my volume control on my macbook pro. First is that the keyboard buttons won't do anything. I can press them and the picture shows up saying they're moving the volume up and down, but on the actual menu bar icon, nothing changes. Also, when I plug things into my computer I have to manually open the preferences to change the output, and once I do that I have to wait about 5 mins for it to register the change. I've tried restarting my computer many times but it doesn't seem to fix the issue :s. HELP!

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
Click the Clear Display icon in the toolbar. Then take an action that isn't working the way you expect. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name or email address, may appear in the log. Anonymize before posting.

Musicapp, speaker and volume control won't work since updated to iOS 7.1

Since I updated my iPhone 4 to iOS 7.1 my iPhone works faster than iOS 7. But some apps like musicapp, youtube have no volume control and the speakers won't work. When somebody call me the iPhone rings normally. I tried turn off bluetooth because I thought the iPhone will conect to my car. I pressed the lock and homebutton for reseting, I deletetet my whole iPhone and installed iOS7.1 again - nothing changed. Only when i plug in my earphones everything will work as normal.

Hi AmishCake!
Thanks for your tipp! i cleaned the headphone port and usb-port and reinserted the plug several times!
i think this isn't the problem!
here i prepared a picture how the screen looks like when i plug in my headphones!
https://www.dropbox.com/s/omi3hlp1zzyx43k/Foto%2026.03.14%2013%2017%2040.png
it seems to be a problem of the update to 7.1 because some guys posted the same problem on other sites.
sorry for my bad english and thank you for trying to solve my problem!

Gnome volume control applet is off screen

Any idea on how to fix this? I have been gone from gnome for a while. Last time I was here the volume control applet slider was vertical. Now that it is horizontal, it exits screen right when it is on the right hand edge of the panel. (For those of you on links/lynx/elinks who cant see my pretty picture)
Last edited by lungdart (2010-10-09 04:34:00)

I only have one screen. But it is a laptop with the capability to run 2 screens.
Also I am using the nvidia drivers.
[lungdart@myhost ~]$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 320 x 240, current 1920 x 1200, maximum 1920 x 1200
default connected 1920x1200+0+0 0mm x 0mm
1920x1200 50.0*
1600x1200 51.0
1400x1050 52.0
1280x1024 53.0
1280x960 54.0
1024x768 55.0
800x600 56.0 57.0
640x512 58.0
640x480 59.0 60.0
512x384 61.0
400x300 62.0
320x240 63.0
[lungdart@myhost ~]$
EDIT: Using gnome 2.32.0, I have had this same problem on my desktop before I pooched it, but never got around to figuring it out.
Last edited by lungdart (2010-10-09 15:33:51)

Apple TV messed up Macbook Pro, Keyboard volume controls won't work.

I can't get my Keyboard Volume controls to work on my macbook pro, Apple TV messed it up. This isn't an issue with disabling the remote control infrared receiver. When I want to turn my volume up or down, I have to go to system prefrences and change the volume that way. It's annoying and a big waste of time. Please help me before I throw this computer against the wall.
Thank You!!

I've got an extremely similar problem. Spillage on the keyboard. Unknown, what it was.
To start with it was dead, no power up.
Then it dried out. There was still a bit of battery power left, and the mouse and track pad worked for a few minutes then it all froze.
So I shut the lid. I left it like that, because I couldnt switch it off.
Much later, opened it up again and all windows opened up, all info was correct,
I was advised to try wireless mouse and keyboard, but you have to get in there before it freezes again.
The battery was charging normally as well.
I made the decision to let the battery die completely and then switch it on again, but sure enough when I did this, it ignored any re-boot command and that's that. Dead as a do-do.
So, without being a computer whizz kid, I presume, it's off to the Apple store for a sizeable bill.
Unless someone else has a cunning plan ????????
I would love to hear it !!!!!!

Audio volume control in quick start bar not working after last HP update

Volume keys at top work fine but clicking cursor on quick start icon for volume control does nothing now.

Hi ,
Thank you for visiting the HP Forums! A great place where you can find solutions for your issues with help from the community!
I came across your post about the Notebook, and wanted to assist you! I have looked into your issue about your HP ENVY 17 Notebook and issues with the Audio after Windows 10 update. Here is a link to the HP Support Assistant if you need it. Just download and run the application and it will help with the software and drivers on your system that might need updating. Restart the Notebook after updates have been done. If your computer is having problems finding and installing operating system updates, try using the Windows Update Troubleshooting tool to fix the problem. Here is a document that shows how to update drivers that are not working correctly with Windows 10. I hope this helps you. Thanks.

Gnome volume control 'jumping'

Hello,
When I try to control the volume in either Volume Control 2.22.0 or in the Volume Control panel applet in Gnome the volume 'jumps'. What I mean by this is when I try to move the slider slightly it behaves abnormally and 'jumps' around from muted, unmuted, or anywhere inbetween (sorry, not sure how else to explain it). If instead I use alsamixer instead to control the sound, the volume moves up/down without a problem. I'm using Alsa version 1.0.16 from www.alsa-project.org.

same problem here. I noticed it the moment i restarted after upgradinig to 2.6.25 Kernel. What happens is (at least for me) the following [assume the volume is being 'increased' using Keyboard or GUI control.
->Vol at 40%
->Vol at 41%
->Vol at 42%... until
->Vol at 0%
->L at 1% R at 0%
->I go to Control app and notice for some reason L and R channels are now unlinked. So i link them back but i cant seem to get the volume up with it linked, the moment i do it goes back to about 0% for both and unlinks. So i moved them seperatley, it worked i have both at 50%, so i felt clever and linked it so i can use keyboard for control, and it went back to unlink+0%ish.
And so on and so forth. U get this is a repeated loop. Once i use alsamixer in console (if channels are unlinked i find they are different volumes so i jst put them back together by maxing both, and now they are linked again) from then on i can change volume using alsamixer OR mplayer for instance (since volume control for mplayer is tied into the PCM volume (NOT Master)) in my case. Of course if i set 3D to post rather than pre PCM volume control becomes useless as always, so mplayer volume control does nothing but mere show. I jst have alsa on Vc/2 so i switch to it when i want to. It is ANNOYING can someone please help.
-Tj

Gnome volume control applet keeps disappearing

Every now and then volume control applet disappears from panel. When I add it again to the panel and log out / log in, there are two of them. I couldn't find any clue on the internet about this issue. Has anybody experienced this problem with gnome? I have gnome 2.28.2.

siriusb wrote:Every now and then volume control applet disappears from panel. When I add it again to the panel and log out / log in, there are two of them. I couldn't find any clue on the internet about this issue. Has anybody experienced this problem with gnome? I have gnome 2.28.2.
Do you block the panels objects for avoid to move?
Otherside, the panel object run in background or not?

LXDE - use Gnome volume control

I started using LXDE coming from Gnome. I loved how I could control the volume on my speakers via the external buttons on my laptop like I did in Gnome. After applying the LXDE panel applet, it won't adjust my volume with the buttons. Only while dragging it's slider.
Anyone know how to use gnome's volume set? I am already using the gnome-power-manager.

You could try installing xbindkeys http://wiki.archlinux.org/index.php/Xbindkeys if it recognizes your external buttons then you can bind them to amixer's master volume

Gnome AND KDE won't start (i686 and 64bit)

http://bbs.archlinux.org/viewtopic.php?id=71991
I've had a rough time these past few days and I posted earlier on Arch64 forums thinking it was just architecture thing but as it turns out after my reinstallation of Arch to 64 bit again (First i686, then 64, then i686 and now 64 again) I finally got it to work but this time Gnome is a pain in the ass, it didn't work with KDE either but KDE never gave me an error or gave me an option to failsafe into the OS.
$HOME/.xsession-errors:
/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
gnome-session[3898]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
gnome-session[3898]: CRITICAL: dbus_g_connection_get_connection: assertion `gconnection' failed
process 3898: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
gnome-session[3898]: ******************* START ********************************
gnome-session[3898]: Frame 0: gnome-session [0x4192d7]
gnome-session[3898]: Frame 1: gnome-session [0x419426]
gnome-session[3898]: Frame 2: /lib/libc.so.6 [0x7f3cbc493ec0]
gnome-session[3898]: Frame 3: /lib/libc.so.6(gsignal+0x35) [0x7f3cbc493e45]
gnome-session[3898]: Frame 4: /lib/libc.so.6(abort+0x19a) [0x7f3cbc4952aa]
gnome-session[3898]: Frame 5: /usr/lib/libdbus-1.so.3 [0x7f3cbef6ab95]
gnome-session[3898]: Frame 6: /usr/lib/libdbus-1.so.3 [0x7f3cbef66a5d]
gnome-session[3898]: Frame 7: /usr/lib/libdbus-1.so.3(dbus_connection_send_with_reply_and_block+0x198) [0x7f3cbef50a88]
gnome-session[3898]: Frame 8: gnome-session [0x41203c]
gnome-session[3898]: Frame 9: gnome-session [0x412140]
gnome-session[3898]: Frame 10: gnome-session [0x41a5b0]
gnome-session[3898]: Frame 11: gnome-session [0x41aa8f]
gnome-session[3898]: Frame 12: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f3cbc48055d]
gnome-session[3898]: Frame 13: gnome-session [0x40aef9]
gnome-session[3898]: ******************* END **********************************
/var/log/gdm/:0.log.3
X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH x86_64
Current Operating System: Linux deuklin 2.6.29-ARCH #1 SMP PREEMPT Sat May 9 14:09:36 CEST 2009 x86_64
Build Date: 15 April 2009 11:01:49AM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue May 12 08:55:10 2009
(==) Using config file: "/etc/X11/xorg.conf"
dlopen: libdrm.so.2: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules/extensions//libdri.so
(EE) Failed to load module "dri" (loader failed, 7)
(EE) Failed to load module "freetype" (module does not exist, 0)
dlopen: libdrm.so.2: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules/extensions//libdri2.so
(EE) Failed to load module "dri2" (loader failed, 7)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Just a point here is that I've had the exact same software installed the same day that I reinstalled and this error did not occur but after formatting my partition with ext4 and testing Arch64 it did. But it did with 32bit as well, there were tons of errors.
I've read about this ConsoleKit error in a few posts here but nothing seems to indicate a fix or anything and since I'm using Gnome now I didn't find anything on it just about KDE.
I can safely use "Failsafe Gnome" without startup scripts but I want it to work without any problems and I don't know if the "dri" thing is related to the ConsoleKit thing with GDM.
I installed it via FTP and had the latest updates as soon as I've installed, so if this is just something that is happening to me right now or alot of other people, please give us hints or anything that could solve this?
If you read my Arch64 thread you know that stuff stopped working for me, first the network (it turns out I had to boot Windows inbetween installing Arch for my network even to start and that sounds ridicilous if it depends on another operating system starting the device because in Windows the network card was turned on with a green light wherein Arch after installing it didn't. I reformated my partitions and changed it again, installed Windows again and tried it out and then installed Arch. It worked, and then I mixed around with KDE and after five minutes of using "startx" (the only thing working) I decided to reinstall with Gnome, but then the network didn't start again (tried booting about ten times) and then I just thought "Let's start windows first so it turns on" and when I just booted Windows and immiedatiely restarted it and booted with the Arch CD, network was available again. Strange? Or is this a period of instability for Arch?
But when I got my network to start, appearantly Keyboard and mouse wasn't working because Xorg forgot to install the drivers when I installed the full group of Xorg so I had to fix that and now it's giving me this error.

Without a dbus socket, dbus probably isn't running. It's supposed to be started automatically when a program needs it. Check to see that it is installed and running:
pacman -Q dbus
pgrep -l dbus
Dbus won't run without hal, so hal should be in:
tail /etc/rc.conf
Are any of your partitions full?
df -h
For the other error, it looks like libdrm isn't installed, but I don't think you need it if you're running the nvidia driver.
Your xorg.conf and Xorg.0.log would also be useful. Also check dmesg for errors.
And see if /etc/rc.d/dbus is marked executable.
Last edited by fphillips (2009-05-12 18:27:41)

Gnome-volume-control won't start

Similar Messages

Maybe you are looking for