Bug#924402: spyder3 Segmentation fault just after console comes up
js jb
em2jacks at yahoo.com
Tue Mar 12 15:30:50 GMT 2019
Package: spyder3
Version: 3.3.3+dfsg1-1
Severity: important
Dear Maintainer,
=======================================================================================================
After upgrade of spyder 3 to latest version in testing (3.3.3+dfsg1-1), spyder3 brings up console and
a few seconds later fails with a segmentation fault. This happens consistently every single time it is run.
Here is the output:
=> spyder3
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Segmentation fault
Here are the last few lines of strace before the crash:
stat64("/usr/lib/i386-linux-gnu/gstreamer-1.0/libgstdecklink.so", {st_mode=S_IFREG|0644, st_size=141740, ...}) = 0
stat64("/usr/lib/i386-linux-gnu/gstreamer-1.0/libgstfbdevsink.so", {st_mode=S_IFREG|0644, st_size=13924, ...}) = 0
stat64("/usr/lib/i386-linux-gnu/gstreamer-1.0/libgstfluidsynthmidi.so", {st_mode=S_IFREG|0644, st_size=30532, ...}) = 0
stat64("/usr/lib/i386-linux-gnu/gstreamer-1.0/libgstbz2.so", {st_mode=S_IFREG|0644, st_size=26468, ...}) = 0
getdents64(43, /* 0 entries */, 32768) = 0
close(43) = 0
futex(0xa8eb2a08, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0xa8eb2a08, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0xa8eb2a08, FUTEX_WAKE_PRIVATE, 2147483647) = 0
mprotect(0x9a4a0000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
madvise(0x9a4a0000, 4096, MADV_WILLNEED) = 0
madvise(0x99fe3000, 12288, MADV_NORMAL) = 0
mprotect(0x9a49e000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
madvise(0x9a49e000, 4096, MADV_WILLNEED) = 0
madvise(0xa0d72000, 4096, MADV_NORMAL) = 0
madvise(0x99fe0000, 12288, MADV_NORMAL) = 0
madvise(0xa0d71000, 4096, MADV_NORMAL) = 0
madvise(0xa0d70000, 4096, MADV_NORMAL) = 0
madvise(0xa0d6f000, 4096, MADV_NORMAL) = 0
madvise(0x99bb0000, 16384, MADV_NORMAL) = 0
madvise(0x993ec000, 8192, MADV_NORMAL) = 0
madvise(0x99bac000, 16384, MADV_NORMAL) = 0
madvise(0xa0d6e000, 4096, MADV_NORMAL) = 0
madvise(0x99ba8000, 16384, MADV_NORMAL) = 0
madvise(0xa0d6d000, 4096, MADV_NORMAL) = 0
madvise(0xa0d6c000, 4096, MADV_NORMAL) = 0
madvise(0xa0d6b000, 4096, MADV_NORMAL) = 0
madvise(0xa0d6a000, 4096, MADV_NORMAL) = 0
madvise(0xa0d69000, 4096, MADV_NORMAL) = 0
madvise(0x997e8000, 32768, MADV_NORMAL) = 0
mprotect(0x9a49f000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
madvise(0x9a49f000, 4096, MADV_WILLNEED) = 0
madvise(0xa0d68000, 4096, MADV_NORMAL) = 0
madvise(0xa0d67000, 4096, MADV_NORMAL) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x1c} ---
+++ killed by SIGSEGV +++
Segmentation fault
This situation has started happening with the previous version of spyder3, which before worked fine,
so may be related to a change in X (eg making Xorg suid) which affected spyder3 in a way that did not
for any other programs.
Note that spyder (version 3.3.3+dfsg1-1) works fine in the same environment, even when using python3
as the interpreter. This is the current work-around for this problem with spyder3.
=======================================================================================================
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 4.17.0-3-686-pae (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), LANGUAGE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages spyder3 depends on:
ii python3-spyder 3.3.3+dfsg1-1
ii python3.7 3.7.2-1
spyder3 recommends no packages.
spyder3 suggests no packages.
Versions of packages python3-spyder depends on:
ii libjs-jquery 3.2.1-1
ii libjs-mathjax 2.7.4+dfsg-1
ii pylint3 2.2.2-1
ii python3 3.7.2-1
ii python3-chardet 3.0.4-1
ii python3-cloudpickle 0.8.0-1
ii python3-jedi 0.13.2-1
ii python3-keyring 17.1.1-1
ii python3-nbconvert 5.4-2
ii python3-numpydoc 0.7.0-1
ii python3-pickleshare 0.7.5-1
ii python3-psutil 5.5.1-1
ii python3-pycodestyle 2.4.0-2
ii python3-pyflakes 2.0.0-1
ii python3-pygments 2.3.1+dfsg-1
ii python3-qtawesome 0.4.4+ds1-1
ii python3-qtconsole 4.3.1-1
ii python3-qtpy 1.3.1-1
ii python3-rope 0.10.5-3
ii python3-sphinx 1.8.4-1
ii python3-spyder-kernels 1.0.1+really0.2.4-1
ii python3-zmq 17.1.2-1
ii spyder-common 3.3.3+dfsg1-1
Versions of packages python3-spyder suggests:
ii cython3 0.29.2-2
ii python3-matplotlib 3.0.2-2
ii python3-numpy 1:1.16.1-1
ii python3-pandas 0.23.3-1
ii python3-pil 5.4.1-1
ii python3-scipy 1.1.0-2
ii python3-sympy 1.3-1
Versions of packages python3-pyqt5 depends on:
ii libc6 2.28-2
ii libgcc1 1:8.3.0-2
ii libpython3.7 3.7.2-1
ii libqt5core5a [qtbase-abi-5-11-3] 5.11.3+dfsg-2
ii libqt5dbus5 5.11.3+dfsg-2
ii libqt5designer5 5.11.3-2
ii libqt5gui5 5.11.3+dfsg-2
ii libqt5help5 5.11.3-2
ii libqt5network5 5.11.3+dfsg-2
ii libqt5printsupport5 5.11.3+dfsg-2
ii libqt5test5 5.11.3+dfsg-2
ii libqt5widgets5 5.11.3+dfsg-2
ii libqt5xml5 5.11.3+dfsg-2
ii libstdc++6 8.3.0-2
ii python3 3.7.2-1
ii python3-sip [sip-py3api-12.5] 4.19.14+dfsg-1
Versions of packages python3-pyqt5 suggests:
pn python3-pyqt5-dbg <none>
-- no debconf information
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20190312/2cd15327/attachment-0001.html>
More information about the debian-science-maintainers
mailing list