http://bugzilla.opensuse.org/show_bug.cgi?id=1191012
http://bugzilla.opensuse.org/show_bug.cgi?id=1191012#c4
--- Comment #4 from Stefan Dirsch ---
There is a discussion on opensuse-factory mailing list with subject "new glibc
from Tumbleweed snapshot 20210920 affects electron based apps" (original
subject: "New Tumbleweed snapshot 20210920 released!")
-----------------------------------------------------
today, after i installed recent updates, including the updates from snapshot
20210920, vscode did not work any more.
after some searching, i found
https://github.com/microsoft/vscode/issues/133804
so i worked around the problem with||||||||the "--no-sandbox" commandline
parameter.
then i noticed also other applications do not work any more.
i noticed, that all non-working applications are chromium/electron based
applications like slack, hamsket, vivaldi, discord, msteams.
all of them don't work any more, unless you use the "--no-sandbox" commandline
parameter.
after some more searching i found:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1944468
the reason for all this seems to be the new glibc, which was coming with
snapshot 20210920
is this already known?
in the above ubuntu issue a new/patched glibc is mentioned.
does such fix also exist for opensuse?
-----------------------------------------------------
The patch is for Electron to behave correct, not for glibc.
Some people hacked around it by disablling the new clone3() syscall,
but this is no solution. It's like buying a Porsche and then put a
very slow engine into it.
If you speak about openSUSE packages like docker: yes, we fixed the
applications we were aware of. But we cannot fix e.g. third party
binaries and openQA does not cover all applications
-----------------------------------------------------
this means, all Electron based applications need to be fixed.
and as long as such an application has not been fixed, the "--no-sandbox"
workaround has to be used with this application.
-----------------------------------------------------
--
You are receiving this mail because:
You are on the CC list for the bug.