> > (audacious2:7539): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: > > assertion `atom != GDK_NONE' failed > > Hmm. We don't call gdk_x11_atom_to_xatom_for_display in Audacious as > far as I know, but I will have someone more familiar with the skins > interface look at it.
Hi, I just came across this same error in a program of mine, and happened to notice it in audacious2 today too. I dug a bit deeper, and this code is usually not called directly. I.e. a call to gtk_dialog_run() can cause this, as it calls gdk_window_set_modal_hint () which a few levels down translates to a call to gdk_x11_atom_to_xatom_for_display (). I just have no clue why the lookup for a cached atom returns null. I also noticed bug # 533128 , where someone noted that this only happens on dual head machines (I am on dual head too). How about the reporter for this bug? Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
