Bug 442896 – crash in Rhythmbox Music Player: ijiDistribution: Fedora ...

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 442896 - crash in Rhythmbox Music Player: ijiDistribution: Fedora ...


Summary:	crash in Rhythmbox Music Player: ijiDistribution: Fedora ...


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-06-01 13:02 UTC by jjthomaskimo
Modified:	2007-06-15 11:21 UTC

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

Description jjthomaskimo 2007-06-01 13:02:53 UTC

What were you doing when the application crashed?
ijiDistribution: 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:47:07 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: 906694656 vsize: 906694656 resident: 226668544 share: 20463616 rss: 226668544 rss_rlim: 18446744073709551615
CPU usage: start_time: 1180702110 rtime: 2532 utime: 2392 stime: 140 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 46912496372288 (LWP 15618)]
[New Thread 1189394768 (LWP 15735)]
[New Thread 1178904912 (LWP 15699)]
[New Thread 1105475920 (LWP 15663)]
[New Thread 1094719824 (LWP 15630)]
(no debugging symbols found)
0x0000003ef680d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 137236

Thread 1 (Thread 46912496372288 (LWP 15618))

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

Comment 1 Jonathan Matthew 2007-06-15 11:21:04 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 ***