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 439733 - crash in Rhythmbox Music Player: Trying to do "Play Queue...
crash in Rhythmbox Music Player: Trying to do "Play Queue...
Status: RESOLVED DUPLICATE of bug 436456
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-19 17:16 UTC by jdalby
Modified: 2007-05-20 10:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jdalby 2007-05-19 17:16:22 UTC
What were you doing when the application crashed?
Trying to do "Play Queue" having just enqueued 2 songs found on magnatune.com


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

System: Linux 2.6.21-1.3174.fc7 #1 SMP Fri May 18 17:36:46 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 124411904 vsize: 124411904 resident: 44740608 share: 17850368 rss: 44740608 rss_rlim: 4294967295
CPU usage: start_time: 1179594866 rtime: 1001 utime: 961 stime: 40 cutime:2 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 -1208833488 (LWP 5494)]
[New Thread -1257960560 (LWP 5520)]
[New Thread -1245906032 (LWP 5503)]
(no debugging symbols found)
0x00bba402 in __kernel_vsyscall ()

Thread 1 (Thread -1208833488 (LWP 5494))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #5 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #6 ??
    from /usr/lib/libpython2.5.so.1.0
  • #7 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #8 ??
    from /usr/lib/libpython2.5.so.1.0
  • #9 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #10 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #11 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #12 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #13 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #20 gdk_window_process_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #21 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gtk/_gtk.so
  • #22 PyCFunction_Call
    from /usr/lib/libpython2.5.so.1.0
  • #23 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #24 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #25 ??
    from /usr/lib/libpython2.5.so.1.0
  • #26 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #27 ??
    from /usr/lib/libpython2.5.so.1.0
  • #28 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #29 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #30 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #31 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #32 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #33 ??
    from /lib/libgobject-2.0.so.0
  • #34 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #35 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #36 gtk_widget_size_allocate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 g_cclosure_marshal_VOID__BOXED
    from /lib/libgobject-2.0.so.0
  • #39 ??
    from /lib/libgobject-2.0.so.0
  • #40 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #41 ??
    from /lib/libgobject-2.0.so.0
  • #42 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #43 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #44 gtk_widget_size_allocate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 g_cclosure_marshal_VOID__BOXED
    from /lib/libgobject-2.0.so.0
  • #47 ??
    from /lib/libgobject-2.0.so.0
  • #48 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #49 ??
    from /lib/libgobject-2.0.so.0
  • #50 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #51 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #52 gtk_widget_size_allocate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #53 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #54 g_cclosure_marshal_VOID__BOXED
    from /lib/libgobject-2.0.so.0
  • #55 ??
    from /lib/libgobject-2.0.so.0
  • #56 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #57 ??
    from /lib/libgobject-2.0.so.0
  • #58 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #59 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #60 gtk_widget_size_allocate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #61 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #62 g_cclosure_marshal_VOID__BOXED
    from /lib/libgobject-2.0.so.0
  • #63 ??
    from /lib/libgobject-2.0.so.0
  • #64 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #65 ??
    from /lib/libgobject-2.0.so.0
  • #66 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #67 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #68 gtk_widget_size_allocate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #69 gtk_container_resize_children
    from /usr/lib/libgtk-x11-2.0.so.0
  • #70 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #71 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #72 ??
    from /lib/libgobject-2.0.so.0
  • #73 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #74 ??
    from /lib/libgobject-2.0.so.0
  • #75 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #76 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #77 gtk_container_check_resize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #78 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #79 ??
    from /lib/libglib-2.0.so.0
  • #80 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #81 ??
    from /lib/libglib-2.0.so.0
  • #82 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #83 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #84 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (15 sec old) ---------------------
No stack.
The program 'gnome-terminal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 100 error_code 2 request_code 78 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
sys:1: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
/usr/lib/rhythmbox/plugins/artdisplay/__init__.py:165: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
  event.window.draw_pixbuf (None, draw_pb, x, y, x, y, min (w, self.size - x), min (h, self.size - y))
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-05-20 10:28:02 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 436456 ***