After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 332259 - Volume control crashed unexpectedly
Volume control crashed unexpectedly
Status: RESOLVED DUPLICATE of bug 171645
Product: gnome-media
Classification: Deprecated
Component: gnome-volume-control
2.14.x
Other other
: High critical
: ---
Assigned To: gnome media maintainers
gnome media maintainers
: 334555 342459 342590 357382 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-02-23 00:31 UTC by manuca
Modified: 2006-09-23 22:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description manuca 2006-02-23 00:31:26 UTC 
From:  <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.13.0
Subject: Volume control crashed unexpectedly

Distribution: Ubuntu 6.04 (dapper)
Package: gnome-applets
Severity: Normal
Version: GNOME2.13.91 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Volume control crashed unexpectedly
Bugzilla-Product: gnome-applets
Bugzilla-Component: mixer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.13.3)
Description:
Description of the crash:
I put up the volume and after loosing focus it crashed.


Debugging Information:

Backtrace was generated from '/usr/bin/gnome-volume-control'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 922289856 (LWP 8088)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 66420

Thread 1 (Thread 922289856 (LWP 8088))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gnome_volume_control_volume_ask
  • #5 gnome_volume_control_preferences_new
  • #6 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 main
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-02-23 00:31 -------
Comment 1 Sergej Kotliar 2006-03-14 18:55:09 UTC 
*** Bug 334555 has been marked as a duplicate of this bug. ***
Comment 2 Sebastien Bacher 2006-03-18 14:57:03 UTC 
https://launchpad.net/distros/ubuntu/+source/gnome-applets/+bug/34514 has a backtrace about that too:

"...
Starting program: /usr/bin/gnome-volume-control
[Thread debugging using libthread_db enabled]
[New Thread -1224403264 (LWP 9804)]

(gnome-volume-control:9804): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GnomeVolumeControlVolume'

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224403264 (LWP 9804)]
0x08051d9e in gnome_volume_control_volume_ask (vol=0x80ed9b0, real_zero=0xbf9ab614, slider_zero=0xbf9ab610)
    at volume.c:544
544       volumes = g_new (gint, vol->track->num_channels);
(gdb) thread apply all bt

+ Trace 67031

Thread 1 (Thread -1224403264 (LWP 9804))

  • #0 gnome_volume_control_volume_ask
    at volume.c line 544
  • #1 cb_check
    at track.c line 119
  • #2 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #5 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #6 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 main
    at main.c line 217 

I got this by enabling/disabling two separate PCM controls."
Comment 3 Sergej Kotliar 2006-05-22 18:34:03 UTC 
*** Bug 342590 has been marked as a duplicate of this bug. ***
Comment 4 Ronald Bultje 2006-05-29 17:01:22 UTC 
*** Bug 342459 has been marked as a duplicate of this bug. ***
Comment 5 Ronald Bultje 2006-06-15 21:23:13 UTC 

*** This bug has been marked as a duplicate of 171645 ***
Comment 6 Karsten Bräckelmann 2006-09-23 22:18:57 UTC 
*** Bug 357382 has been marked as a duplicate of this bug. ***