Your message dated Mon, 23 Dec 2019 10:16:37 +0100 with message-id <75ad7ad5-12fa-df53-a4bf-be2a26fc949a@freexian.com> and subject line Re: Update has caused the Debian Bug report #940565, regarding PySide2 segfaults with Python3. Message: "SystemError: could not initialize part 1" (shiboken) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 940565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940565 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: "submit@bugs.debian.org" <submit@bugs.debian.org>
- Subject: PySide2 segfaults with Python3. Message: "SystemError: could not initialize part 1" (shiboken)
- From: Mark Weyer <Mark.Weyer@Hahn-Schickard.de>
- Date: Tue, 17 Sep 2019 11:57:20 +0000
- Message-id: <8c85c6dd10d940259846f7325f2c62ea@iit-es01.hsg.privat>
Package: pyside2 Version: 5.11.2-3 Severity: grave The file test.py contains a single line (without the "> " quotation): > import PySide2.QtCore as core Running > python3 test.py results in a segfault with output: > SystemError: could not initialize part 1 FWIW, I could trace that message to sources/shiboken2/libshiboken/signature.cpp in the pyside2 orig.tar Running the script with python instead of python3 gives no error. The same behaviour occurs with other Pyside2 modules instead of QtCore. > uname -a > Linux debian 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2 (2019-08-28) x86_64 GNU/Linux > ls -l /lib/*/libc.so.6 > lrwxrwxrwx 1 root root 12 Mai 1 19:24 /lib/x86_64-linux-gnu/libc.so.6 -> libc-2.28.so The machine in question runs in a VirtualBox VM. Best regards, Mark Weyer
--- End Message ---
--- Begin Message ---
- To: 940565-done@bugs.debian.org
- Subject: Re: Update
- From: Sophie Brun <sophie@freexian.com>
- Date: Mon, 23 Dec 2019 10:16:37 +0100
- Message-id: <75ad7ad5-12fa-df53-a4bf-be2a26fc949a@freexian.com>
- In-reply-to: <c64b410b-4d4e-1f47-4f3b-6ac527a76995@freexian.com>
- References: <46567cbe708e4ae3a294d41cd4f3414b@iit-es01.hsg.privat> <46567cbe708e4ae3a294d41cd4f3414b@iit-es01.hsg.privat> <c64b410b-4d4e-1f47-4f3b-6ac527a76995@freexian.com> <c64b410b-4d4e-1f47-4f3b-6ac527a76995@freexian.com>
As there is no more segfault and it's a Python3 error, not a pyside 2 I think I can close this bug.
Sophie
--- End Message ---