Bug 445214 – crash in Rhythmbox Music Player: Forsøgte at lukke progra...

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 445214 - crash in Rhythmbox Music Player: Forsøgte at lukke progra...


Summary:	crash in Rhythmbox Music Player: Forsøgte at lukke progra...


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-07 17:55 UTC by lasse
Modified:	2007-06-07 23:13 UTC

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

Description lasse 2007-06-07 17:55:28 UTC

What were you doing when the application crashed?
Forsøgte at lukke programmet mens det (vist nok) forsøgte at oprette forbindelse til radiostation.


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: 185036800 vsize: 185036800 resident: 52039680 share: 18169856 rss: 52039680 rss_rlim: 4294967295
CPU usage: start_time: 1181238702 rtime: 1461 utime: 1403 stime: 58 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 -1208743376 (LWP 3376)]
[New Thread -1304437872 (LWP 3521)]
[New Thread -1247093872 (LWP 3389)]
[New Thread -1220826224 (LWP 3381)]
[New Thread -1234154608 (LWP 3380)]
(no debugging symbols found)
0x001ee402 in __kernel_vsyscall ()

+ Trace 139138

Thread 1 (Thread -1208743376 (LWP 3376))

#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_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#6 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#7 ??
from /usr/lib/libpython2.5.so.1.0
#8 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#9 ??
from /usr/lib/libpython2.5.so.1.0
#10 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#11 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#12 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#13 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#14 ??
from /lib/libexpat.so.0
#15 ??
from /lib/libexpat.so.0
#16 ??
from /lib/libexpat.so.0
#17 ??
from /lib/libexpat.so.0
#18 XML_ParseBuffer
from /lib/libexpat.so.0
#19 XML_Parse
from /lib/libexpat.so.0
#20 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#21 PyCFunction_Call
from /usr/lib/libpython2.5.so.1.0
#22 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#23 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#24 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#25 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#26 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#27 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#28 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#29 ??
from /usr/lib/libpython2.5.so.1.0
#30 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#31 ??
from /usr/lib/libpython2.5.so.1.0
#32 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#33 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#34 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#35 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#36 ??
from /lib/libglib-2.0.so.0
#37 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#38 ??
from /lib/libglib-2.0.so.0
#39 g_main_loop_run
from /lib/libglib-2.0.so.0
#40 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#41 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
/usr/lib/python2.5/site-packages/_xmlplus/dom/minidom.py:291: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
  childNodes.append(node)
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-06-07 23:13:21 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 ***