Bug 437837 – crash in Rhythmbox Music Player: clicking on song in Magn...

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 437837 - crash in Rhythmbox Music Player: clicking on song in Magn...


Summary:	crash in Rhythmbox Music Player: clicking on song in Magn...


Status:	RESOLVED DUPLICATE of bug 436456

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.10.0
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-12 07:29 UTC by dtvarnum
Modified:	2007-05-20 10:23 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description dtvarnum 2007-05-12 07:29:31 UTC

What were you doing when the application crashed?
clicking on song in Magntune


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.3116.fc7 #1 SMP Thu Apr 26 10:36:44 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: 232804352 vsize: 232804352 resident: 153169920 share: 17952768 rss: 153169920 rss_rlim: 4294967295
CPU usage: start_time: 1178954862 rtime: 2486 utime: 2371 stime: 115 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 -1208649472 (LWP 3219)]
[New Thread -1220834416 (LWP 3237)]
[New Thread -1235223664 (LWP 3225)]
(no debugging symbols found)
0x00172402 in __kernel_vsyscall ()

+ Trace 133752

Thread 1 (Thread -1208649472 (LWP 3219))

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



----------- .xsession-errors (71 sec old) ---------------------
localuser:dtvarnum being added to access control list
SESSION_MANAGER=local/localhost:/tmp/.ICE-unix/2855
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-05-20 10:23: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 ***