Package Details: microsoft-edge-stable-bin 131.0.2903.51-1

Git Clone URL: https://aur.archlinux.org/microsoft-edge-stable-bin.git (read-only, click to copy)
Package Base: microsoft-edge-stable-bin
Description: A browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier
Upstream URL: https://www.microsoftedgeinsider.com/en-us/download
Keywords: browser chromium web
Licenses: custom
Conflicts: edge, edge-stable, edge-stable-bin, microsoft-edge-stable
Provides: edge-stable, microsoft-edge-stable
Submitter: nicomix
Maintainer: aakashhemadri
Last Packager: aakashhemadri
Votes: 125
Popularity: 2.99
First Submitted: 2021-10-29 02:42 (UTC)
Last Updated: 2024-11-15 23:01 (UTC)

Dependencies (11)

Required by (5)

Sources (2)

Pinned Comments

Littletiger commented on 2024-04-23 17:13 (UTC)

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

aakashhemadri commented on 2022-03-29 13:23 (UTC) (edited on 2022-03-29 13:24 (UTC) by aakashhemadri)

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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 16 Next › Last »

petronny commented on 2023-11-15 06:38 (UTC)

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

Bot-wxt1221 commented on 2023-11-12 01:18 (UTC) (edited on 2023-11-12 01:19 (UTC) by Bot-wxt1221)

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

mfmAURuser-name commented on 2023-11-11 14:58 (UTC)

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

Bot-wxt1221 commented on 2023-11-11 13:08 (UTC)

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.

detian commented on 2023-09-02 08:26 (UTC)

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.

detian commented on 2023-08-30 08:00 (UTC)

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

detian commented on 2023-08-30 07:55 (UTC) (edited on 2023-08-30 07:56 (UTC) by detian)

@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.

ItachiSan commented on 2023-08-30 07:35 (UTC)

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

ItachiSan commented on 2023-08-30 07:34 (UTC)

@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

ignxcy commented on 2023-08-24 08:15 (UTC)

no.