Bug#893320: libc6: libc-2.27.so causes segfaults in multiple programs

[Svein Engelsgjerd <waxhead@dirtcellar.net>]

Package: libc6
Version: 2.27
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I upgraded debain 'testing' today.
The upgrade included libc and systemd as far as I remember.
After the upgrade Multiple programs and libraries segfaults for some reason.
I believe this is caused by libc-2.27

Examples:
[ 1996.980004] show_signal_msg: 16 callbacks suppressed
[ 1996.980007] gmain[1815]: segfault at ffffffffffffffff ip 00007f8240d2af3d sp 00007f8237924690 error 5 in libglib-2.0.so.0.5400.3[7f8240cc3000+111000]
[ 1996.984537] traps: gdbus[1641] general protection ip:7f1bb2b425f9 sp:7f1babffed08 error:0 in libc-2.27.so[7f1bb2a56000+1b1000]
[ 1996.986582] pasystray[1840]: segfault at 8 ip 00007f79a5366caa sp 00007ffc9dc41520 error 4 in libglib-2.0.so.0.5400.3[7f79a531c000+111000]
[ 1997.005432] panel-29-xfce4-[1747]: segfault at 7f818f97331f ip 00007f730bbbf064 sp 00007ffef88b8e40 error 4 in libglib-2.0.so.0.5400.3[7f730bb77000+111000]
[ 1997.008670] smart-notifier[1844]: segfault at ffffffffffffffff ip 00007f1e874ad9f3 sp 00007ffd65740e50 error 5 in libglib-2.0.so.0.5400.3[7f1e87463000+111000]
[ 1997.015035] traps: gdbus[1865] general protection ip:7fc65581e5f9 sp:7fc643ffeac8 error:0 in libc-2.27.so[7fc655732000+1b1000]
[ 2000.019533] perf: interrupt took too long (3930 > 3927), lowering kernel.perf_event_max_sample_rate to 50750
[ 2020.774800] qpdfview[2098]: segfault at 4 ip 00007f32ffd31bb7 sp 00007fff3891bd70 error 6 in libQt5Widgets.so.5.9.2[7f32ff8f3000+614000]
[ 3049.114858] xfce4-panel[1709]: segfault at 0 ip 00007ff3c6a7a9f3 sp 00007ffc97eefea0 error 4 in libglib-2.0.so.0.5400.3[7ff3c6a30000+111000]
[ 3049.170745] traps: gdbus[1936] general protection ip:7f85b31225f9 sp:7f85abffed08 error:0 in libc-2.27.so[7f85b3036000+1b1000]
[ 3049.175240] traps: gdbus[1920] general protection ip:7ffae2d1e5f9 sp:7ffadbffed08 error:0 in libc-2.27.so[7ffae2c32000+1b1000]

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I ran memtest86+ to verify that my hardware (memory) is not the cause.

   * What was the outcome of this action?
System was fine, programs continue to crash

   * What outcome did you expect instead?
I did not expect a upgrade to cause lots of program segfaults "all over" the system.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled