GNOME Bugzilla – Bug 449679
crash in Rhythmbox Music Player:
Last modified: 2007-06-21 10:17:31 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 243609600 vsize: 243609600 resident: 155004928 share: 17522688 rss: 155004928 rss_rlim: 4294967295 CPU usage: start_time: 1182412846 rtime: 9225 utime: 8578 stime: 647 cutime:4 cstime: 4 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209145632 (LWP 23065)] [New Thread -1356862576 (LWP 3753)] [New Thread -1313870960 (LWP 1248)] [New Thread -1270252656 (LWP 27000)] [New Thread -1248539760 (LWP 23095)] (no debugging symbols found) 0x00f51402 in __kernel_vsyscall ()
+ Trace 142579
Thread 1 (Thread -1209145632 (LWP 23065))
----------- .xsession-errors (13 sec old) --------------------- Major opcode: 158 Minor opcode: 6 Resource id: 0x180179d X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x180170e ** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3 rhythmbox: Python/ceval.c:2626: PyEval_EvalCodeEx: Assertion `tstate != ((void *)0)' failed. sys:1: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc' ** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x4d --------------------------------------------------
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 ***