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 443914 - crash in Rhythmbox Music Player: I just clicked play butt...
crash in Rhythmbox Music Player: I just clicked play butt...
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-06-04 12:31 UTC by tokegee
Modified: 2007-06-04 12:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description tokegee 2007-06-04 12:31:33 UTC
What were you doing when the application crashed?
I just clicked play buttom.


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:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 140492800 vsize: 140492800 resident: 42954752 share: 15949824 rss: 42954752 rss_rlim: 4294967295
CPU usage: start_time: 1180960070 rtime: 1755 utime: 1655 stime: 100 cutime:4 cstime: 1 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 -1208247760 (LWP 24953)]
[New Thread -1296155760 (LWP 24976)]
[New Thread -1225360496 (LWP 24965)]
[New Thread -1239192688 (LWP 24960)]
(no debugging symbols found)
0x007c6402 in __kernel_vsyscall ()

Thread 1 (Thread -1208247760 (LWP 24953))

  • #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/libpython2.5.so.1.0
  • #5 PyEval_GetGlobals
    from /usr/lib/libpython2.5.so.1.0
  • #6 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #7 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #8 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #9 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #10 ??
    from /lib/libexpat.so.0
  • #11 ??
    from /lib/libexpat.so.0
  • #12 ??
    from /lib/libexpat.so.0
  • #13 ??
    from /lib/libexpat.so.0
  • #14 XML_ParseBuffer
    from /lib/libexpat.so.0
  • #15 XML_Parse
    from /lib/libexpat.so.0
  • #16 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #17 PyCFunction_Call
    from /usr/lib/libpython2.5.so.1.0
  • #18 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #19 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #20 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #21 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #22 PyEval_EvalCodeEx
    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 ??
    from /lib/libglib-2.0.so.0
  • #33 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #34 ??
    from /lib/libglib-2.0.so.0
  • #35 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #36 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (36 sec old) ---------------------
QLayout "unnamed" added to QWidget "unnamed", which already has a layout
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3600007 specified for 0x3600252 (Kaffeine P).
~ScimInputContextPlugin()
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2400003 specified for 0x240012b (User Switc).
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400003 (Export Fil)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** 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
sys:1: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
sys:1: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
/usr/lib/python2.5/site-packages/_xmlplus/dom/expatbuilder.py:223: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
  parser.Parse(string, True)
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-04 12:33:06 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 ***