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 493376 - 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-11-04 14:45 UTC by leongyh74
Modified: 2007-11-05 08:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description leongyh74 2007-11-04 14:45:09 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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 310710272 vsize: 310710272 resident: 29863936 share: 26185728 rss: 29863936 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194187023 rtime: 21 utime: 11 stime: 10 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 46912496336560 (LWP 2929)]
(no debugging symbols found)
0x00000038ac80d945 in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496336560 (LWP 2929))

  • #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 (159 sec old) ---------------------
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
CalDAV Eplugin starting up ...
** (evolution:2962): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2962): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
python: can't open file '/usr/lib/python2.5/site-packages/deluge/update.py': [Errno 2] No such file or directory
python: can't open file '/usr/lib/python2.5/site-packages/deluge/info.py': [Errno 2] No such file or directory
(evolution:2962): e-data-server-DEBUG: Loading categories from "/home/lyh/.evolution/categories.xml"
(evolution:2962): e-data-server-DEBUG: Loaded 15 categories
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
--------------------------------------------------
Comment 1 Christoph Wolk 2007-11-05 08:01:42 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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