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.
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: | 127 |
Popularity: | 0.70 |
First Submitted: | 2021-10-29 02:42 (UTC) |
Last Updated: | 2025-04-17 20:00 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 16 Next › Last »
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
no.
When I start edge via PWA app, the command line in microsoft-edge-stable-flags.conf
are not applied, any way to fix this?
In order to perform a downgrade the correct way is to increment the epoch
in the PKGBUILD
, in this case setting it to 1
: https://wiki.archlinux.org/title/PKGBUILD#epoch
Apparently Microsoft withdrew stable version 115 from their repository: https://packages.microsoft.com/repos/edge/pool/main/m/microsoft-edge-stable/
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 meaakashhemadri 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.