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 503961 - crash in Multimedia Systems Selector: trying to detect my onbo...
crash in Multimedia Systems Selector: trying to detect my onbo...
Status: RESOLVED DUPLICATE of bug 455030
Product: gnome-media
Classification: Deprecated
Component: gstreamer-properties
2.18.x
Other All
: High critical
: ---
Assigned To: gnome media maintainers
gnome media maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-17 01:42 UTC by jlove1221
Modified: 2008-01-19 14:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jlove1221 2007-12-17 01:42:43 UTC
Version: 2.18.0

What were you doing when the application crashed?
trying to detect my onboard sound card



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 356982784 vsize: 356982784 resident: 17395712 share: 11796480 rss: 17395712 rss_rlim: 18446744073709551615
CPU usage: start_time: 1197855690 rtime: 46 utime: 39 stime: 7 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gstreamer-properties'

(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 46912496402400 (LWP 3710)]
[New Thread 1084229968 (LWP 3731)]
(no debugging symbols found)
0x0000003ee320d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496402400 (LWP 3710))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /usr/lib64/libgstbase-0.10.so.0
  • #4 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #5 gst_pad_get_caps
    from /usr/lib64/libgstreamer-0.10.so.0
  • #6 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #7 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #8 gst_pad_get_caps
    from /usr/lib64/libgstreamer-0.10.so.0
  • #9 gst_pad_peer_get_caps
    from /usr/lib64/libgstreamer-0.10.so.0
  • #10 ??
    from /usr/lib64/libgstbase-0.10.so.0
  • #11 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #12 gst_pad_get_caps
    from /usr/lib64/libgstreamer-0.10.so.0
  • #13 gst_pad_peer_get_caps
    from /usr/lib64/libgstreamer-0.10.so.0
  • #14 ??
    from /usr/lib64/libgstbase-0.10.so.0
  • #15 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #16 gst_pad_get_caps
    from /usr/lib64/libgstreamer-0.10.so.0
  • #17 gst_pad_peer_get_caps
    from /usr/lib64/libgstreamer-0.10.so.0
  • #18 ??
    from /usr/lib64/libgstbase-0.10.so.0
  • #19 ??
    from /usr/lib64/libgstbase-0.10.so.0
  • #20 ??
    from /usr/lib64/libgstbase-0.10.so.0
  • #21 gst_pad_activate_push
    from /usr/lib64/libgstreamer-0.10.so.0
  • #22 gst_pad_set_active
    from /usr/lib64/libgstreamer-0.10.so.0
  • #23 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #24 gst_iterator_fold
    from /usr/lib64/libgstreamer-0.10.so.0
  • #25 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #26 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #27 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #28 ??
    from /usr/lib64/libgstbase-0.10.so.0
  • #29 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #30 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #31 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #32 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #33 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #34 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #35 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #36 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #37 user_test_pipeline
  • #38 _start
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (12 sec old) ---------------------
gstreamer-properties-Message: Skipping unavailable plugin 'v4l2src'
gstreamer-properties-Message: Skipping unavailable plugin 'esdmon'
gstreamer-properties-Message: Skipping unavailable plugin 'pulsesrc'
gstreamer-properties-Message: Error running pipeline 'ALSA - Advanced Linux Sound Architecture': Could not open resource for writing. [gstalsasink.c(625): gst_alsasink_open (): /pipeline0/alsasink3:
Playback open error on device 'default': No such device]
gstreamer-properties-Message: Error running pipeline 'ALSA - Advanced Linux Sound Architecture': Could not open resource for writing. [gstalsasink.c(625): gst_alsasink_open (): /pipeline1/alsasink4:
Playback open error on device 'default': No such device]
gstreamer-properties-Message: Error running pipeline 'OSS - Open Sound System': Could not open resource for writing. [gstalsasink.c(625): gst_alsasink_open (): /pipeline2/alsasink5:
Playback open error on device 'default': No such device]
gstreamer-properties-Message: Error running pipeline 'Custom': Could not open resource for writing. [gstalsasink.c(625): gst_alsasink_open (): /pipeline3/alsasink6:
Playback open error on device 'default': No such device]
gstreamer-properties-Message: Error running pipeline 'Silence': Could not open resource for writing. [gstalsasink.c(625): gst_alsasink_open (): /pipeline4/alsasink7:
Playback open error on device 'default': No such device]
gstreamer-properties-Message: Error running pipeline 'Test Sound': Could not open resource for writing. [gstalsasink.c(625): gst_alsasink_open (): /pipeline5/alsasink8:
Playback open error on device 'default': No such device]
--------------------------------------------------
Comment 1 Marc-Andre Lureau 2008-01-19 14:16:15 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 455030 ***