Bug 515344 – crash in Rhythmbox Music Player:

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 515344 - crash in Rhythmbox Music Player:


Summary:	crash in Rhythmbox Music Player:


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:	2008-02-09 03:44 UTC by rpn_a
Modified:	2008-02-09 05:36 UTC

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

Description rpn_a 2008-02-09 03:44:22 UTC

What were you doing when the application crashed?



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: 182554624 vsize: 182554624 resident: 30064640 share: 16818176 rss: 30064640 rss_rlim: 4294967295
CPU usage: start_time: 1202528452 rtime: 404 utime: 368 stime: 36 cutime:2 cstime: 1 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 -1208780240 (LWP 3950)]
[New Thread -1308390512 (LWP 4124)]
[New Thread -1297900656 (LWP 4121)]
[New Thread -1287410800 (LWP 4108)]
[New Thread -1276920944 (LWP 4103)]
[New Thread -1230959728 (LWP 4100)]
[New Thread -1220469872 (LWP 4098)]
[New Thread -1329370224 (LWP 4094)]
[New Thread -1339860080 (LWP 4090)]
[New Thread -1350349936 (LWP 4086)]
[New Thread -1266431088 (LWP 3977)]
[New Thread -1244791920 (LWP 3958)]
(no debugging symbols found)
0x008d8402 in __kernel_vsyscall ()

+ Trace 188611

Thread 1 (Thread -1208780240 (LWP 3950))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 Py_FatalError
from /usr/lib/libpython2.5.so.1.0
#8 PyTuple_New
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 PyEval_EvalFrameEx
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_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#16 ??
from /usr/lib/libpython2.5.so.1.0
#17 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#18 ??
from /usr/lib/libpython2.5.so.1.0
#19 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#20 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#21 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#22 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#23 ??
from /lib/libglib-2.0.so.0
#24 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#25 ??
from /lib/libglib-2.0.so.0
#26 g_main_loop_run
from /lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
localuser:arif being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2613
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Fatal Python error: GC object already tracked
--------------------------------------------------

Comment 1 Jonathan Matthew 2008-02-09 05:36:05 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 ***