GNOME Bugzilla – Bug 461743
crash in Rhythmbox Music Player: open flash file .swf ...
Last modified: 2007-08-02 10:37:44 UTC
What were you doing when the application crashed? open flash file .swf 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.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 135229440 vsize: 135229440 resident: 52215808 share: 23502848 rss: 52215808 rss_rlim: 4294967295 CPU usage: start_time: 1185822068 rtime: 785 utime: 752 stime: 33 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 -1208686032 (LWP 5319)] [New Thread -1287423088 (LWP 5354)] [New Thread -1240740976 (LWP 5351)] [New Thread -1266025584 (LWP 5328)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 151555
Thread 2 (Thread -1287423088 (LWP 5354))
----------- .xsession-errors (2060 sec old) --------------------- QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error QFile::readBlock: Null pointer error ...Too much output, ignoring rest... --------------------------------------------------
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 434003 ***