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 456534 - crash in Rhythmbox Music Player: I was listening some tra...
crash in Rhythmbox Music Player: I was listening some tra...
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 10:23 UTC by fausto_ltec
Modified: 2007-07-15 00:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description fausto_ltec 2007-07-13 10:23:47 UTC 
What were you doing when the application crashed?
I was listening some tracks on Jamendo Source, then I gave a click on Magnature and in a glance another click on Radio.

The stations were shown to me but was impossible to choose one because the reporting bug tool appeared...

Hope to be useful :$


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 296456192 vsize: 296456192 resident: 211550208 share: 25772032 rss: 211550208 rss_rlim: 4294967295
CPU usage: start_time: 1184316186 rtime: 23122 utime: 22232 stime: 890 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 -1208833488 (LWP 7990)]
[New Thread -1310991472 (LWP 11393)]
[New Thread -1233704048 (LWP 11327)]
[New Thread -1245004912 (LWP 7997)]
(no debugging symbols found)
0x00bf9402 in __kernel_vsyscall ()

+ Trace 147735

Thread 1 (Thread -1208833488 (LWP 7990))

  • #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/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #12 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #13 ??
    from /lib/libexpat.so.0
  • #14 ??
    from /lib/libexpat.so.0
  • #15 ??
    from /lib/libexpat.so.0
  • #16 ??
    from /lib/libexpat.so.0
  • #17 XML_ParseBuffer
    from /lib/libexpat.so.0
  • #18 XML_Parse
    from /lib/libexpat.so.0
  • #19 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #20 PyCFunction_Call
    from /usr/lib/libpython2.5.so.1.0
  • #21 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #22 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #23 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #24 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #25 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #26 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #27 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #28 ??
    from /usr/lib/libpython2.5.so.1.0
  • #29 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #30 ??
    from /usr/lib/libpython2.5.so.1.0
  • #31 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #32 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #33 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #34 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #35 ??
    from /lib/libglib-2.0.so.0
  • #36 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #37 ??
    from /lib/libglib-2.0.so.0
  • #38 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #39 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libpython2.5.so.1.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgstpbutils-0.10.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libvorbisenc.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libvorbis.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-15 00:51:44 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 ***