GNOME Bugzilla – Bug 507200
crash in Rhythmbox Music Player: Rhythmbox svn trunk r5529 (post 0.11.4 release)
Last modified: 2008-01-04 08:14:42 UTC
Version: 0.11.4 What were you doing when the application crashed? Rhythmbox svn trunk 5529 (post 0.11.4) crashed when quiting rhythmbox. Distribution: Unknown Gnome Release: 2.20.2 2007-12-11 (Archlinux) BugBuddy Version: 2.20.1 System: Linux 2.6.23-ARCH #1 SMP PREEMPT Fri Dec 21 19:39:35 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: gnome Memory status: size: 112390144 vsize: 112390144 resident: 42409984 share: 19857408 rss: 42409984 rss_rlim: 4294967295 CPU usage: start_time: 1199431921 rtime: 12102 utime: 11287 stime: 815 cutime:13 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6a3e6d0 (LWP 12616)] [New Thread 0xb27f9b90 (LWP 12787)] [New Thread 0xb539eb90 (LWP 12622)] 0xb7f4f410 in __kernel_vsyscall ()
+ Trace 184021
Thread 2 (Thread 0xb27f9b90 (LWP 12787))
----------- .xsession-errors --------------------- (rhythmbox:12616): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry->refcount > 0' failed (rhythmbox:12616): RhythmDB-CRITICAL **: rhythmdb_entry_get_double: assertion `entry != NULL' failed (rhythmbox:12616): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry != NULL' failed (rhythmbox:12616): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry->refcount > 0' failed (rhythmbox:12616): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed (rhythmbox:12616): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry != NULL' failed get ht990332 pop://ht990332@mail.lau.edu.lb/ Find Items 0 Cannot access memory at address 0x80 Cannot access memory at address 0x80 --------------------------------------------------
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 465946 ***