Bug 472899 – crash in Rhythmbox Music Player: nothing...look firefox

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 472899 - crash in Rhythmbox Music Player: nothing...look firefox


Summary:	crash in Rhythmbox Music Player: nothing...look firefox


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-09-02 18:20 UTC by sagaiina
Modified:	2007-09-03 11:41 UTC

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

Description sagaiina 2007-09-02 18:20:16 UTC

What were you doing when the application crashed?
nothing...look firefox 


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.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 301064192 vsize: 301064192 resident: 189870080 share: 30224384 rss: 189870080 rss_rlim: 4294967295
CPU usage: start_time: 1188799799 rtime: 3366 utime: 3127 stime: 239 cutime:1 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 -1209181648 (LWP 4574)]
[New Thread -1336992880 (LWP 4677)]
[New Thread -1284277360 (LWP 4583)]
[New Thread -1260717168 (LWP 4580)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 159885

Thread 2 (Thread -1336992880 (LWP 4677))

#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 __assert_fail
from /lib/libc.so.6
#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_CallFunction
from /usr/lib/libpython2.5.so.1.0
#14 PyErr_WarnEx
from /usr/lib/libpython2.5.so.1.0
#15 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#16 g_logv
from /lib/libglib-2.0.so.0
#17 g_log
from /lib/libglib-2.0.so.0
#18 g_type_check_instance_cast
from /lib/libgobject-2.0.so.0
#19 ??
from /usr/lib/gstreamer-0.10/libgstgnomevfs.so
#20 gnome_vfs_module_callback_invoke
from /usr/lib/libgnomevfs-2.so.0
#21 ??
from /usr/lib/gnome-vfs-2.0/modules/libhttp.so
#22 ??
from /usr/lib/gnome-vfs-2.0/modules/libhttp.so
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
from /usr/lib/gnome-vfs-2.0/modules/libhttp.so
#28 ??
#29 ??



----------- .xsession-errors ---------------------
  Resource id:  0x1807516
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x1807516
sys:1: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
rhythmbox: Python/ceval.c:2920: set_exc_info: Assertion `frame != ((void *)0)' 失敗。
** (rhythmbox:4574): CRITICAL **: Resources for ring buffer 0x9cebe80 still acquired
(bug-buddy:4679): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: 第 1 行第 40 個字發生錯誤：元素‘b’已關閉，但開啟中的元素是‘span’
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x3f
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-09-03 11:41:19 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 ***