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 786771 - Critical about mismatched GdkDisplays when opening Inspector combobox
Critical about mismatched GdkDisplays when opening Inspector combobox
Status: RESOLVED DUPLICATE of bug 468868
Product: gtk+
Classification: Platform
Component: Widget: GtkComboBox
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2017-08-24 19:39 UTC by Daniel Boles
Modified: 2017-08-27 21:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Daniel Boles 2017-08-24 19:39:25 UTC 
With GTK+ 3.22.17 on Debian unstable, on X11 (at least), opening the Inspector over any program, and trying to open the ComboBox from the Objects tab > Show Details button:

> Gdk-CRITICAL **: gdk_device_grab: assertion 'gdk_window_get_display (window) == gdk_device_get_display (device)' failed

The popup does not open; the button just stays depressed (and thus, so do I).

I haven't been able to replicate this with the ComboBoxes in gtk3-demo or testcombo. Also, due to the version, it's not related to the recent change in grabbing on GtkButton (which hit GTK+ 3 only).

Perhaps strangely, though, GTK+ 4 does not exhibit this.
Comment 1 Daniel Boles 2017-08-24 20:27:47 UTC 
D'oh. I forgot I had a ~/.config/gtk-3.0/gtk.css that enforced -GtkComboBox-appears-as-list, as part of tests for the other 100 bugs about that monstrosity.

With the non-deprecated menu type ComboBox, as solely used in GTK+ 4, this doesn't happen.

Something is really wrong with -appears-as-list, and it may be one or multiple problems; I won't bother keeping this one open until some headway is made with the others, to ascertain how many issues we're dealing with.
Comment 2 Daniel Boles 2017-08-27 21:12:40 UTC 

*** This bug has been marked as a duplicate of bug 468868 ***