Share via

Problem with opening microsoft-edge-dev with systemd-libs version 249

Anonymous
2021-07-15T05:44:59+00:00

As I'm trying to open microsoft-edge-dev (alomost all version of 91-93) on Arch Linux (with AUR), I met

fish: Job 1, 'microsoft-edge-dev' terminated by signal SIGSEGV (Address boundary error).

After using gdb to trace it, I found the problem was caused by

Thread 82 "msedge" received signal SIGSEGV, Segmentation fault.

Thread 82 (Thread 0x7fffc8a5e640 (LWP 16455) "msedge"):

#0 0x000055555aff8502 in ()

#1 0x00007fffc8a5d0c0 in ()

#2 0x00007fffc817c337 in () at /usr/lib/libnss_resolve.so.2

It indicates that this is a problem with systemd-libs (current version 249). After I downgrade it to version 248, the microsoft-edge-dev works normally.

I thought that this is a problem of edge and I came here for help. Sorry for choosing the wrong Operating System (Sine no Linux to choose).

Microsoft Edge | Open the browser | Android

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-07-15T15:31:56+00:00

    Hi,

    Thank you for writing to Microsoft Community Forums.

    I understand that you are unable to open Microsoft Edge Dev with systemd-libs version 249.

    However, we do have a dedicated forum for issues related to Microsoft Edge Dev, let me point you in the right direction. I would suggest you to post your query in Microsoft Tech Community, where you will find support professionals with expertise on Microsoft Edge Dev to assist you with the appropriate details.

    Regards,

    Nikhar Khare

    Microsoft Community – Moderator

    Was this answer helpful?

    0 comments