This reverts commit 0410b880.

meson.build has an explicit dependency on 2.79.2, for the Gio <->
GioUnix split[1]. 2.80 is the first stable release that satisfies that
dependency.

[1] https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/11a10214

This reverts commit 516827c2.

* Build-Depends: Drop versioned constraint on libibus-1.0-dev (>= 1.5.22-2ubuntu2~).
* Build-Depends: Drop versioned constraint on libpulse-dev (>= 13).
* gnome-shell: Drop versioned constraint on gir1.2-atspi-2.0 (>= 2.36) in Depends.
* gnome-shell: Drop versioned constraint on gir1.2-graphene-1.0 (>= 1.10.2) in Depends.
* gnome-shell: Drop versioned constraint on gir1.2-ibus-1.0 (>= 1.5.22-2ubuntu2~) in Depends.
* gnome-shell: Drop versioned constraint on gir1.2-malcontent-0 (>= 0.6.0) [linux-any] in Suggests.
* gnome-shell-common: Drop conflict with removed package gnome-shell (<< 3.36.1-6~) in Replaces.
* gnome-shell-common: Drop conflict with removed package gnome-shell (<< 3.36.1-6~) in Breaks.
* gnome-shell-extension-prefs: Drop conflict with removed package gnome-shell (<< 3.36.0-2) in Replaces.
* gnome-shell-extension-prefs: Drop conflict with removed package gnome-shell (<< 3.36.0-2) in Breaks.

Changes-By: deb-scrub-obsolete

This removes one of the reasons we need the legacy and
non-cross-friendly libgirepository1.0-dev.

In combination with the previous commit, this means we do not need to
build-depend on the legacy libgirepository1.0-dev.

Workaround for #1060838

libgcr-4-dev doesn't have a Provides on that name yet.

While yeah, it's technically possible to run gnome-shell 46
without gnome-control-center, there are several buttons
that wouldn't work: the network settings in the top right
system menu and those in the desktop right-click menu.

It's also just a poor user experience to try to have
GNOME Shell without gnome-control-center

Closes: #1077738

This reverts commit e0dc45b8.

This reverts commit 43703991.

I think these tests are running more reliably now

Now that we no longer provide a portal implementation ourselves,
the only expected callers are the GNOME portal implementation
and (since recently) the remote desktop daemon.

Make that explicit and restrict callers to these senders, like
we do for other D-Bus APIs.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3411>
(cherry picked from commit 1a12bd4f)

Instead, use CSS to request a monospace font selectively where
it makes sense (the evaluator).

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7776
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3413>
(cherry picked from commit 6f2c9914)

All styling currently happens on the ScrollView child, which
means that instead of a scrollbar inside the dialog to move
the content, we have a scrollbar next to the dialog that moves
the dialog as a whole.

Fix this by simply moving the style classes to the up-most parent.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3414>
(cherry picked from commit 811a4103)

Remove duplicate and unnecessary keys, and add missing ones
(e.g. ZWNJ).

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3409>
(cherry picked from commit 459981ef)

Besides building custom fedora images,  we will build
system extensions for GNOME OS. Since GNOME OS uses a
a different libdir compared to what meson defaults to,
we must allow setting libdir in this script.

See https://discourse.gnome.org/t/towards-a-better-way-to-hack-and-test-your-system-components/21075
See https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/837

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3390>
(cherry picked from commit dfafc972)

To build a system extension we need to:

1. Add dependencies to the container (to build it), and also
2. Add dependencies to the extension (to run it, later).

So there's effectively two locations where we need to install
those dependencies.

See https://discourse.gnome.org/t/towards-a-better-way-to-hack-and-test-your-system-components/21075
See https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/837

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3390>
(cherry picked from commit 2e5c3aec)

The eslint job occasionally fails because node hits an
illegal-instruction error. There's a chance that a package
update fixed that issue in the meantime, so rebuild the image.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3415>
(cherry picked from commit 6dc07b41)

In commit e69da360, Florian Müllner
wrote:

> We currently complete the animation using an onComplete handler,
> which only runs if the corresponding transition was stopped when
> finished.
>
> While it is unexpected that the transition is interrupted, it can
> apparently happen under some circumstances (like VMs with qlx).
> The consequences of that are pretty bad, mainly due to the cover
> pane that prevents input during the animation not getting removed.
>
> Address this by always completing the animation when the transition
> is stopped, regardless of whether it completed or not.

There are effectively four branches of the startup animation:

1. if Meta.is_restart() is true, no animation is run on startup; I
   believe this is the X11-only case of restarting the shell
   mid-session.
2. if Main.sessionMode.isGreeter is true, just the panel is eased onto
   the screen; this is the GDM case.
3. if Main.sessionMode.hasOverview is true, then a whole sequence of
   animations are run; this is the normal session case.
4. otherwise, the whole UI zooms in to full size, and from full
   transparency to full opacity; this is the Initial Setup case.

The fix above handles cases 2 and 4, but not 3. This patch applies the
same fix to case 3, so that the callback is always called on session
startup even if the transition is interrupted.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3422>
(cherry picked from commit 93b33cf3)

It wasn't possible to navigate by keyboard inside app folders due
to the focus being grabbed by the dialog. Changed vfunc_key_press_event()
to use the focus manager's navigate_from_event(), which is the same method
used by modal dialogs (also making use of the focus group already assigned
to AppFolderDialog).

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6331
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3338>
(cherry picked from commit 30615896)

The AppFolderDialog would lose keyboard focus after editing the title
(likely due to the folder entry grabbing key focus). This commit adds
navigate_focus() to _showFolderLabel() to send key focus back to the
dialog's elements after editing the title.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3338>
(cherry picked from commit a04b35b5)

When an app folder is opened it would do so without grabbing the
keyboard focus, so one could not navigate with the arrow keys without
pressing Tab. This adds the focus parameter to popup()'s grab, which
sets the key focus to the elements of the folder when it is opened.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3338>
(cherry picked from commit 9569239e)

During session startup, we have the following chain:

    LayoutManager._prepareStartupAnimation()
    `- LayoutManager._startupAnimation()
       `- LayoutManager._startupAnimationComplete()       (a)
       | or
       `- LayoutManager._startupAnimationGreeter()        (b)
       | or
       `- LayoutManager._startupAnimationSession()        (c)
          `- Overview.runStartupAnimation()               (d)
             `- OverviewActor.runStartupAnimation()       (e)
                `- ControlsManager.runStartupAnimation()  (f)

Branch (b) calls LayoutManager._startupAnimationComplete() once the
animation is complete. Branch (c) does the same, except that
ControlsManager.runStartupAnimation() is an async function that awaits
LayoutManager.ensureAllocation().

LayoutManager._prepareStartupAnimation() is an `async` function, and its
caller catches & logs any error it raises.

Previously, ControlsManager.runStartupAnimation() – (f) in the above
diagram – was declared `async`, because it uses `await` internally, but
also accepted a callback, which was called on successful completion of
the function and the animation it triggers.

If an exception is raised during execution of the function, its callback
would never be called, and because the promise it implicitly returns is
discarded, the exception would never be logged either. And, stepping a
few levels up the call stack, the callback that
LayoutManager._startupAnimationSession() (c) provided would never be
called, and so LayoutManager._startupAnimationComplete() would never be
called, meaning the cover pane that prevents input would never be
removed and the session would be unusable.

Remove the callback parameter from ControlsManager.runStartupAnimation()
(f), and instead make it resolve in the case where the callback would
previously have been called.

Remove the callback parameter from OverviewActor.runStartupAnimation()
(e) – it is just a wrapper around ControlsManager.runStartupAnimation().

Adjust Overview.runStartupAnimation() (d) accordingly: rather than
passing a callback to OverviewActor.runStartupAnimation(), await its
return and then proceed. There is a slight behaviour change here:
previously, in the branch where this._syncGrab() is false, the callback
would be called before calling this.hide(), whereas now this.hide() is
called before the async function returns.

Adjust LayoutManager._startupAnimationSession() and its siblings to be
async, rather than each calling _startupAnimationComplete() directly.
Finally, in _prepareStartupAnimation()  await _startupAnimation() either
succeeding or failing, and in either case call
_startupAnimationComplete(), removing the cover pane that prevents all
input.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3428>
(cherry picked from commit 3d061345)

Use the right variable. A static WirelessNetwork._securityTypes
variable does exist, but the correct variable when checking
autoconnect possibility is this._securityType; this._securityTypes
is undefined, causing clicking an enterprise network name in panel
network selector do nothing instead of properly opening GNOME
Settings panel.

Closes https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7698

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3426>
(cherry picked from commit a21558d6)

In the early days of shell development, someone accidentally pushed
their eclipse configuration. Most of it was removed at one point,
but one file was missed.

Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3432>
(cherry picked from commit 949af345)

Update NEWS.

Update to upstream version '46.4'
with Debian dir a73e4b5d22c3c446fbb77dbf47b15cedaecdb7cc

tagging package gnome-shell version debian/46.4-1

* tag 'debian/46.4-1': (41 commits)
  releasing package gnome-shell version 46.4-1
  New upstream release
  Bump version to 46.4
  cleanup: Remove left-over config file
  status/network: Fix enterprise network connecting from panel
  Make startup animation use async functions throughout
  appDisplay: Use AppFolderDialog grabHelper to obtain key focus on popup()
  appDisplay: Use navigate_focus() to keep focus after editing app folder title
  appDisplay: Use navigate_from_event() for keyboard focus in app folders
  overviewControls: Make sure startup animation completes
  ci: Rebuild javascript image
  ci: Support additional destdir in install-meson-project.sh
  ci: Support setting libdir in install-meson-project.sh
  osk-layouts: Fixed Persian OSK
  lookingGlass: Include ScrollView in inspector styling
  lookingGlass: Stop setting font programmatically
  accessDialog: Restrict senders
  releasing package gnome-shell version 46.3.1-4
  Bump Standards-Version to 4.7.0
  Skip the shell tests on riscv64
  ...

This reverts commit 909801b5.

This change was also made in Debian so we should revert it
on that side if desired

Debian's gnome-shell no longer has any direct dependency relationship with it

Gbp-Dch: Ignore