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 455631 - crash in Rhythmbox Music Player: Pressed Play while an ap...
crash in Rhythmbox Music Player: Pressed Play while an ap...
Status: RESOLVED DUPLICATE of bug 413801
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-10 18:01 UTC by tom.judd62
Modified: 2007-07-11 08:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description tom.judd62 2007-07-10 18:01:13 UTC
What were you doing when the application crashed?
Pressed Play while an application using OSS had control of the audio hardware. Completely reproducable.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 177184768 vsize: 177184768 resident: 49975296 share: 37335040 rss: 49975296 rss_rlim: 4294967295
CPU usage: start_time: 1184090284 rtime: 305 utime: 270 stime: 35 cutime:7 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208903120 (LWP 5448)]
[New Thread -1313277040 (LWP 5468)]
[New Thread -1292297328 (LWP 5467)]
[New Thread -1302787184 (LWP 5466)]
[New Thread -1281807472 (LWP 5455)]
(no debugging symbols found)
0x00ecd402 in __kernel_vsyscall ()

Thread 3 (Thread -1292297328 (LWP 5467))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/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/libgstreamer-0.10.so.0
  • #27 gst_pad_get_caps
    from /usr/lib/libgstreamer-0.10.so.0
  • #28 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #29 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #30 gst_pad_link
    from /usr/lib/libgstreamer-0.10.so.0
  • #31 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #32 gst_element_link_pads
    from /usr/lib/libgstreamer-0.10.so.0
  • #33 ??
    from /usr/lib/gstreamer-0.10/libgstplaybin.so
  • #34 ??
    from /usr/lib/gstreamer-0.10/libgstplaybin.so
  • #35 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #36 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #37 ??
    from /lib/libgobject-2.0.so.0
  • #38 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #39 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #40 gst_element_no_more_pads
    from /usr/lib/libgstreamer-0.10.so.0
  • #41 ??
    from /usr/lib/gstreamer-0.10/libgstdecodebin.so
  • #42 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #43 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #44 ??
    from /lib/libgobject-2.0.so.0
  • #45 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #46 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #47 gst_element_no_more_pads
    from /usr/lib/libgstreamer-0.10.so.0
  • #48 ??
    from /usr/lib/gstreamer-0.10/libgstqtdemux.so
  • #49 ??
    from /usr/lib/gstreamer-0.10/libgstqtdemux.so
  • #50 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #51 ??
    from /lib/libglib-2.0.so.0
  • #52 ??
    from /lib/libglib-2.0.so.0
  • #53 start_thread
    from /lib/libpthread.so.0
  • #54 clone
    from /lib/libc.so.6


----------- .xsession-errors (18 sec old) ---------------------
observer added
snooze time is:null
considering alarm for item:NRUFC meeting
 offset:-PT15M, which makes alarm time:2007/06/12 18:45:00 UTC
now is 2007/07/10 16:10:19 UTC
Last ack was:2007/06/17 13:28:30 UTC
NRUFC meeting - alarm previously ackd2
observer removed
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(rhythmbox:3150): Rhythmbox-WARNING **: Unable to stop mDNS browsing: MDNS service is not running
(rhythmbox:5448): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running
Xlib: unexpected async reply (sequence 0xa154)!
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-11 08:53:40 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 ***