Bug#940822: silx view crashes on invocation

2019-09-23 Thread Dmitry Shachnev



Am 23. September 2019 12:45:18 GMT+03:00 schrieb PICCA Frederic-Emmanuel 
:
> Is it possible to fix Buster ?

It is, but I am not the KCrash maintainer.

--
Dmitry Shachnev



Bug#940822: silx view crashes on invocation

2019-09-23 Thread PICCA Frederic-Emmanuel
Is it possible to fix Buster ?


Bug#940822: silx view crashes on invocation

2019-09-23 Thread Dmitry Shachnev
Control: reassign -1 libkf5crash5 5.54.0-1
Control: fixed -1 libkf5crash5/5.61.0-1

Hi all,

On Fri, Sep 20, 2019 at 07:11:39PM +, PICCA Frederic-Emmanuel wrote:
> Ok this simple script trigger the bug.
>
> from PyQt5.QtWidgets import QApplication, QLabel
> app = QApplication([])
>
> on KDE, but not on Gnome.
>
> BUT this
>
> app = QApplication(['a'])
>
> works.
>
> on KDE and Gnome.

I was able to reproduce this. The stack trace is attached.

This is a bug in KCrash, and it is already fixed in unstable. Cherry-picking
this upstream commit to testing version (5.54.0-1) fixes it too:

https://cgit.kde.org/kcrash.git/commit/?id=34b1a0aad1beaff9

--
Dmitry Shachnev
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x77c0a535 in __GI_abort () at abort.c:79
#2  0x77c61508 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x77d6c28d "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x77c67c1a in malloc_printerr (str=str@entry=0x77d6db68 
"malloc_consolidate(): invalid chunk size") at malloc.c:5341
#4  0x77c67f2a in malloc_consolidate (av=av@entry=0x77da3c40 
) at malloc.c:4471
#5  0x77c6aa58 in _int_malloc (av=av@entry=0x77da3c40 , 
bytes=bytes@entry=16409) at malloc.c:3695
#6  0x77c6c56a in __GI___libc_malloc (bytes=16409) at malloc.c:3057
#7  0x75fda4b2 in QArrayData::allocate (objectSize=objectSize@entry=1, 
alignment=alignment@entry=8, capacity=capacity@entry=16385, options=..., 
options@entry=...)
at tools/qarraydata.cpp:118
#8  0x75fdc400 in QTypedArrayData::allocate (options=..., 
capacity=16385) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:218
#9  QByteArray::QByteArray (this=0x7fffca40, size=16384) at 
tools/qbytearray.cpp:1711
#10 0x760444a8 in QRingChunk::QRingChunk (alloc=, 
this=0x7fffca40)
at 
../../include/QtCore/5.11.3/QtCore/private/../../../../../src/corelib/tools/qringbuffer_p.h:76
#11 QRingBuffer::reserve (this=0xcb5198, bytes=bytes@entry=16384) at 
tools/qringbuffer.cpp:152
#12 0x760ce8d5 in QIODevicePrivate::QRingBufferRef::reserve 
(this=0xcb2310, bytes=16384) at io/qiodevice_p.h:101
#13 QIODevicePrivate::read (this=0xcb2280, data=0x7fffcb2f "", 
maxSize=maxSize@entry=1, peeking=peeking@entry=false) at io/qiodevice.cpp:1128
#14 0x760cee48 in QIODevice::read (this=, 
data=, maxSize=maxSize@entry=1) at io/qiodevice.cpp:1052
#15 0x760d007a in QIODevice::getChar (this=, 
c=) at io/qiodevice.cpp:1840
#16 0x7282c242 in KCrash::CoreConfig::CoreConfig (this=0x7282f3b0 
<(anonymous namespace)::Q_QGS_s_coreConfig::innerFunction()::holder>, path=...) 
at ./src/coreconfig.cpp:40
#17 0x7282bcd7 in (anonymous 
namespace)::Q_QGS_s_coreConfig::Holder::Holder (this=0x7282f3b0 <(anonymous 
namespace)::Q_QGS_s_coreConfig::innerFunction()::holder>)
at ./src/coreconfig_p.h:30
#18 (anonymous namespace)::Q_QGS_s_coreConfig::innerFunction () at 
./src/kcrash.cpp:106
#19 (anonymous namespace)::Q_QGS_s_coreConfig::innerFunction () at 
./src/kcrash.cpp:106
#20 QGlobalStatic::operator() (this=)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobalstatic.h:135
#21 KCrash::initialize () at ./src/kcrash.cpp:144
#22 KCrash::initialize () at ./src/kcrash.cpp:124
#23 0x761848ed in qAddPreRoutine (p=0x7282bd90 
) at kernel/qcoreapplication.cpp:287
#24 0x77fe437a in call_init (l=, argc=argc@entry=1, 
argv=argv@entry=0x7fffe0c8, env=env@entry=0x7fffe0d8) at dl-init.c:72
#25 0x77fe4476 in call_init (env=0x7fffe0d8, argv=0x7fffe0c8, 
argc=1, l=) at dl-init.c:30
#26 _dl_init (main_map=main_map@entry=0xc929b0, argc=1, argv=0x7fffe0c8, 
env=0x7fffe0d8) at dl-init.c:119
#27 0x77fe82d3 in dl_open_worker (a=a@entry=0x7fffd030) at 
dl-open.c:517
#28 0x77d1cb2f in __GI__dl_catch_exception (exception=, 
operate=, args=) at dl-error-skeleton.c:196
#29 0x77fe7bba in _dl_open (file=0xc90e88 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so",
 mode=-2147479551, 
caller_dlopen=0x7617da2c , 
nsid=, argc=1, argv=0x7fffe0c8, env=0x7fffe0d8) at 
dl-open.c:599
#30 0x77f7e256 in dlopen_doit (a=a@entry=0x7fffd250) at dlopen.c:66
#31 0x77d1cb2f in __GI__dl_catch_exception 
(exception=exception@entry=0x7fffd1f0, operate=, 
args=) at dl-error-skeleton.c:196
#32 0x77d1cbbf in __GI__dl_catch_error (objname=0x8e8370, 
errstring=0x8e8378, mallocedp=0x8e8368, operate=, 
args=) at dl-error-skeleton.c:215
#33 0x77f7e975 in _dlerror_run (operate=operate@entry=0x77f7e200 
, args=args@entry=0x7fffd250) at dlerror.c:163
#34 0x77f7e2e6 in __dlopen (file=, mode=mode@entry=4097) 
at dlopen.c:87
#35 0x7617da2c in QLibraryPrivate::load_sys (this=0xc74ab0) at 
../../include/QtCore/../../src/corelib/tools/qarraydata.h:206
#36 0x761776b5 in 

Bug#940822: silx view crashes on invocation

2019-09-23 Thread Carlos Pascual
Thanks for the investigation!

I can only add that the version of  python3-qt5  available for stretch 
(5.7+dfsg-5) was not affected by this.



Bug#940822: silx view crashes on invocation

2019-09-20 Thread PICCA Frederic-Emmanuel
Ok this simple script trigger the bug.

from PyQt5.QtWidgets import QApplication, QLabel
app = QApplication([])

on KDE, but not on Gnome.

BUT this

app = QApplication(['a'])

works.

on KDE and Gnome.


Bug#940822: silx view crashes on invocation

2019-09-20 Thread PICCA Frederic-Emmanuel
Ok, I can reproduce this bug.

I switched to plasma and now I have

picca@cush:~$ silx view
malloc_consolidate(): invalid chunk size
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = python3.7 path = /usr/bin pid = 1876
KCrash: Arguments: 
Minuterie d'alerte

So this is something related to kde...


Bug#940822: silx view crashes on invocation

2019-09-20 Thread PICCA Frederic-Emmanuel
If I remove the config file, I have this error


picca@cush:~$ rm .config/silx/silx-view.ini 
picca@cush:~$ silx view
QSettings::value: Empty key passed
QSettings::value: Empty key passed
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = python3.7 path = /usr/bin pid = 1893
KCrash: Arguments: 
KCrash: Attempting to start .usr/lib/x86_64-linux-gnu/libexec/drkonqi from 
kdeinit
sock_file=/run/user/1001/kdeinit5__0
KCrash: Attempting to start .usr/lib/x86_64-linux-gnu/libexec/drkonqi directly
KCrash failed to exec(), errno = 2


Bug#940822: silx view crashes on invocation

2019-09-20 Thread PICCA Frederic-Emmanuel
Did you trye also to remove the .config files

picca@cush:~/.config/silx$ ls
silx-view.ini

If I remember correctly, I had a problem which was solved by removing this file.


Bug#940822: silx view crashes on invocation

2019-09-20 Thread PICCA Frederic-Emmanuel
Here you have the information about the core dump.

https://wiki.debian.org/HowToGetABacktrace



Bug#940822: silx view crashes on invocation

2019-09-20 Thread PICCA Frederic-Emmanuel
> Please find attached the output

It seems that KCrash is in our way.
Is it possible for you to run silx view from a gnome environment ?

are you using kde ?


Bug#940822: silx view crashes on invocation

2019-09-20 Thread Carlos Pascual
On Friday, September 20, 2019 11:21:29 AM CEST PICCA Frederic-Emmanuel wrote:
> gdb -ex r --args python3 -m silx.app.view.main

Please find attached the output

-- 
++
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpasc...@cells.es
 Phone: +34 93 592 4428
++:~$ gdb -ex r --args python3 -m silx.app.view.main
GNU gdb (Debian 8.2.1-2+b1) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from python3...(no debugging symbols found)...done.
Starting program: /usr/bin/python3 -m silx.app.view.main
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 10654]
[New Thread 0x7fffee6ba700 (LWP 10656)]
malloc_consolidate(): invalid chunk size

Thread 1 "python3" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x779b3535 in __GI_abort () at abort.c:79
#2  0x77a0a508 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x77b1528d "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x77a10c1a in malloc_printerr (str=str@entry=0x77b16b68 
"malloc_consolidate(): invalid chunk size") at malloc.c:5341
#4  0x77a10f2a in malloc_consolidate (av=av@entry=0x77b4cc40 
) at malloc.c:4471
#5  0x77a13a58 in _int_malloc (av=av@entry=0x77b4cc40 , 
bytes=bytes@entry=16409) at malloc.c:3695
#6  0x77a1556a in __GI___libc_malloc (bytes=16409) at malloc.c:3057
#7  0x76bcc552 in QArrayData::allocate(unsigned long, unsigned long, 
unsigned long, QFlags) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x76bce4a0 in QByteArray::QByteArray(int, Qt::Initialization) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x76c365b8 in QRingBuffer::reserve(long long) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x76cc09f5 in QIODevicePrivate::read(char*, long long, bool) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x76cc219a in QIODevice::getChar(char*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fffec0b0242 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5Crash.so.5
#13 0x7fffec0afcd7 in KCrash::initialize() () from 
/usr/lib/x86_64-linux-gnu/libKF5Crash.so.5
#14 0x76d76e7d in qAddPreRoutine(void (*)()) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x77fe437a in call_init (l=, argc=argc@entry=3, 
argv=argv@entry=0x7fffde48, env=env@entry=0xbf19e0) at dl-init.c:72
#16 0x77fe4476 in call_init (env=0xbf19e0, argv=0x7fffde48, argc=3, 
l=) at dl-init.c:30
#17 _dl_init (main_map=main_map@entry=0xf98aa0, argc=3, argv=0x7fffde48, 
env=0xbf19e0) at dl-init.c:119
#18 0x77fe82d3 in dl_open_worker (a=a@entry=0x7fffc750) at 
dl-open.c:517
#19 0x77ac5b2f in __GI__dl_catch_exception (exception=, 
operate=, args=) at dl-error-skeleton.c:196
#20 0x77fe7bba in _dl_open (file=0xf970d8 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so",
 mode=-2147479551, 
caller_dlopen=0x76d6ffac, nsid=, argc=3, 
argv=0x7fffde48, env=0xbf19e0) at dl-open.c:599
#21 0x77f38256 in dlopen_doit (a=a@entry=0x7fffc970) at dlopen.c:66
#22 0x77ac5b2f in __GI__dl_catch_exception 
(exception=exception@entry=0x7fffc910, operate=, 
args=) at dl-error-skeleton.c:196
#23 0x77ac5bbf in __GI__dl_catch_error (objname=0x8cca90, 
errstring=0x8cca98, mallocedp=0x8cca88, operate=, 
args=)
at dl-error-skeleton.c:215
#24 0x77f38975 in _dlerror_run (operate=operate@entry=0x77f38200 
, args=args@entry=0x7fffc970) at dlerror.c:163
#25 0x77f382e6 in __dlopen (file=, mode=) 
at dlopen.c:87
#26 0x76d6ffac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x76d69c25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 

Bug#940822: silx view crashes on invocation

2019-09-20 Thread PICCA Frederic-Emmanuel
gdb -ex r --args python3 -m silx.app.view.main


Bug#940822: silx view crashes on invocation

2019-09-20 Thread Carlos Pascual
On Friday, September 20, 2019 10:57:22 AM CEST PICCA Frederic-Emmanuel wrote:
> Could it be a problem with the OpenGL drivers on your computer ?

It could be something OpenGL-related, but I would not suspect the drivers, 
since it works well in the same machine when I use the pip version in a 
virtualnev.
I'll try to check some more.

> Do you have a backtrace from gdb available ?

No. I was not able to produce a core file...
The crash is handled by KCrash and even if I set `ulimit -c unlimited` it does 
not seem to produce a core  file. 
Any hint on how I can produce the backtrace?


-- 
++
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpasc...@cells.es
 Phone: +34 93 592 4428
++



Bug#940822: silx view crashes on invocation

2019-09-20 Thread PICCA Frederic-Emmanuel
Hello carlos,

I am using this on all our computers and I have no problem.

com-diffabs@diffabs6:~$ dpkg -l | grep silx
ii  python-silx   0.11.0+dfsg-1~bpo10+1 
   amd64Toolbox for X-Ray data analysis - Python2 
library
ii  python-silx-dbg   0.11.0+dfsg-1~bpo10+1 
   amd64Toolbox for X-Ray data analysis - Python2 debug
ii  python-silx-doc   0.11.0+dfsg-1~bpo10+1 
   all  Toolbox for X-Ray data analysis - Documentation
ii  python3-silx  0.11.0+dfsg-1~bpo10+1 
   amd64Toolbox for X-Ray data analysis - Python3
ii  python3-silx-dbg  0.11.0+dfsg-1~bpo10+1 
   amd64Toolbox for X-Ray data analysis - Python3 debug
ii  silx  0.11.0+dfsg-1~bpo10+1 
   all  Toolbox for X-Ray data analysis - Executables

Could it be a problem with the OpenGL drivers on your computer ?

Do you have a backtrace from gdb available ?


Bug#940822: silx view crashes on invocation

2019-09-20 Thread Carlos Pascual
Package: silx
Version: 0.9.0+dfsg-3
Severity: important

Dear Maintainer,

Running `silx view` or `silx test` produces a crash straight away with the 
following output:

```
~$ silx view
malloc_consolidate(): invalid chunk size
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = python3.7 path = /usr/bin pid = 10504
KCrash: Arguments: 
Alarm clock
```

The expected outcome is a silx view GUI appearing.

I also tested with version 0.11.0+dfsg-1~bpo10+1 from buster-backports,
with the same result.

In contrast, the version 0.11.0 from PyPI (installed in a py3 virtual env with 
pip) 
launches fine.


-- System Information:
Debian Release: 10.1
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages silx depends on:
ii  python33.7.3-1
ii  python3-numpy  1:1.16.2-1
ii  python3-silx   0.9.0+dfsg-3

silx recommends no packages.

silx suggests no packages.

-- no debconf information