Description of problem: When debugging certain app I got Wayland crashes, then reproduced it on Xorg as well. Simplest reproduction I got to is to create a file that executes "os.kill(0, 15)" and run/debug it from eclipse. Version-Release number of selected component (if applicable): eclipse-equinox-osgi-4.14-5.fc32.x86_64 eclipse-jgit-5.6.0-2.fc32.noarch eclipse-jdt-4.14-5.fc32.noarch eclipse-pydev-7.7.0-1.fc32.x86_64 eclipse-egit-5.6.0-2.fc32.noarch eclipse-swt-4.14-5.fc32.x86_64 eclipse-ecf-core-3.14.6-4.fc32.noarch eclipse-platform-4.14-5.fc32.x86_64 eclipse-emf-core-2.20.0-5.fc32.noarch libwayland-egl-1.18.0-1.fc32.i686 libwayland-server-1.18.0-1.fc32.x86_64 xorg-x11-server-Xwayland-1.20.8-1.fc32.x86_64 qt5-qtwayland-5.14.2-4.fc32.x86_64 gnome-session-wayland-session-3.36.0-2.fc32.x86_64 xorg-x11-server-Xorg-1.20.8-1.fc32.x86_64 How reproducible: Always Steps to Reproduce: 1. create a python file with "import os; os.kill(0, 15)" 2. select "Run As"->"Python Run" Actual results: Eclipse crashes and Wayland/Xorg as well (Xorg restarts, Wayland stays dead) Expected results: Ideally Eclipse should stay unaffected but at least it'd be nice if Wayland/Xorg survived. Additional info: It also works when I start debugging any script and manually execute the "os.kill(0, 15)" from the pydev console. On the other hand everything works well when the process is started elsewhere and pydev is only accessed via "import pydevd; pydevd.settrace("127.0.0.1", True, True)" directly from the script (execution only kills the python process, Eclipse as well as Wayland/Xorg survives)
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This issue is still on, by installing pydev on Fedora it's simple to crash Wayland/Xorg session. Can someone from Wayland/Xorg take a look? The reproducer is very simple and eclipse-pydev can still be downloaded from the eclipse store.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days