GNOME Bugzilla – Bug 605152
crash in Rhythmbox: rhythmbox tried to advan...
Last modified: 2009-12-22 03:31:41 UTC
Version: 0.12.6 What were you doing when the application crashed? rhythmbox tried to advance to the next song Distribution: Mandriva Linux release 2010.1 (Cooker) for i586 Gnome Release: 2.29.3 2009-12-11 (Mandriva) BugBuddy Version: 2.28.0 System: Linux 2.6.32.1-desktop-1mnb #1 SMP Wed Dec 16 13:19:29 EST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10703000 Selinux: No Accessibility: Disabled GTK+ Theme: Galaxy Icon Theme: Echo GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 313475072 vsize: 313475072 resident: 88530944 share: 41242624 rss: 88530944 rss_rlim: 18446744073709551615 CPU usage: start_time: 1261417298 rtime: 5979 utime: 5195 stime: 784 cutime:2 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0xb63b46c0 (LWP 11647)] [New Thread 0xa7afeb70 (LWP 12242)] [New Thread 0xac6fdb70 (LWP 12241)] [New Thread 0xacefeb70 (LWP 12240)] [New Thread 0xad6ffb70 (LWP 12236)] [New Thread 0xb018fb70 (LWP 12221)] [New Thread 0xb359eb70 (LWP 11785)] 0xffffe424 in __kernel_vsyscall ()
+ Trace 219722
Thread 1 (Thread 0xb63b46c0 (LWP 11647))
----------- .xsession-errors (13 sec old) --------------------- (evolution:11537): camel-CRITICAL **: camel_message_info_free: assertion `mi != NULL' failed (<unknown>:11966): GLib-WARNING **: g_set_prgname() called multiple times (<unknown>:12001): GLib-WARNING **: g_set_prgname() called multiple times (<unknown>:12009): GLib-WARNING **: g_set_prgname() called multiple times (<unknown>:12016): GLib-WARNING **: g_set_prgname() called multiple times (<unknown>:12030): GLib-WARNING **: g_set_prgname() called multiple times (<unknown>:12034): GLib-WARNING **: g_set_prgname() called multiple times Missing separate debug info for /usr/lib/libmusicbrainz3.so.6 --------------------------------------------------
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 bug 482955 ***