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 513329 - crash in Volume Control: it crashed at startup
crash in Volume Control: it crashed at startup
Status: RESOLVED DUPLICATE of bug 513018
Product: gnome-applets
Classification: Other
Component: mixer
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-31 01:28 UTC by devotion97
Modified: 2008-01-31 11:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description devotion97 2008-01-31 01:28:23 UTC
What were you doing when the application crashed?
it crashed at startup


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 31870976 vsize: 31870976 resident: 10797056 share: 7831552 rss: 10797056 rss_rlim: 4294967295
CPU usage: start_time: 1201742788 rtime: 16 utime: 12 stime: 4 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2'

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

Thread 1 (Thread 0xb6e7b6b0 (LWP 9315))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
    from /usr/lib/libgthread-2.0.so.0
  • #12 ??
  • #13 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #14 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #15 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #16 ??
  • #17 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #18 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #19 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #20 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #21 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #22 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #23 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #24 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #25 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #26 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #27 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #28 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #29 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #30 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #31 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #32 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #33 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #34 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #35 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #36 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #37 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #38 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #39 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #40 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #41 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #42 gst_structure_set_parent_refcount
    from /usr/lib/libgstreamer-0.10.so.0
  • #43 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #44 ??
  • #45 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(nautilus:9272): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sugah\s.gnome2\snautilus-scripts\snautilus_scripts_tar_gz\sFile%20System%20Management' to action group 'Scri
(nautilus:9272): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sugah\s.gnome2\snautilus-scripts\snautilus_scripts_tar_gz\sFile%20System%20Management' to action group 'Scri
(nautilus:9272): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sugah\s.gnome2\snautilus-scripts\snautilus_scripts_tar_gz\sMultimedia' to action group 'ScriptsGroup'
(nautilus:9272): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sugah\s.gnome2\snautilus-scripts\snautilus_scripts_tar_gz\sMultimedia' to action group 'ScriptsGroup'
(nautilus:9272): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sugah\s.gnome2\snautilus-scripts\snautilus_scripts_tar_gz\sObsolete' to action group 'ScriptsGroup'
(nautilus:9272): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sugah\s.gnome2\snautilus-scripts\snautilus_scripts_tar_gz\sObsolete' to action group 'ScriptsGroup'
(nautilus:9272): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sugah\s.gnome2\snautilus-scripts\snautilus_scripts_tar_gz\sSystem%20Configuration' to action group 'ScriptsG
(nautilus:9272): Gtk-WARNING **: Refusing to add non-unique action 'submenu_file:\s\s\shome\sugah\s.gnome2\snautilus-scripts\snautilus_scripts_tar_gz\sSystem%20Configuration' to action group 'ScriptsG
--------------------------------------------------
Comment 1 Gianluca Borello 2008-01-31 11:31:07 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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