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 449308 - crash in Sound: Went into Sound Preferen...
crash in Sound: Went into Sound Preferen...
Status: RESOLVED DUPLICATE of bug 413801
Product: gnome-control-center
Classification: Core
Component: Sound
2.19.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-19 23:20 UTC by yorkincr
Modified: 2007-06-20 02:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description yorkincr 2007-06-19 23:20:21 UTC
Version: 2.19.3

What were you doing when the application crashed?
Went into Sound Preferences because I was getting this message very often: "Couldn't open audio Please check that: Your soundcard is configured properly. You have the correct output plugin selected. No other Program is blocking the soundcard". This usually hapens when I am playing mp3 in xmm and another program produce any sound, for example, incoming message in kopete.


Distribution: Fedora release 7.89 (Rawhide)
Gnome Release: 2.19.3 2007-06-04 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.10.fc8xen #1 SMP Mon Jun 11 15:31:58 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 47681536 vsize: 47681536 resident: 23031808 share: 19992576 rss: 23031808 rss_rlim: 4294967295
CPU usage: start_time: 1182294969 rtime: 32 utime: 28 stime: 4 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-sound-properties'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209112864 (LWP 9151)]
(no debugging symbols found)
0x0021d402 in __kernel_vsyscall ()

Thread 1 (Thread -1209112864 (LWP 9151))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #5 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #6 gst_pad_get_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #7 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #8 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #9 gst_pad_get_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #10 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #11 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #12 gst_pad_get_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #13 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #14 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #15 gst_pad_get_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #16 gst_pad_peer_get_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #17 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #18 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #19 gst_pad_get_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #20 gst_pad_peer_get_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #21 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #22 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #23 gst_pad_get_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #24 gst_pad_peer_get_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #25 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #26 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #27 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #28 gst_pad_activate_push
    from /usr/lib/libgstreamer-0.10.so.0
  • #29 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #30 gst_pad_set_active
    from /usr/lib/libgstreamer-0.10.so.0
  • #31 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #32 gst_iterator_fold
    from /usr/lib/libgstreamer-0.10.so.0
  • #33 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #34 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #35 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #36 ??
    from /usr/lib/libgstbase-0.10.so.0
  • #37 gst_element_change_state
    from /usr/lib/libgstreamer-0.10.so.0
  • #38 gst_element_continue_state
    from /usr/lib/libgstreamer-0.10.so.0
  • #39 gst_element_change_state
    from /usr/lib/libgstreamer-0.10.so.0
  • #40 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #41 gst_element_set_state
    from /usr/lib/libgstreamer-0.10.so.0
  • #42 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #43 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #44 gst_element_change_state
    from /usr/lib/libgstreamer-0.10.so.0
  • #45 gst_element_continue_state
    from /usr/lib/libgstreamer-0.10.so.0
  • #46 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #47 gst_element_get_state
    from /usr/lib/libgstreamer-0.10.so.0
  • #48 user_test_pipeline
  • #49 _start
  • #0 __kernel_vsyscall


----------- .xsession-errors (9 sec old) ---------------------
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-20 02:04:05 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 413801 ***