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 735338 - The inspector sometimes doesn't show up
The inspector sometimes doesn't show up
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Debugging
3.13.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2014-08-24 20:08 UTC by Sébastien Wilmet
Modified: 2018-04-15 00:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sébastien Wilmet 2014-08-24 20:08:44 UTC
Launching the inspector on the gtk3-demo main window doesn't work, the inspector is not shown. I use the Ctrl+Shift+D shortcut.

The dialog "Do you want to use GTK+ Inspector?" is shown, but not the inspector window.

When the inspector window should be shown, there is a graphic artifact (I use Xfce).

The inspector works fine when a gtk3-demo component is shown. For example double-click on "Application Class" in the side panel, then Ctrl+Shift+D, and the inspector is correctly shown.
Comment 1 Matthias Clasen 2014-09-26 13:20:04 UTC
After spending some time debugging this, it turns out the culprit is the treeview code. It passes key events to its search entry, which is in a separate toplevel window. So the Ctrl-Shift-d propagates all the way up to that window, where the enable-debugging keybinding is triggered. But the treeview still returns FALSE from its key press handler, causing the event to be propagated up the treeviews own widget ancestry as well, until it ends up in another window, where it gets handled again. Since this is a toggle key binding, we end up turning the inspector on and off with the same key event.
Comment 2 Matthias Clasen 2018-02-10 05:06:16 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 3 Matthias Clasen 2018-04-15 00:26:36 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new