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 457162 - crash in Rhythmbox Music Player: I had clicked Magnatune ...
crash in Rhythmbox Music Player: I had clicked 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-07-15 18:00 UTC by jeffchillemi
Modified: 2007-07-16 22:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jeffchillemi 2007-07-15 18:00:22 UTC
What were you doing when the application crashed?
I had clicked Magnatune and when all the songs came up, I just double clicked one.  It then put the red circle (looks like do not enter sign) next to that song and proceeded down the list, putting that error icon next to every song.  I tried to stop it by clicking the buttons at the top and right clicking when the bug buddy window appeared.


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: 131817472 vsize: 131817472 resident: 53334016 share: 18264064 rss: 53334016 rss_rlim: 4294967295
CPU usage: start_time: 1184522164 rtime: 665 utime: 627 stime: 38 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 -1209038288 (LWP 4080)]
[New Thread -1230939248 (LWP 4098)]
[New Thread -1220449392 (LWP 4086)]
(no debugging symbols found)
0x00a17402 in __kernel_vsyscall ()

Thread 1 (Thread -1209038288 (LWP 4080))

  • #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 ??
    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_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #32 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #33 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #34 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #35 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #36 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #37 ??
    from /usr/lib/libpython2.5.so.1.0
  • #38 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #39 ??
    from /usr/lib/libpython2.5.so.1.0
  • #40 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #41 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #42 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #43 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #44 ??
    from /lib/libglib-2.0.so.0
  • #45 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #46 ??
    from /lib/libglib-2.0.so.0
  • #47 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #48 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (78 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3000003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (gnome-default-printer:3951): WARNING **: IPP request failed with status 1030
** (gnome-default-printer:3951): WARNING **: IPP request failed with status 1030
** (gnome-default-printer:3951): WARNING **: IPP request failed with status 1030
** (gnome-default-printer:3951): WARNING **: IPP request failed with status 1030
** (gnome-default-printer:3951): WARNING **: Couldn't find default printer  in list!
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800021 (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: Received a _NET_WM_MOVERESIZE message for 0x3800021 (Music Play); these messages lack timestamps and therefore suck.
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-16 22:09:47 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 ***