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 460764 - crash in Rhythmbox Music Player: i was trying to play a s...
crash in Rhythmbox Music Player: i was trying to play a s...
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-07-26 22:39 UTC by ali_sendme
Modified: 2007-07-28 15:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ali_sendme 2007-07-26 22:39:40 UTC
What were you doing when the application crashed?
i was trying to play a save .wav extension file...


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: Fedora

Memory status: size: 143351808 vsize: 143351808 resident: 37769216 share: 23678976 rss: 37769216 rss_rlim: 4294967295
CPU usage: start_time: 1185467730 rtime: 228 utime: 215 stime: 13 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 -1208796624 (LWP 5460)]
[New Thread -1277011056 (LWP 5476)]
[New Thread -1266127984 (LWP 5472)]
[New Thread -1220486256 (LWP 5468)]
[New Thread -1244808304 (LWP 5466)]
(no debugging symbols found)
0x00ad6402 in __kernel_vsyscall ()

Thread 1 (Thread -1208796624 (LWP 5460))

  • #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 PyInstance_New
    from /usr/lib/libpython2.5.so.1.0
  • #12 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #13 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #14 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #15 ??
    from /usr/lib/libpython2.5.so.1.0
  • #16 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #17 ??
    from /usr/lib/libpython2.5.so.1.0
  • #18 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #19 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #20 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #21 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #22 ??
    from /lib/libexpat.so.0
  • #23 ??
    from /lib/libexpat.so.0
  • #24 XML_ParseBuffer
    from /lib/libexpat.so.0
  • #25 XML_Parse
    from /lib/libexpat.so.0
  • #26 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #27 PyCFunction_Call
    from /usr/lib/libpython2.5.so.1.0
  • #28 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #29 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #30 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #31 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #32 ??
    from /usr/lib/libpython2.5.so.1.0
  • #33 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #34 ??
    from /usr/lib/libpython2.5.so.1.0
  • #35 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #36 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #37 PyEval_CallFunction
    from /usr/lib/libpython2.5.so.1.0
  • #38 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gnomevfs/_gnomevfs.so
  • #39 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #40 ??
  • #41 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (8 sec old) ---------------------
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4d specified for 0x3e00201 (Twinkle - ).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4d specified for 0x3e00fb2 (Twinkle - ).
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400021 (Music Play)
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'
/usr/lib/python2.5/site-packages/_xmlplus/sax/xmlreader.py:282: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
  self._attrs = attrs
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-28 15:34:25 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 ***