GNOME Bugzilla – Bug 555781
crash in Rhythmbox Music Player: attempting to use last.f...
Last modified: 2008-11-17 11:38:10 UTC
Version: 0.11.6 What were you doing when the application crashed? attempting to use last.fm playback; after getting to the bottom of the playlist (press next. repeatedly) it went into a loop cycling through each of the songs and marking them as unavailable Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Wed Oct 1 12:03:14 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10501000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 135004160 vsize: 135004160 resident: 60846080 share: 25440256 rss: 60846080 rss_rlim: 4294967295 CPU usage: start_time: 1223632681 rtime: 34487 utime: 33234 stime: 1253 cutime:11 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0xb64ed770 (LWP 22706)] [New Thread 0xaeafdb90 (LWP 31420)] [New Thread 0xb2ea1b90 (LWP 31405)] [New Thread 0xb516cb90 (LWP 22720)] 0xb7fd9424 in __kernel_vsyscall ()
+ Trace 207991
Thread 1 (Thread 0xb64ed770 (LWP 22706))
----------- .xsession-errors --------------------- (rhythmbox:22706): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed (rhythmbox:22706): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed (rhythmbox:22706): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed (rhythmbox:22706): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed (rhythmbox:22706): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong: assertion `entry != NULL' failed (rhythmbox:22706): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed ** RhythmDB:ERROR:rhythmdb-tree.c:1418:remove_child: assertion failed: (g_hash_table_remove (parent->children, data)) Cannot access memory at address 0x58b2 Cannot access memory at address 0x58b2 --------------------------------------------------
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 454247 ***