Bug 411346 – crash in Volume Control: it crashed at system sta...

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 411346 - crash in Volume Control: it crashed at system sta...


Summary:	crash in Volume Control: it crashed at system sta...


Status:	RESOLVED INCOMPLETE

Product:	gnome-applets
Classification:	Other
Component:	mixer
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-applets Maintainers
QA Contact:	gnome-applets Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-23 20:20 UTC by prem
Modified:	2007-06-30 14:35 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description prem 2007-02-23 20:20:37 UTC

What were you doing when the application crashed?
it crashed at system startup


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 19537920 vsize: 0 resident: 19537920 share: 0 rss: 6606848 rss_rlim: 0
CPU usage: start_time: 1172261977 rtime: 0 utime: 16 stime: 0 cutime:13 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/mixer_applet2'

(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 -1226336592 (LWP 4576)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 113326

Thread 1 (Thread -1226336592 (LWP 4576))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 pthread_mutex_lock
from /lib/tls/i686/cmov/libpthread.so.0
#5 bonobo_object_add_interface
from /usr/lib/libbonobo-2.so.0
#6 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#7 g_object_set
from /usr/lib/libgobject-2.0.so.0
#8 bonobo_object_add_interface
from /usr/lib/libbonobo-2.so.0
#9 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#10 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_object_new
from /usr/lib/libgobject-2.0.so.0
#12 bonobo_generic_factory_new_closure
from /usr/lib/libbonobo-2.so.0
#13 bonobo_generic_factory_new
from /usr/lib/libbonobo-2.so.0
#14 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#15 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#16 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#17 panel_applet_factory_main
from /usr/lib/libpanel-applet-2.so.0
#18 main
#0 __kernel_vsyscall

Comment 1 palfrey 2007-04-30 14:38:54 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 Bruno Boaventura 2007-06-30 14:35:24 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!