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 499639 - crash in Rhythmbox Music Player: pressing the next button...
crash in Rhythmbox Music Player: pressing the next button...
Status: RESOLVED DUPLICATE of bug 434996
Product: rhythmbox
Classification: Other
Component: general
0.10.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-25 23:57 UTC by gsafford
Modified: 2007-11-27 14:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description gsafford 2007-11-25 23:57:32 UTC 
Version: 0.10.1

What were you doing when the application crashed?
pressing the next button to advance to the next shuffled song.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 149233664 vsize: 149233664 resident: 58195968 share: 27619328 rss: 58195968 rss_rlim: 4294967295
CPU usage: start_time: 1196010834 rtime: 23402 utime: 18270 stime: 5132 cutime:16 cstime: 18 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 -1209132496 (LWP 15258)]
[New Thread -1256916080 (LWP 16711)]
[New Thread -1222710384 (LWP 16672)]
[New Thread -1235125360 (LWP 15263)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 179632

Thread 2 (Thread -1256916080 (LWP 16711))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 g_object_set_valist
    from /lib/libgobject-2.0.so.0
  • #6 g_object_set
    from /lib/libgobject-2.0.so.0
  • #7 ??
    from /usr/lib/gstreamer-0.10/libgstplaybin.so
  • #8 ??
    from /usr/lib/gstreamer-0.10/libgstplaybin.so
  • #9 ??
    from /usr/lib/gstreamer-0.10/libgstplaybin.so
  • #10 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #12 ??
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #15 gst_element_no_more_pads
    from /usr/lib/libgstreamer-0.10.so.0
  • #16 ??
    from /usr/lib/gstreamer-0.10/libgstdecodebin.so
  • #17 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #22 gst_element_no_more_pads
    from /usr/lib/libgstreamer-0.10.so.0
  • #23 ??
    from /usr/lib/gstreamer-0.10/libgstqtdemux.so
  • #24 ??
    from /usr/lib/gstreamer-0.10/libgstqtdemux.so
  • #25 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #26 ??
    from /lib/libglib-2.0.so.0
  • #27 ??
    from /lib/libglib-2.0.so.0
  • #28 start_thread
    from /lib/libpthread.so.0
  • #29 clone
    from /lib/libc.so.6 


----------- .xsession-errors (11 sec old) ---------------------
    gnomevfs.async.open (url, self.open_cb, data=("", callback, args))
TypeError: Cannot build a gnomevfs.URI
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-11-27 14:06:38 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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