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 771100 - [gnome-terminal] menus are grayed out even the application is active
[gnome-terminal] menus are grayed out even the application is active
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Wayland
3.21.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: WaylandRelated
 
 
Reported: 2016-09-09 07:37 UTC by Kamil Páral
Modified: 2018-04-15 00:25 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
bug demonstration video (1.78 MB, video/webm)
2016-09-09 07:37 UTC, Kamil Páral 		Details

Description Kamil Páral 2016-09-09 07:37:31 UTC 
Created attachment 335153 [details]
bug demonstration video

If I start gnome-terminal, the menus are grayed out, like if the application was not focused. But it is. The menus are recolored properly (into white text) if I click on some of the menu, or if I do Alt+Tab to a different application and back. But on each start, they always look like inactive.

See the video.

This seems to be just a cosmetic issue, nothing else. But sometimes it confuses me, because I have the impression that a different application is focused, so I click inside gnome-terminal to focus it, and nothing happens... and then I realize the menus are just colored improperly.

gnome-terminal-3.21.90-2.fc25.x86_64
Comment 1 Kamil Páral 2016-09-09 07:38:07 UTC 
I should say I'm running Wayland.

gnome-session-wayland-session-3.21.90-1.fc25.x86_64
gnome-shell-3.21.91-1.fc25.x86_64
libwayland-client-1.11.92-1.fc25.x86_64
libwayland-cursor-1.11.92-1.fc25.x86_64
libwayland-server-1.11.92-1.fc25.x86_64
mesa-libwayland-egl-12.0.2-1.fc25.x86_64
mutter-3.21.91-2.fc25.x86_64
xorg-x11-server-Xwayland-1.18.4-5.fc25.x86_64
Comment 2 Kamil Páral 2016-09-09 07:40:24 UTC 
This does not happen on X11.
Comment 3 Christian Persch 2016-09-09 08:13:39 UTC 
It's a standard gtk+ menubar constructed by gtkuimanager, and g-t has zero wayland specific code. Therefore -> gtk+
Comment 4 Kamil Páral 2016-09-09 08:31:25 UTC 
The interesting thing is that I can't find any other app that would exhibit the same behavior. I can also reproduce this in a cleanly installed Fedora 25 VM.
Comment 5 Matthias Clasen 2016-09-10 12:28:46 UTC 
ndoes not reproduce here
Comment 6 Kamil Páral 2016-09-12 11:11:20 UTC 
If you can't reproduce on your local system, please download https://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20160911.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-25-20160911.n.0.iso and run it in a VM. Happens to me every time.
Comment 7 Olivier Fourdan 2016-09-28 08:38:49 UTC 
I can reproduce here as well, but funny thing is I can also reproduce with xfce4-terminal (on F25, built against gtk3 wtih Wayland support).
Comment 8 Matthias Clasen 2018-02-10 05:21:36 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 9 Matthias Clasen 2018-04-15 00:25:40 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