Bug#887078: libc6: Amarok get SIGSEGV at start
Package: libc6
Version: 2.26.9000+20180108.401311cf-0experimental0
Severity: important
Dear Maintainer,
Upgrading libc6 to Experimental makes Amarok no longer start. No other programs I have tried are affected.
It gets SIGSEGV with stacks that are pretty hard to understand in gdb:
$ gdb amarok
(gdb) set args --nofork
(gdb) r
Starting program: /usr/bin/amarok --nofork
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Program received signal SIGSEGV, Segmentation fault.
0x00007fffffffdc60 in ?? ()
(gdb) where
#0 0x00007fffffffdc60 in ()
#1 0x0000000000000000 in ()
Downgrading libc6 to Unstable makes Amarok work again.
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Reply to: