GNOME Bugzilla – Bug 506562
crash in Rhythmbox Music Player: trying to get to jamendo
Last modified: 2007-12-31 12:38:50 UTC
Version: 0.10.1 What were you doing when the application crashed? trying to get to jamendo Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 400044032 vsize: 400044032 resident: 312848384 share: 38113280 rss: 312848384 rss_rlim: 4294967295 CPU usage: start_time: 1198970772 rtime: 471705 utime: 449961 stime: 21744 cutime:5 cstime: 1 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 -1208755664 (LWP 7538)] [New Thread -1261438064 (LWP 7554)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183622
Thread 1 (Thread -1208755664 (LWP 7538))
----------- .xsession-errors (6 sec old) --------------------- - Arts::StereoVolumeControl - Arts::StereoEffectStack - Arts::Synth_BUS_DOWNLINK - Arts::SoundServerV2 - Arts::MidiManager warning: leaving MCOP Dispatcher and still 112 types alive. X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x26000bb (gecko:23490): Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed RhythmDB-ERROR **: file rhythmdb-property-model.c: line 653 (rhythmdb_property_model_delete_prop): assertion failed: ((ptr = g_hash_table_lookup (model->priv->reverse_map, propstr))) aborting... --------------------------------------------------
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 452703 ***