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 489377 - crash in Volume Control:
crash in Volume Control:
Status: RESOLVED DUPLICATE of bug 463147
Product: gnome-applets
Classification: Other
Component: mixer
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-23 12:43 UTC by maxamx
Modified: 2007-10-23 18:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description maxamx 2007-10-23 12:43:57 UTC 
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 285601792 vsize: 285601792 resident: 20000768 share: 16318464 rss: 20000768 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193140996 rtime: 209 utime: 148 stime: 61 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496389808 (LWP 3226)]
(no debugging symbols found)
0x0000003c72c0d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 172208

Thread 1 (Thread 46912496389808 (LWP 3226))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gtk_vscale_new
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 __assert_fail
    from /lib64/libc.so.6
  • #6 snd_hctl_handle_events
    from /lib64/libasound.so.2
  • #7 snd_mixer_handle_events
    from /lib64/libasound.so.2
  • #8 gtk_vscale_new
    from /usr/lib64/gstreamer-0.10/libgstalsa.so
  • #9 gtk_vscale_new
    from /usr/lib64/gstreamer-0.10/libgstalsa.so
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 gtk_vscale_new
    from /lib64/libglib-2.0.so.0
  • #14 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #15 gtk_vscale_new
    from /lib64/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #17 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #18 bonobo_generic_factory_main_timeout
    from /usr/lib64/libbonobo-2.so.0
  • #19 panel_applet_factory_main_closure
    from /usr/lib64/libpanel-applet-2.so.0
  • #20 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
Could not set idle IO priority...attempting best effort 7 priority
Initializing nautilus-search-tool extension
Throttle level is 0
(nautilus:3121): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.5.so: cannot open shared object file: Arquivo ou diretório não encontrado
Traceback (most recent call last):
  File "/usr/lib64/python2.5/site-packages/gtk-2.0/gobject/__init__.py", line 30, in <module>
    from _gobject import *
ImportError: /usr/lib64/python2.5/site-packages/gtk-2.0/gobject/_gobject.so: undefined symbol: _Py_ZeroStruct
(nautilus:3121): Nautilus-Python-WARNING **: could not import gobject
kbuildsycoca running...
DCOP Cleaning up dead connections.
Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x4600012 especificada para 0x460043e (Senha Requ).
Aviso do gerenciador de janelas: Janela WM_TRANSIENT_FOR inválida 0x4600012 especificada para 0x460045b (Senha Requ).
--------------------------------------------------
Comment 1 Christoph Wolk 2007-10-23 18:28:21 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 463147 ***