For those who cannot install/update, I have tried:
cd ~/.cache/yay/microsoft-edge-stable-bin/
makepkg -si
and it finished install the update.
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: | 3.45 |
First Submitted: | 2021-10-29 02:42 (UTC) |
Last Updated: | 2024-10-24 20:45 (UTC) |
For those who cannot install/update, I have tried:
cd ~/.cache/yay/microsoft-edge-stable-bin/
makepkg -si
and it finished install the update.
I am noticing a recent problem after an attempted upgrade. I uninstalled it and get the following when I attempt to reinstall. The message is the same for when it was failing to upgrade as well.
❯ yay -S microsoft-edge-stable-bin
AUR Explicit (1): microsoft-edge-stable-bin-128.0.2739.79-1
:: PKGBUILD up to date, skipping download: microsoft-edge-stable-bin
-> error merging /home/ding/.cache/yay/microsoft-edge-stable-bin: fatal: No current branch.
There's something wrong with the master branch, it is not pointing to HEAD.
Its evident by cloning the repo:
git clone https://aur.archlinux.org/microsoft-edge-stable-bin
Cloning into 'microsoft-edge-stable-bin'...
remote: Enumerating objects: 698, done.
remote: Counting objects: 100% (698/698), done.
remote: Compressing objects: 100% (79/79), done.
remote: Total 698 (delta 625), reused 688 (delta 617), pack-reused 0 (from 0)
Receiving objects: 100% (698/698), 161.42 KiB | 536.00 KiB/s, done.
Resolving deltas: 100% (625/625), done.
Note: switching to 'c0a1d6fe598aa020bfd94258233a8ad13df18dd6'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
Not all the Unicode characters are showing in Edge. For example, the Bluetooth character '' is showing fine in the terminal but like a box in Edge. I tried changing fonts in Edge itself but that didn't work at all.
Emojis are not showing in the browser. Apparently, it's fine in Chrome but not in Edge.
There is an error and the MsEdge is broken:
Unable to decompress /opt/microsoft/msedge/libvulkan.so.1 (Truncated zstd input)
The microsoft-edge-dev-bin is OK.
you should edit microsoft-edge-stable-flags.conf to apply electron flags.
cat /usr/bin/microsoft-edge-stable
#!/usr/bin/env sh
# Launches MS Edge with flags specified in $XDG_CONFIG_HOME/microsoft-edge-beta-flags.conf
# 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
exec /opt/microsoft/msedge/microsoft-edge $EDGE_USER_FLAGS "$@"
Cannot open with microsoft-edge-stable --ozone-platform=wayland
on KDE Plasma 6.1, how should I fix this?
The built-in screenshot tool does not work
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.