KDE Neon: 5.17
5.0.0-31-lowlatency
GT 630 (nvidia-435)
Multiscreen setup (2x 22", 1x 15")

after installing latest updates from oct 18, I have noticed a python3 zombie process

Code: Select all

ps ax -o s,pid,comm,ppid | grep '^Z'
Z  2742 pytho <defunct>  2684


Code: Select all

user     2802  0.0  0.0      0     0 ? Z    18:22   0:00 [python3] <defunct>


maybe an issue when multiple monitors are used due to the new monitor features?
for another system with a single monitor, the problem does not occur ...

If I try to kill the ppid Kwin crashes & shuts down in bash mode ...
so i have killed the ppid from there but after a reboot a new python3 zombie process is present
it seems to produce many xruns in my DAW with jack (cadence) too.

I split this in a separate post, as it is unrelated to the other one. Please do not hijack posts for issues.

some more details:
it seems there is a problem with the new screen manager ...
the system freezes when I save settings in kscreen manager
If I use the old ones (from kscreen folder) the system works but a zombie process is shown
would it be possible to re-install the previous displaymanager instead of the new one?

some more details:

Code: Select all

Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xcb.helper: Event Base:  89
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xcb.helper: Event Error:  147


Code: Select all

ct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: Connected output 637 to CRTC 634
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: Connected output 649 to CRTC 633
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: Connected output 659 to CRTC 635
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xcb.helper: Detected XRandR 1.5
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xcb.helper: Event Base:  89
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xcb.helper: Event Error:  147
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: XRandR::setConfig
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: Requested screen size is QSize(2880, 1668)
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: Needed CRTCs:  3
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: Actions to perform:
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: #011Change Screen Size: false
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: #011Disable outputs: false
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: #011Change outputs: false
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: #011Enable outputs: false
Oct 24 08:03:19 user org.kde.KScreen[19199]: kscreen.xrandr: XRandR::setConfig done!


Thank you guys for the quick supply of the bug fixes & for the updated live ISO which helped me a lot to determine the zombie problem!
Kscreen worked perfectly after the update but the zombie was still present ...
I found out that the reason was due to a extra (outdated) config file from Cadence which was integrated in the X11 folder.
after removing the file everything works fine without any zombies

/etc/X11/Xsession.d/61cadence-session-inject

Code: Select all

# Cadence Session Startup Injection
# Set plugin paths and start JACK (or not) according to user settings

INSTALL_PREFIX="/usr"

if [ -f $INSTALL_PREFIX/bin/cadence-session-start ]; then

export CADENCE_AUTO_STARTED="true"

export LADSPA_PATH="`$INSTALL_PREFIX/bin/cadence-session-start --printLADSPA_PATH`"
export DSSI_PATH="`$INSTALL_PREFIX/bin/cadence-session-start --printDSSI_PATH`"
export LV2_PATH="`$INSTALL_PREFIX/bin/cadence-session-start --printLV2_PATH`"
export VST_PATH="`$INSTALL_PREFIX/bin/cadence-session-start --printVST_PATH`"

STARTUP="$INSTALL_PREFIX/bin/cadence-session-start --system-start-by-x11-startup $STARTUP"

fi

unset INSTALL_PREFIX