a91b6439ba
There have been several bugs in the past that caused invalid transitions of the `shown` state, such as going from `showing` to `showing`. These cause consecutive emissions of the `showing` signal, which can confuse other classes such as the search controller which connects to the stage `key-press-event` on showing and disconnects again on `hiding`. Having two consecutive `showing` signals will cause it to connect twice, and only disconnect once when hiding the overview again. This will lead to key presses getting repeated in the search until the session is restarted. Because there is no obvious connection to how and when this issue got triggered, this now adds some validation code that only allows valid transitions and throws an error otherwise so we get a backtrace of the code actually causing the problem. This does not fix the issue(s) causing the invalid state transitions, it only adds a way of tracking them down. Related: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4651 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2514>
GNOME Shell
GNOME Shell provides core user interface functions for the GNOME desktop, like switching to windows and launching applications. GNOME Shell takes advantage of the capabilities of modern graphics hardware and introduces innovative user interface concepts to provide a visually attractive and easy to use experience.
For more information about GNOME Shell, including instructions on how to build GNOME Shell from source and how to get involved with the project, see the project wiki.
Bugs should be reported to the GNOME bug tracking system. Please refer to the Schedule wiki page to see the supported versions.
Contributing
To contribute, open merge requests at https://gitlab.gnome.org/GNOME/gnome-shell.
Commit messages should follow the GNOME commit message
guidelines. If a merge request
fixes an existing issue, it is good practice to append the full issue URL
to each commit message. Try to always prefix commit subjects with a relevant
topic, such as panel: or status/network:, and it's always better to write
too much in the commit message body than too little.
Default branch
The default development branch is main. If you still have a local
checkout under the old name, use:
git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main
License
GNOME Shell is distributed under the terms of the GNU General Public License, version 2 or later. See the COPYING file for details.