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 751447 - GtkSearchBar takes up half the height of gnome-system-monitor's window
GtkSearchBar takes up half the height of gnome-system-monitor's window
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
3.17.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 752189 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-06-24 15:08 UTC by Michael Catanzaro
Modified: 2015-07-09 21:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gnome-system-monitor screenshot in Weston (316.76 KB, image/png)
2015-06-24 15:08 UTC, Michael Catanzaro
Details
Screenshot showing search bar activated (396.52 KB, image/png)
2015-06-24 15:09 UTC, Michael Catanzaro
Details

Description Michael Catanzaro 2015-06-24 15:08:54 UTC
Created attachment 306015 [details]
gnome-system-monitor screenshot in Weston

The upper half of process list is gray when running in Wayland.

Turns out it's the GtkSearchBar. :)

Screenshots attached
Comment 1 Michael Catanzaro 2015-06-24 15:09:17 UTC
Created attachment 306016 [details]
Screenshot showing search bar activated
Comment 2 Michael Catanzaro 2015-06-24 22:32:08 UTC
Turns out this has nothing to do with Weston, just with GTK+ 3.17.2+. Oops.

I bisected it:

a921229246d99c28c14ffa060b3cc77ce4a649c1 is the first bad commit
commit a921229246d99c28c14ffa060b3cc77ce4a649c1
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Sat May 2 18:23:20 2015 -0400

    GtkSearchBar: Simplify ui template
Comment 3 Matthias Clasen 2015-06-25 11:00:31 UTC
Thanks for the bisection. Turns out setting vexpand explicitly to its default value has a side-effect.
Comment 4 Michael Catanzaro 2015-06-25 12:15:49 UTC
(In reply to Matthias Clasen from comment #3)
> Thanks for the bisection. Turns out setting vexpand explicitly to its
> default value has a side-effect.

(Methinks this is crazy, but whatever, thanks for the fix!)
Comment 5 Robert Roth 2015-07-09 21:22:48 UTC
*** Bug 752189 has been marked as a duplicate of this bug. ***