Unable to change window state with keyboard in gnome shell (such as Always on _Top - <Alt+Space+t>)

[Norbert]

Steps to reproduce:
1. Install Ubuntu 17.10
2. Login to the default Ubuntu session
3. Open any windowed application such as Nautilus or `gnome-terminal`
3. Click <Alt+Space> to show current window settings
4. Try to set "Always on Top" property with keyboard shortcut (<t>)

Expected results:
* window reacts on <t> and set on top as requested

Actual results:
* window does not react on <t>

Notes:
"Always on Top" is just an illustration. Mnemonics for other (Minimize, Maximize, Move, Resize, Always on Visible Workspace, Move to workspace down, etc) do not defined and do work too.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 17:18:12 2017
DisplayManager: gdm3
GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2017-10-21 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Norbert (nrbrtx)]

This problem of using <x> for Maximize was mentioned on AskUbuntu (see https://askubuntu.com/q/967131/66509 ).

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Marco Trevisan (Treviño) (3v1n0)]

Submit the bug upstream and we can also work on a solution on this, I don't think there's no reason why it couldn't be accepted.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1710421, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.