GNOME Bugzilla – Bug 594276
crash in Rhythmbox Music Player: executed shell.get_playe...
Last modified: 2009-09-05 23:44:02 UTC
Version: 0.12.4 What were you doing when the application crashed? executed shell.get_player().props.source in rhythmbox python console Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.30-1-686 #1 SMP Sat Aug 15 19:11:58 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10603000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 172634112 vsize: 172634112 resident: 66248704 share: 26497024 rss: 66248704 rss_rlim: 18446744073709551615 CPU usage: start_time: 1252186489 rtime: 39620 utime: 36531 stime: 3089 cutime:0 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0xad2b9b90 (LWP 4371)] [New Thread 0xb529db90 (LWP 4367)] [New Thread 0xb5076b90 (LWP 3372)] 0xb7f41424 in __kernel_vsyscall ()
+ Trace 217350
Thread 1 (Thread 0xb6489760 (LWP 3360))
---- Critical and fatal warnings logged during execution ---- ** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed ** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed ** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed ** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed ----------- .xsession-errors (45065 sec old) --------------------- (firefox-bin:31920): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:31920): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:31920): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:31920): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:31920): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:31920): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:31920): Gdk-WARNING **: XID collision, trouble ahead ...Too much output, ignoring rest... --------------------------------------------------
*** This bug has been marked as a duplicate of bug 580022 ***