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 441191 - crash in Rhythmbox Music Player: I clicked on Magnatune, ...
crash in Rhythmbox Music Player: I clicked on Magnatune, ...
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-25 13:39 UTC by jbrothers
Modified: 2007-06-03 10:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jbrothers 2007-05-25 13:39:53 UTC 
What were you doing when the application crashed?
I clicked on Magnatune, waited for the song list to be populated, and double-clicked on Goa Life by Ambient Teknology. Rhythmbox failed to play it or the next five tracks of the album, marking them with red circles as it attempted, then crashed at the eighth track, On The Floor.


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.3163.fc7 #1 SMP Tue May 15 20:35:22 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 703074304 vsize: 703074304 resident: 66437120 share: 20516864 rss: 66437120 rss_rlim: 18446744073709551615
CPU usage: start_time: 1180100068 rtime: 638 utime: 591 stime: 47 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496366704 (LWP 12138)]
[New Thread 1115699536 (LWP 12161)]
[New Thread 1105209680 (LWP 12160)]
[New Thread 1084229968 (LWP 12154)]
[New Thread 1094719824 (LWP 12142)]
(no debugging symbols found)
0x0000003b2980d7cf in waitpid () from /lib64/libpthread.so.0

+ Trace 135997

Thread 1 (Thread 46912496366704 (LWP 12138))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #4 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #5 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #6 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #7 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #8 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #9 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #10 PyEval_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #11 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #12 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #13 PyEval_CallObjectWithKeywords
    from /usr/lib64/libpython2.5.so.1.0
  • #14 ??
    from /usr/lib64/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #15 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #16 ??
    from /lib64/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Philip Withnall





          2007-06-03 10:27:09 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 ***