Bug 456066 – crash in Rhythmbox Music Player: clicking «play»

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 456066 - crash in Rhythmbox Music Player: clicking «play»


Summary:	crash in Rhythmbox Music Player: clicking «play»


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-07-11 23:40 UTC by mybudbuddyreport
Modified:	2007-07-12 10:10 UTC

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

Description mybudbuddyreport 2007-07-11 23:40:05 UTC

What were you doing when the application crashed?
clicking «play»


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Simple
Icon Theme: Fedora

Memory status: size: 171237376 vsize: 171237376 resident: 97292288 share: 24276992 rss: 97292288 rss_rlim: 4294967295
CPU usage: start_time: 1184197044 rtime: 1914 utime: 1834 stime: 80 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 -1208604112 (LWP 5587)]
[New Thread -1267737712 (LWP 5603)]
[New Thread -1257247856 (LWP 5596)]
(no debugging symbols found)
0x00d78402 in __kernel_vsyscall ()

+ Trace 147382

Thread 1 (Thread -1208604112 (LWP 5587))

#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 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#12 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#13 ??
from /lib/libexpat.so.0
#14 ??
from /lib/libexpat.so.0
#15 XML_ParseBuffer
from /lib/libexpat.so.0
#16 XML_Parse
from /lib/libexpat.so.0
#17 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#18 PyCFunction_Call
from /usr/lib/libpython2.5.so.1.0
#19 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#20 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#21 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#22 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#23 ??
from /usr/lib/libpython2.5.so.1.0
#24 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#25 ??
from /usr/lib/libpython2.5.so.1.0
#26 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#27 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#28 PyEval_CallFunction
from /usr/lib/libpython2.5.so.1.0
#29 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gnomevfs/_gnomevfs.so
#30 ??
from /usr/lib/libgnomevfs-2.so.0
#31 ??
#32 ??
#0 __kernel_vsyscall



----------- .xsession-errors (134 sec old) ---------------------
in emp_apps_open_in
** Message: <info>  Deactivating the current VPN connection.
** Message: <info>  Activating VPN connection 'Uni Bern'.
** Message: <info>  Activating VPN connection 'Uni Bern'.
** (gecko:5494): WARNING **: Format der Bilddatei unbekannt
** (gecko:5494): WARNING **: Format der Bilddatei unbekannt
Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c00023 (Musik-Play)
Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-12 10:10:44 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 ***