mutter:2486-mutter-crashes-on-xdg_activation-activate-request

Last commit made on 2022-12-06
Get this branch:
git clone -b 2486-mutter-crashes-on-xdg_activation-activate-request https://git.launchpad.net/mutter

Branch merges

Branch information

Name:
2486-mutter-crashes-on-xdg_activation-activate-request
Repository:
lp:mutter

Recent commits

88a53cc... by =?utf-8?q?Hunor_Csomort=C3=A1ni?= <email address hidden>

ci: Fix the expected name of the junit report

Tests are run with '--setup plain', expect testlog-plain.junit.xml as an
artifact name.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2733>

3d08365... by =?utf-8?q?Hunor_Csomort=C3=A1ni?= <email address hidden>

check-style: Improve the proposed git-rebase command

Include the sha used for the dry-run instead of using 'origin/main'.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2733>

ce4e58d... by =?utf-8?q?Hunor_Csomort=C3=A1ni?= <email address hidden>

check-style: Use run() instead of Popen()

The Python docs recommends using run() for all use-cases it can handle:
https://docs.python.org/3/library/subprocess.html#using-the-subprocess-module

run() waits for the subprocess started to complete, so it's not
necessary to use wait() and communicate() anymore. This simplifies the
script.

Previously running "check-style.py -r" after each commit in an
interactive rebase failed, b/c the script did not wait for the amend
command to complete. Using run() instead of Popen() solves this issue.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2733>

72a1791... by =?utf-8?q?Hunor_Csomort=C3=A1ni?= <email address hidden>

check-style: Don't turn off formatting when the chunk starts on line 1

Before this, new files introduced by the range of commits checked were
not considered for formatting b/c uncrustify was always turned off in
the beginning of the files, and never turned back on.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2733>

1493bf9... by =?utf-8?q?Hunor_Csomort=C3=A1ni?= <email address hidden>

check-style: Start enumerating lines from 1

This way "the line before start" and "the line before end" can be
expressed as "[start|end] - 1", which looks less like using a magic
number.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2733>

ec17d19... by Michael Webster

tiling: Remove unnecessary update_edge_constraints().

Both meta_window_maximize and meta_window_tile use
meta_window_maximize_internal(), and edge constraints are already
recalculated and updated there.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2579>

559e6ff... by Michael Webster

tiling: Skip the resize effect for tiled windows during user grabs.

meta_window_tile gets called by the grabbed window's match during
tile resizing. These incremental changes don't need to be animated.

Closes: #2246
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2579>

b1e08f6... by Georges Basile Stavracas Neto

frames/window-tracker: Trivial style cleanup

A space of indentation was missing.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2740>

62ddea3... by Georges Basile Stavracas Neto

frames: Add default-decoration CSS class

Add this CSS class both to the header bar itself, since it is what
actually contains the window controls, and to MetaFrameHeader too,
since it's what's directly attached to the window.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2740>

f7f88c1... by Georges Basile Stavracas Neto

frames/window-tracker: Initialize color scheme properly

Previous commit added support for setting the GTK4 theme setting
according to the color scheme setting. That's cool. What it didn't
add, though, was initializing the GTK4 theme setting to the proper
value. That means if the desktop starts at dark style, you'd still
get a light titlebar.

Fix that by updating the GTK4 theme setting on init as well.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2740>