GNOME Bugzilla – Bug 623750
crash in Rhythmbox:
Last modified: 2010-07-07 14:55:39 UTC
Version: 0.12.8 What were you doing when the application crashed? Distribution: Debian squeeze/sid Gnome Release: 2.30.0 2010-04-26 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.34-bfs304 #1 SMP PREEMPT Tue Jun 15 09:13:15 EEST 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 283181056 vsize: 283181056 resident: 46280704 share: 21159936 rss: 46280704 rss_rlim: 18446744073709551615 CPU usage: start_time: 1278476134 rtime: 147973 utime: 6574 stime: 141399 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0xa9c63b70 (LWP 7898)] [New Thread 0xab469b70 (LWP 7897)] [New Thread 0xb2285b70 (LWP 7896)] [New Thread 0xaa464b70 (LWP 7891)] [New Thread 0xaac65b70 (LWP 19319)] [New Thread 0xabc6ab70 (LWP 19227)] [New Thread 0xb10ffb70 (LWP 19223)] 0xffffe424 in __kernel_vsyscall ()
+ Trace 222728
Thread 5 (Thread 0xaa464b70 (LWP 7891))
Inferior 1 [process 19219] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (35318 sec old) --------------------- (seamonkey-bin:16103): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:16103): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:16103): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:16103): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:16103): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:16103): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:16103): Gdk-WARNING **: XID collision, trouble ahead ...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 bug 612156 ***