Package Details: microsoft-edge-beta-bin 132.0.2957.11-1

Git Clone URL: https://aur.archlinux.org/microsoft-edge-beta-bin.git (read-only, click to copy)
Package Base: microsoft-edge-beta-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
Licenses: custom
Conflicts: edge, edge-beta, edge-beta-bin, microsoft-edge-beta
Provides: edge-beta, microsoft-edge-beta
Submitter: bittin
Maintainer: bittin (EsauPR, kode54)
Last Packager: kode54
Votes: 28
Popularity: 0.031017
First Submitted: 2021-05-01 07:39 (UTC)
Last Updated: 2024-11-26 03:50 (UTC)

Dependencies (15)

Required by (1)

Sources (3)

Latest Comments

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

Epicccal commented on 2021-07-20 04:25 (UTC)

Hello, I think I found a solution.

this is a problem with systemd-libs (current version 249-3). After I downgrade it to version 248-5, the msedge-beta works normally.

execute sudo downgrade systemd-libs and choose systemd-libs-248

There are specific instructions in this article: https://techcommunity.microsoft.com/t5/discussions/linux-edge-beta-problem-with-systemd-249/m-p/2550466

zilvervos commented on 2021-07-19 10:00 (UTC) (edited on 2021-07-19 10:05 (UTC) by zilvervos)

@Vedun: commenting out the hosts line in nsswitch.conf did the trick for me. I don't like systemd's expansionist behaviour. Why should it be involved in DNS resolving? Why are we, Arch users, bound to use systemd and all that comes with it?

Makes me seriously consider moving over to Artix (a systemd-free Arch fork that gets pretty positive reviews).

gebau00a commented on 2021-07-17 02:56 (UTC)

@angelettif: I can confirm, disabling systemd-resolved solves the issue for me as well

angelettif commented on 2021-07-16 16:56 (UTC) (edited on 2021-07-16 17:52 (UTC) by angelettif)

@Vedun Thank you removing /etc/nsswitch.conf, solved the problem.

My default host NSS switch conf is

hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns

Could be so wrong that make edge segfault :D?

// It seems this resolve [!UNAVAIL=return] trigger the problem Could be another systemd bug?, in this case systemd-resolved ? // To me... yes.! sudo systemctl disable systemd-resolved sudo systemctl stop systemd-resolved

disable systemd-resolved and configure /etc/resolv.conf Fixed.

gebau00a commented on 2021-07-16 15:58 (UTC) (edited on 2021-07-16 15:58 (UTC) by gebau00a)

Resetting the nsswitch.conf did not work for me, the reset file is the same as the old one. I also have the hostname for both 127.0.0.1 and ::1

But I can confirm, it's related to SmartScreenDnsResolver not being able to connect to an internet address.

Posting the question also in the Microsoft Tech Forum (https://techcommunity.microsoft.com/t5/discussions/linux-edge-beta-problem-with-systemd-249/m-p/2550466), it gave a link to libnss_resolve.so.2

Checking the arch manuals, (https://man.archlinux.org/man/core/systemd/libnss_resolve.so.2.8.en), this file belongs to the systemd-resolved.service But even resetting nsswitch.conf according to the manual given there does not solve the error for me.

I only learned in this process, the only package to downgrade is actually systemd-libs

Vedun commented on 2021-07-16 15:06 (UTC) (edited on 2021-07-16 16:52 (UTC) by Vedun)

@angelettif Finally I found the problem! The whole problem is in the NSS, or rather in its settings. Delete the configuration file (/etc/nsswitch.conf) and then the settings NSS will be set to default.

Enjoy!

p.s. NSS - "Name Service Switch"

p.p.s. ... or you can just comment out the hosts line in the /etc/nsswitch.conf file, by default this line should be:

hosts: dns [!UNAVAIL=return] files

angelettif commented on 2021-07-16 14:03 (UTC)

/etc/hosts fix doesn't work for me

angelettif commented on 2021-07-16 13:18 (UTC)

what were on your hosts? I got my hostname and doesnt work. How can fail with a segfault just because some word is missing on a /etc/hosts

mister commented on 2021-07-16 12:23 (UTC)

As armadillo said, adding a loopback entry to /etc/hosts with your hostname seems to fix the issue. It did for me too

armadillo commented on 2021-07-16 08:36 (UTC) (edited on 2021-07-16 08:50 (UTC) by armadillo)

As per the comment posted for microsoft-edge-dev-bin, adding an entry to /etc/hosts for my own hostname fixes the issue for me. Either 127.0.1.1 (loopback) or the actual network IP seems OK.

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