Issues with SGI_video_sync

Hello Guys,

since last release i've a lot of stability issue with SGI_video_sync :

[jeu. mars 19 10:21:14 2020] SGI_video_sync[14919]: segfault at e6 ip 0000560a13c90c4d sp 00007fa344dc3780 error 6 in skypeforlinux[560a108fc000+5425000]
[jeu. mars 19 10:21:14 2020] SGI_video_sync[14934]: segfault at e6 ip 0000561f08f5cc4d sp 00007f17ea6fa780 error 6 in skypeforlinux[561f05bc8000+5425000]
[jeu. mars 19 10:21:14 2020] SGI_video_sync[14950]: segfault at e6 ip 0000562530d78c4d sp 00007fa382ffb780 error 6 in skypeforlinux[56252d9e4000+5425000]
[jeu. mars 19 13:34:18 2020] SGI_video_sync[22653]: segfault at e6 ip 000055f73cd63bfd sp 00007f2adf236780 error 6 in bitwarden[55f739952000+5322000]
[jeu. mars 19 13:34:18 2020] SGI_video_sync[22664]: segfault at e6 ip 000055568aa49bfd sp 00007fdd7c5a2780 error 6 in bitwarden[555687638000+5322000]
[jeu. mars 19 13:34:18 2020] SGI_video_sync[22675]: segfault at e6 ip 000055b355264bfd sp 00007f772fd2c780 error 6 in bitwarden[55b351e53000+5322000]
[jeu. mars 19 13:50:58 2020] SGI_video_sync[23875]: segfault at e6 ip 0000564ee09e220d sp 00007f0b38580740 error 6 in Discord[564edd541000+53ad000]
[jeu. mars 19 13:50:59 2020] SGI_video_sync[23888]: segfault at e6 ip 00005650c191520d sp 00007f14be145740 error 6 in Discord[5650be474000+53ad000]
[jeu. mars 19 13:50:59 2020] SGI_video_sync[23928]: segfault at e6 ip 0000564653c5720d sp 00007fb8efb2a740 error 6 in Discord[5646507b6000+53ad000]
[ven. mars 20 10:30:35 2020] MellowPlayer[68421]: segfault at 0 ip 00007faddf853fdc sp 00007ffe379bc680 error 4 in libQt5Core.so.5.14.1[7faddf812000+2f9000]
[ven. mars 20 10:30:49 2020] SGI_video_sync[103265]: segfault at e6 ip 0000560afa0e2c4d sp 00007f030d450780 error 6 in skypeforlinux[560af6d4e000+5425000]

Here are few informations on my setup :

OS: Manjaro 19.0.2 Kyria
Kernel: x86_64 Linux 5.5.8-1-MANJARO
Packages: 1689
Shell: zsh 5.8
DE: KDE 5.67.0 / Plasma 5.18.3
WM: KWin
GTK Theme: Breath [GTK2], Adwaita [GTK3]
Icon Theme: breath
Disk: 117G / 220G (57%)
CPU: Intel Core i5-8600K @ 6x 4.3GHz [39.0°C]
GPU: GeForce GTX 1660 Ti
RAM: 4250MiB / 15821MiB

Is anyone having a similar issue ?

I've seen some post here and there speaking about GLIBC as a root cause :

https://forums.opera.com/topic/38293/solved-opera-66-0-3515-72-1-crashing-without-any-extension-or-new-installation/82

But it's not very clear, as this link seems related but doesn't speak about GLIBC :
https://bugs.archlinux.org/task/65643?project=5&string=sc

Thanks a lot !

edited title and added tags #kde, #nvidia

I have had blank screens from Skypeforlinux (stable) on different i5 intel chips. What worked for me was to open skype with the following command:

/usr/bin/skypeforlinux --disable-gpu

You might see if that helps your situation... and yes I know we are not seeing the exact same problem. :wink: But this may help.

Hey :slight_smile:

The root cause here is a change in glibc, as noted by the 2.31 release notes:

  • System call wrappers for time system calls now use the new time64
    system calls when available. On 32-bit targets, these wrappers
    attempt to call the new system calls first and fall back to the
    older 32-bit time system calls if they are not present. This may
    cause issues in environments that cannot handle unsupported system
    calls gracefully by returning -ENOSYS. Seccomp sandboxes are
    affected by this issue.

Since it's the individual applications like Discord, or any other electron/CEF based/like app that apply the seccomp filter, they will have to adjust their filters. Until that happens, the options are:

Or while highly technical and not user friendly, still an option:

  • Patch the individual binaries to allow clock_gettime64, similary to how the source code changed in upstream chromium for a previous issue github. com/chromium/chromium/commit/54407b422a9cbf775a68c1d57603c0ecac8ce0d7#diff-76dd4327967fba9837d93a944eeb1165

A similar change was commited to OpenSSH
github. com/openssh/openssh-portable/commit/ccd3b247d59d3bde16c3bef0ea888213fbd6da86#diff-5039537cc0e0b50db6f66642be1248fa

Forum kindly sponsored by