pyside6-designer crashes desktop with SIGSEGV

urlkrueger

Running pyside6-designer in a virtual environment when I select create a new MainWindow the window appears with "Type Here" in a tab at the top left. If I click on the tab, type some text, hit enter key a drop down appears containing "Type Here" and "Add Separator". Also a new "Type Here" tab appears in the menu bar. If I then click anywhere within the MainWindow my desktop consistently crashes due to SIGSEGV. This happens on both a Dell laptop and a iMac running Linux.

This appears to be only related to the tabs as I can drag in other widgets and change the text in them without any problems.

Any comments or suggestions?

Ubuntu 22.04
Python 3.10.6
Qt Designer 6.4.1

friedemannkleint

Then I would recommend switching from Wayland to X11. Apparently Wayland and Qt support for it still has many restrictions.

friedemannkleint

What language are you using? Is there some kind of Input Method Support active for it? Could you try to obtain a debug stack trace?

urlkrueger

By crashing I mean my screen goes blank and after a while I am presented with the Ubuntu logon screen.

The crash dump tells me:
ExecutablePath: /usr/bin/gnome-shell
ProblemType: Crash
Title: gnome-shell crashed with SIGSEGV in __pthread_kill_implementation()
ProcEnviron: LANG=en_US.UTF-8, PATH=(custom,no user), SHELL=/bin/bash

The top of the stack trace lists pthread_kill.c then I see libc, libmutter, libwayland and such ending with libc-start.c.

My interpretation of this is that memory somewhere (gnome-shell?) is somehow being corrupted by pyside6-designer since that is the only program I use that causes this crash. Since my C++ skills are limited I am not sure how much further I can go into diagnosing this.

urlkrueger

Using a third laptop (Samsung) I formatted the disk and then installed:

a fresh Ubuntu 22.04 Desktop edition and all updates,,
Qt Open Source edition 6.4.2 for desktop using online installer from qt.io ,
venv and
PySide6 using pip.

When running pyside6-designer as described in first post of this thread I get the same crash as with the other two computers.

This is totally reproducible and consistent in that I have never had it not fail on three different brands of hardware. Now the question is what is causing this, Ubuntu or Qt.

friedemannkleint

Then I would recommend switching from Wayland to X11. Apparently Wayland and Qt support for it still has many restrictions.

urlkrueger

@friedemannkleint You were right, switching to X11 cures the problem. Thanks for the help.

For completeness sake to make the switch I followed instruction in this thread
Ubuntu switch Wayland to X11