GNOME Bugzilla – Bug 449346
crash in Rhythmbox Music Player: Loading music
Last modified: 2007-06-20 21:49:31 UTC
What were you doing when the application crashed? Loading music Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (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: Clearlooks Icon Theme: Fedora Memory status: size: 241881088 vsize: 241881088 resident: 157536256 share: 23871488 rss: 157536256 rss_rlim: 4294967295 CPU usage: start_time: 1182309719 rtime: 5998 utime: 5823 stime: 175 cutime:4 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 -1208456656 (LWP 2475)] [New Thread -1255658608 (LWP 2565)] [New Thread -1244902512 (LWP 2564)] [New Thread -1233261680 (LWP 2481)] (no debugging symbols found) 0x005e5402 in __kernel_vsyscall ()
+ Trace 142318
Thread 1 (Thread -1208456656 (LWP 2475))
----------- .xsession-errors (21 sec old) --------------------- localuser:Rick being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2276 ** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3 rhythmbox: Objects/obmalloc.c:745: PyObject_Malloc: Assertion `bp != ((void *)0)' failed. /usr/lib/rhythmbox/plugins/artdisplay/__init__.py:160: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc' if self.merged_pixbuf.props.width != self.size: ** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3 --------------------------------------------------
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 ***