gnome-volume control crashes (preferences)

Bug #69894 reported by R Volgers
6
Affects Status Importance Assigned to Milestone
gnome-media (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Although my alsa config is somewhat broken at the moment, gnome-volume-manager is the only app that actually manages to crash because of it. Crash occurred when selecting the "Preferences" menu option.

See attached crash report.

Revision history for this message
R Volgers (mr-wiseman) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :
Download full text (46.4 KiB)

--- stack trace ---
Using host libthread_db library "/lib/libthread_db.so.1".
Core was generated by `gnome-volume-control'.
Program terminated with signal 11, Segmentation fault.
#0 IA__gtk_widget_show (widget=0x0) at gtkwidget.c:2217
 in gtkwidget.c
#0 IA__gtk_widget_show (widget=0x0) at gtkwidget.c:2217
No locals.
#1 0x00002b0396fc948a in IA__g_closure_invoke (closure=0x6be180, return_value=0x0, n_param_values=1, param_values=0x7fff169285c0,
    invocation_hint=0x7fff16928490) at gclosure.c:490
 marshal = (GClosureMarshal) 0x2b0396fd5790 <IA__g_cclosure_marshal_VOID__VOID>
 marshal_data = (gpointer) 0x0
 __PRETTY_FUNCTION__ = "IA__g_closure_invoke"
#2 0x00002b0396fd8a08 in signal_emit_unlocked_R (node=0x64c9c0, detail=0, instance=0x66d630, emission_return=0x0,
    instance_and_params=0x7fff169285c0) at gsignal.c:2440
 tmp = <value optimized out>
 handler = (Handler *) 0x6ba640
 accumulator = (SignalAccumulator *) 0x0
 emission = {next = 0x7fff16928af0, instance = 0x66d630, ihint = {signal_id = 114, detail = 0, run_type = G_SIGNAL_RUN_FIRST},
  state = EMISSION_RUN, chain_type = 4}
 class_closure = (GClosure *) 0x64c950
 handler_list = (Handler *) 0x6ba640
 return_accu = (GValue *) 0x0
 accu = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0,
      v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0,
      v_double = 0, v_pointer = 0x0}}}
 signal_id = 114
 max_sequential_handler_number = 555
 return_value_altered = 1
#3 0x00002b0396fd9e43 in IA__g_signal_emit_valist (instance=0x66d630, signal_id=<value optimized out>, detail=0,
    var_args=0x7fff16928840) at gsignal.c:2199
 _cvalue = <value optimized out>
 _flags = <value optimized out>
 _vtable = <value optimized out>
 _cvalues = {{v_int = 8744164, v_long = 8744164, v_int64 = 8744164, v_double = 4.3201910340017777e-317, v_pointer = 0x856ce4}, {
    v_int = -1747613312, v_long = 47294432250240, v_int64 = 47294432250240, v_double = 2.3366554214409905e-310,
    v_pointer = 0x2b0397d58980}, {v_int = 8808384, v_long = 8808384, v_int64 = 8808384, v_double = 4.3519199297777026e-317,
    v_pointer = 0x8667c0}, {v_int = 129, v_long = 129, v_int64 = 129, v_double = 6.3734468313520804e-322, v_pointer = 0x81}, {
    v_int = 8808368, v_long = 8808368, v_int64 = 8808368, v_double = 4.3519120247273691e-317, v_pointer = 0x8667b0}, {v_int = 5,
    v_long = 5, v_int64 = 5, v_double = 2.4703282292062327e-323, v_pointer = 0x5}, {v_int = 80, v_long = 80, v_int64 = 80,
    v_double = 3.9525251667299724e-322, v_pointer = 0x50}, {v_int = -1749492740, v_long = 47294430370812, v_int64 = 47294430370812,
    v_double = 2.3366553285849096e-310, v_pointer = 0x2b0397b8dbfc}}
 _lcopy_format = <value optimized out>
 _n_values = <value optimized out>
 return_value = {g_type = 80, data = {{v_int = 8771488, v_uint = 8771488, v_long = 137447724960, v_ulong = 137447724960,
      v_int64 = 137447724960, v_uint64 = 137447724960, v_float = 1.22914727e-38, v_double = 6.7908199001772423e-313,
      v_pointer = 0x200085d7a0}, {v_int = 138969114...

Changed in gnome-media:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Does it happen every time you go to the preferences? How is your alsa config broken? The backtrace looks like a GTK issue

Revision history for this message
R Volgers (mr-wiseman) wrote :

Hi, sorry for the late reply. Luckily, this doesn't happen every time I go to prefs. In fact I haven't been able to reproduce it since.
My alsa config is now fixed after deleting some (trivial, or so I thought) custom config files left over from dapper (/etc/asound.conf and .asoundrc). Symptoms were all kinds of strange behaviour, esp. relating to multi-channel output (stuttering, refusing to play, non-working volume controls etc.).

Revision history for this message
R Volgers (mr-wiseman) wrote :

Ah, just to clarify, the custom changes I had made to my config files were an extra pcm to duplicate stereo to 5.1 in my .asoundrc and some code in asound.conf that made sure the correct sound card was used IIRC (I have onboard audio and a separate card). I no longer have the old asound.conf unfortunately.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Does that mean that reverting your custom changes made it work again?

Changed in gnome-media:
status: Confirmed → Needs Info
Revision history for this message
Michael Wohlmuther (mwohlmuther) wrote :

Gnome Volume Control crashed when raising the volume for "master"

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

Michael, thank you for your bug interest. The bug you used to comment is a different one that the one you are facing though (duplicate from bug #65822) which creates confusing. If you are not sure of what you are doing could you rather open a new bug, the bugsquad will direct you to the right place then.

Revision history for this message
Jisnot (nhs6abdzsy) wrote :

I was playing with the gnome-volume-control sliders (changing the master volume, etc) and it managed to crash itself. Find attached a crash dump.

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

No reply, bug closed. Feel free to reopen with the asked informations if you still get that problem

Changed in gnome-media:
status: Needs Info → Rejected
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.