-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest version of Skype won't run #70
Comments
Same for me. Running from command line with
No skype process running afterwards |
As a quick workaround I downgraded to the previously working version with:
|
|
There's some previous discussion of the difficulty of flatpaking the Chrome sandbox helper here: flathub/flathub#566 |
See also flatpak/flatpak#3044. |
Is this discussion about https://forum.manjaro.org/t/skypeforlinux-doesnt-work-anymore-after-updating/99853 It seems that the following command helped in some cases for Linux kernel before 5.1.8: $ sudo sysctl kernel.unprivileged_userns_clone=1 |
@alexeymuranov I am running Arch with current kernel 5.2.11, so unprivileged_userns_clone is already enabled. Changing this value doesn't make a difference. |
For me, 8.51.0.72 simply crashes:
|
I can also confirm this for Fedora 30 Silverblue. After running this downgrade I was able to start Skye again.
|
Linking here for better visibility. https://answers.microsoft.com/en-us/skype/forum/sk_access-skype_linux/disable-electronchrome-sandboxing-on-linux/0260e3b1-5fa0-49ba-9854-dde1c040e249 If skype would allow passing |
As a temporary workaround for no upstream-supported way for Electron to request nested sandboxes be created by Flatpak, use a version of https://github.com/flathub/com.unity.UnityHub/blob/master/patch-resources.py to patch the app resource file and remove the JavaScript code that makes Skype exit if you pass --no-sandbox. After doing this, we can add --no-sandbox to our launch script and run newer versions of Skype inside a Flatpak sandbox. Works around #70 for now.
As a temporary workaround for no upstream-supported way for Electron to request nested sandboxes be created by Flatpak, use a version of https://github.com/flathub/com.unity.UnityHub/blob/master/patch-resources.py to patch the app resource file and remove the JavaScript code that makes Skype exit if you pass --no-sandbox. After doing this, we can add --no-sandbox to our launch script and run newer versions of Skype inside a Flatpak sandbox. Works around #70 for now.
As a temporary workaround for no upstream-supported way for Electron to request nested sandboxes be created by Flatpak, use a version of https://github.com/flathub/com.unity.UnityHub/blob/master/patch-resources.py to patch the app resource file and remove the JavaScript code that makes Skype exit if you pass --no-sandbox. After doing this, we can add --no-sandbox to our launch script and run newer versions of Skype inside a Flatpak sandbox. Works around #70 for now.
It's broken again:
|
How To
Nothing really special. I updated Skype and since then it won't start. Running it from the terminal gives no logging. Preforming a Flatpak repair does nothing as well.
System
Client info
The text was updated successfully, but these errors were encountered: