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 456731 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
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-13 21:53 UTC by sandro.santos
Modified: 2007-07-15 00:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sandro.santos 2007-07-13 21:53:29 UTC
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (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: Enforcing
Accessibility: Disabled
GTK+ Theme: BlueHeart
Icon Theme: Neu

Memory status: size: 281534464 vsize: 281534464 resident: 173711360 share: 26292224 rss: 173711360 rss_rlim: 4294967295
CPU usage: start_time: 1184363160 rtime: 2780 utime: 2715 stime: 65 cutime:1 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 -1208829392 (LWP 5899)]
[New Thread -1279689840 (LWP 14340)]
[New Thread -1258710128 (LWP 14338)]
[New Thread -1269199984 (LWP 14288)]
[New Thread -1248191600 (LWP 14237)]
[New Thread -1290179696 (LWP 14236)]
[New Thread -1300669552 (LWP 14214)]
[New Thread -1311159408 (LWP 13856)]
[New Thread -1236440176 (LWP 5903)]
(no debugging symbols found)
0x00e85402 in __kernel_vsyscall ()

Thread 1 (Thread -1208829392 (LWP 5899))

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


----------- .xsession-errors (1341 sec old) ---------------------
Video: no video
Starting playback...
A:   1.6 (01.5) of 222.0 (03:42.0) ??,?%                                        
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
Starting playback...
A:   3.0 (03.0) of 201.0 (03:21.0) ??,?%                                        
A:   1.6 (01.5) of 181.0 (03:01.0) ??,?%                                        
Video: no video
Starting playback...
A:   1.6 (01.5) of 238.0 (03:58.0) ??,?%                                        
A:   1.6 (01.6) of 222.0 (03:42.0) ??,?%                                        
A:   1.6 (01.6) of 222.0 (03:42.0) ??,
Exiting... (Exit)
A:  13.7 (13.6) of 222.0 (03:42.0)  1.1%                                        
A:  15.1 (15.0) of 201.0 (03:21.0)  1.1%                                        
A:  13.7 (13.6) of 181.0 (03:01.0)  1.
Exiting... (Exit)
A:  14.2 (14.2) of 222.0 (03:42.0)  1.1%                                        
A:  15.6 (15.6) of 201.0 (03:21.0)  1.1%                                        
A:  14.2 (14.2) of 222.0 (03:42.0)  1.
Exiting... (Exit)
A:  16.1 (16.0) of 201.0 (03:21.0)  1.1%                                        
A:  16.1 (16.0) of 201.0 (03:21.0)  1.1%                                        
A:  16.1 (16.1) of 201.0 (03:21.0)  1.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-15 00:25:30 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 ***