volume control will never open from the menu and will never appear on panel

Bug #344728 reported by Aaron
This bug report is a duplicate of:  Bug #345550: gnome-sound-properties freeze. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-media (Ubuntu)
Incomplete
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-media

the volume will however open when run from a terminal, and works perfectly.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-volume-control
NonfreeKernelModules: nvidia
Package: gnome-media 2.25.92-0ubuntu2
ProcAttrCurrent: unconfined
ProcEnviron:
 LANG=C
 SHELL=/bin/bash
SourcePackage: gnome-media
Uname: Linux 2.6.28-10-generic x86_64

Revision history for this message
Aaron (apelly) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, do you have any error in .xsession-errors when having the issue?

Changed in gnome-media (Ubuntu):
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Aaron (apelly) wrote :

yes, there seem to be some interesting words in .xsession-errors. I have attached it so you can decide if any of it is relevant

Revision history for this message
Noel J. Bergman (noeljb) wrote :

I am also seeing the problem that the volume applet has disappeared from the Gnome panel, and will not add back. I tried doing a tail -n 0 -F .xsession-errors while adding. Nothing.

And I'm on tonight's kernel: 2.6.28-11-generic, with all other current updates.

However, I cannot reproduce that gnome-volume-control runs from the commandline. I get the following:

$ gnome-volume-control
/usr/share/themes/Human/gtk-2.0/gtkrc:82: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/usr/share/themes/Human/gtk-2.0/gtkrc:83: Murrine configuration option "lightborder_ratio" will be deprecated in future releases. Please use "lightborder_shade" instead.
/usr/share/themes/Human/gtk-2.0/gtkrc:194: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.

And no volume control window.

Changed in gnome-media:
status: Incomplete → Confirmed
Revision history for this message
Noel J. Bergman (noeljb) wrote :

This is fixed now. Please verify if it is fixed for you, too.

Revision history for this message
Aaron (apelly) wrote :

Well, I upgraded about 20 minutes ago, and now I see the same behavior as you, Noel.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

I upgraded again today, and now the volume control is broken again. :-( I get the same behavior that I did last night before reporting it as fixed.

Revision history for this message
Sebastien Bacher (seb128) wrote :

what icon do you click on exactly? could you open a command line, run ps aux | grep volume and see if the capplet is running? could you attach gdb to it to get a stracktrace?

Changed in gnome-media (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Noel J. Bergman (noeljb) wrote :

Sebastian, there IS NO ICON. That's kinda the whole point. :-) And if it is last night, when I kept trying to add one, it never appeared until the transient fix, and then like 20 of them appeared, which I then cleaned up

Now here's some additional information. If I run gnome-volume-control from the command line, it starts and hangs. Attached is the output from:

  $ strace gnome-volume-control 2> gvc-strace

*BUT* ... when I first did the strace, I had a typo:

  $ strace gnome-volume-control > gvc-strace

and the control panel DID come up! I have reproduced that with:

  $ gnome-volume-control > /dev/null

Sure enough, fires right up.

Hope some of this helps.

Revision history for this message
Aaron (apelly) wrote :
Revision history for this message
Aaron (apelly) wrote :

gvc.strace1 failed
gvc.strace2 worked fine immediately afterwards

the behavior is erratic. sometimes it works, sometimes it doesn't. it doesn't appear to be related to permissions; root sees the same problems.

is this any help?

Revision history for this message
Sebastien Bacher (seb128) wrote :

strace are not really useful no, what you be useful is to get a gdb stacktrace of the hanging run

Revision history for this message
Aaron (apelly) wrote :

OK, I have googled & I still have no good idea how to help. I do have this however:

0x00007f9475fb22e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
(gdb) bt
#0 0x00007f9475fb22e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007f94770d313e in gst_task_join () from /usr/lib/libgstreamer-0.10.so.0
#2 0x00007f946ed6458e in ?? () from /usr/lib/gstreamer-0.10/libgstalsa.so
#3 0x00007f946ed6563e in ?? () from /usr/lib/gstreamer-0.10/libgstalsa.so
#4 0x00007f947709a1cc in gst_element_change_state () from /usr/lib/libgstreamer-0.10.so.0
#5 0x00007f947709ce7e in ?? () from /usr/lib/libgstreamer-0.10.so.0
#6 0x0000000000409744 in ?? ()
#7 0x00007f94761ca92a in ?? () from /usr/lib/libgstaudio-0.10.so.0
#8 0x00007f94761cad24 in gst_audio_default_registry_mixer_filter () from /usr/lib/libgstaudio-0.10.so.0
#9 0x000000000040954a in ?? ()
#10 0x00007f9475c535a6 in __libc_start_main () from /lib/libc.so.6
#11 0x0000000000407e79 in ?? ()
#12 0x00007fff80b5eff8 in ?? ()
#13 0x000000000000001c in ?? ()
#14 0x0000000000000001 in ?? ()
#15 0x00007fff80b6072a in ?? ()
#16 0x0000000000000000 in ?? ()
(gdb)

from attaching gdb to gnome-volume-control while it was hung and telling it 'bt'

so is _this_ any help? i'm happy to provide more info if you need it.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue seems similar to bug #576586

Revision history for this message
Aaron (apelly) wrote :

i can't find that bug anywhere sorry.

Revision history for this message
Sebastien Bacher (seb128) wrote :

that was the GNOME bug number, bug #345550 there

Revision history for this message
Aaron (apelly) wrote :

yes. probable duplicate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.