After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 581633 - Critical warnings on login: assertion `xatom != None' failed
Critical warnings on login: assertion `xatom != None' failed
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: X11
2.17.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 593805 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-05-06 18:48 UTC by Vincent Untz
Modified: 2009-09-01 14:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
backtrace of the warning (7.43 KB, text/plain)
2009-05-21 10:43 UTC, Milan Crha 		Details

Description Vincent Untz 2009-05-06 18:48:45 UTC 
(smoketesting 2.27.1)

When logging in my 2.27.1, I get ~10 critical warnings like this:

(nautilus:7502): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed
Comment 1 Milan Crha 2009-05-21 10:43:53 UTC 
Created attachment 135079 [details]
backtrace of the warning

I see the same when drag&drop. Two samples above, one from evolution, one from gedit, file chooser. Might be a different thing, I do not know, but seems to be part of gdk, not any higher level application.
Comment 2 A. Walton 2009-05-21 11:15:42 UTC 
I'm seeing this too when I run gedit from a terminal. Probably not our fault then. Reassigning to gdk.
Comment 3 Johan Bilien 2009-06-09 16:45:24 UTC 
Looks like this would be fixed by the fix to bug# 580511  (4b16b875db66c72003606c4199b23899ed451e78)
Comment 4 Hernando Torque 2009-06-16 13:28:22 UTC 
I'm using Ubuntu 9.10 Alpha 2 (gtk+ 2.17.0-0ubuntu1) and I'm also seeing this (fix for bug 580511 should already be applied according to the package's changelog).
Comment 5 Hernando Torque 2009-06-17 07:48:26 UTC 
Seems fixed now with gtk+ 2.17.2-0ubuntu2.
Comment 6 A. Walton 2009-06-17 07:59:22 UTC 
Let's call it fixed then.
Comment 7 Claudio Saavedra 2009-09-01 14:40:58 UTC 
*** Bug 593805 has been marked as a duplicate of this bug. ***