Arch Linux User Repository

I was using --ozone-platform-hint=auto and having the startup issue in 124 as well, changing this to --ozone-platform=wayland fixed it for me

Please wait 30 minutes after a new update is released by Microsoft. The out-of-date flag sends an email notification to all those subscribed. If after a day the package stays out-of-date then please go ahead and flag the package as out-of-date to notify us.

Thanks for mentioning everyone, set it to the latest available and shutdown the update CI, will fix and turn it back on, thanks for the suggestion to use vercmp @petronny

@aakashhemadri Is the auto update CI fixed? Please call vercmp in your CI to ensure no downgrade.

What happened to this. What caused that?

Age Commit message (Expand) Author
14 min. Update microsoft-edge-stable to v119.0.2151.44  Aakash Hemadri
9 hours Update microsoft-edge-stable to v119.0.2151.58  Aakash Hemadri
10 hours    Update microsoft-edge-stable to v119.0.2151.44  Aakash Hemadri
11 hours    Update microsoft-edge-stable to v119.0.2151.58  Aakash Hemadri
12 hours    Update microsoft-edge-stable to v119.0.2151.44  Aakash Hemadri
19 hours    Update microsoft-edge-stable to v119.0.2151.58  Aakash Hemadri
22 hours    Update microsoft-edge-stable to v119.0.2151.44  Aakash Hemadri
27 hours    Update microsoft-edge-stable to v119.0.2151.58  Aakash Hemadri
29 hours    Update microsoft-edge-stable to v119.0.2151.44  Aakash Hemadri
31 hours    Update microsoft-edge-stable to v119.0.2151.58  Aakash Hemadri
34 hours    Update microsoft-edge-stable to v119.0.2151.44  Aakash Hemadri
45 hours    Update microsoft-edge-stable to v119.0.2151.58  Aakash Hemadri
47 hours    Update microsoft-edge-stable to v119.0.2151.44  Aakash Hemadri
2 days  Update microsoft-edge-stable to v119.0.2151.58  Aakash Hemadri
9 days  Update microsoft-edge-stable to v119.0.2151.44  Aakash Hemadri

Age        Commit message (Expand)
55 min.    Update microsoft-edge-stable to v119.0.2151.58
115 min.   Update microsoft-edge-stable to v119.0.2151.44
9 hours    Update microsoft-edge-stable to v119.0.2151.58
12 hours   Update microsoft-edge-stable to v119.0.2151.44
17 hours   Update microsoft-edge-stable to v119.0.2151.58
19 hours   Update microsoft-edge-stable to v119.0.2151.44
21 hours   Update microsoft-edge-stable to v119.0.2151.58
24 hours   Update microsoft-edge-stable to v119.0.2151.44
35 hours   Update microsoft-edge-stable to v119.0.2151.58
37 hours   Update microsoft-edge-stable to v119.0.2151.44
43 hours   Update microsoft-edge-stable to v119.0.2151.58
9 days     Update microsoft-edge-stable to v119.0.2151.44

Why bump to microsoft-edge-stable_119.0.2151.44-1_amd64.deb ?

microsoft-edge-stable_119.0.2151.58-1_amd64.deb is still exist.

Since installed PWA app are hard code to launch by /opt/microsoft/msedge/microsoft-edge, maybe change the #User flag aware launcher part in PKGBUILD to:

        # User flag aware launcher
        readflag_script=$(sed -z 's|\n|\\n|g' <<- "SHELL"

            # Make script fail if `cat` fails for some reason
            set -e

            # Set default value if variable is unset/null
            XDG_CONFIG_HOME="${XDG_CONFIG_HOME:-${HOME}/.config}"

            # Attempt to read a config file if it exists
            if [ -r "${XDG_CONFIG_HOME}/microsoft-edge-stable-flags.conf" ]; then
                EDGE_USER_FLAGS="$(cat "$XDG_CONFIG_HOME/microsoft-edge-stable-flags.conf")"
            fi

        SHELL
        ) && sed -i -z "s|#\n|$readflag_script|; /exec/{s|\"\$@\"|\$EDGE_USER_FLAGS \$@|}" \
            "${pkgdir}/opt/microsoft/${_pkgshortname}/${_pkgname}"

Will be better? Just edit /opt/microsoft/msedge/microsoft-edge to add ${XDG_CONFIG_HOME}/microsoft-edge-stable-flags.conf support, so flags will also be applied to PWA apps.

@ItachiSan now I just merge script /usr/bin/microsoft-edge-stable into /opt/microsoft/msedge/microsoft-edge to make my command line work

@ItachiSan find an issue page upstream:
https://bugs.chromium.org/p/chromium/issues/detail?id=1439149
looks like add --disable-features=AllowQt or --ui-toolkit=gtk to command line can work around this bug.

A recent update broke HiDPI support in Plasma Wayland... Am I the only one with this issue?

@detian I modified the launchers in

~/.local/share/applications

And ran on each of them sed for using the wrapper script, via:

for f in msedge-*.desktop
do
  echo "fixing $f"
  sed -i 's|/opt/microsoft/msedge/microsoft-edge|/usr/bin/microsoft-edge-stable|' $f
done