BUG: startkwayland leave processes after log out.
 

Hello,

I have a problems on current x64 with wayland. My wayland packages is:
After I click log out to exit in shell, wayland leave few processes that fire up load average to 3.40.

This problem does not exists of I run kde with startx. I also have a problem with wayland if power manager switch off monitor for more then 30 minutes after that no login screen appear for that if I will be away from kbd more the 30 minutes I leave from X. Forgot so say, leaving the processes up is not happened every time.

In fact, looks like (sometimes?) you have crashes on logout - see the drkonqi instances. So, you get zombies.

Would be interesting to known about your graphics stack - which model of graphics card? Which driver you use?

Because usually the crashes on Wayland/Plasma5 are produced by the graphics stack.

BTW, did you properly setup the PipeWire daemons? On Wayland/Plasma5 they aren't that "optional" as people thinks.

Sorry,

I did not setup anything. May be that is the problem, btw It's really crash something but I was thinking that is normal. How I can find a guide about PipeWire daemons, where are they
and what are they, I really don't know anything about these internal kde5 daemons ?

Here is my inxi:

You can take a look on this feature request:

https://www.linuxquestions.org/quest...ml#post6232769

Unless you want to use PipeWire also as audio server, you do not need the third XDG desktop file for pipewire-pulse.

Please note that that feature request uses a small daemon supervisor, described there:

https://www.linuxquestions.org/quest...ed-4175691414/

I use also myself (on multiple systems) the design proposed by @ZhaoLin1457 and works perfectly.

Probably it's the best way to tame the PipeWire daemons on a non-systemd distro like Slackware. You will find many details about the particularities of running those PipeWire daemons on the threads I suggested you.

BTW, the PipeWire itself is included already on Slackware-current, BUT just as dead weight (no startup setup), because it's a hard dependency of Plasma5.

However, the PipeWire is not something internal to Plasma5, but the very successor of PulseAudio, as an Audio/Video server.

Think that is something like the PulseVideo - which was its original name, BTW...

Firstly, you are kind to stop using QUOTEs ? Please use CODEs instead!

To make some sense on the previously quoted post of yours, I had to replace manually your QUOTEs with CODEs.

Anyway, at the first sight, your box should run fine the Wayland/Plasma5.

PS. After you setup properly the PipeWire daemons, you will notice also that the taskbar thumbnails work like on X11/Plasma5. ;)

I experience the same problem with a zombie kdeconnectd eating up 100% of one cpu core after a session logout.
The nice part is that even if i disable kdeconnectd from the tray settings, it gets started anyway.
By now my workaround is to just uninstall the package.
Same graphics stack as gildbg, amdgpu (ryzen 7 4700)

My apologies about quotes, I did not know the rules of the community. I forgot to mentioned I used X or wayland on init 3.


I make these changes but no effect, I see this error when I start the plasma, I also attach full log.

I need to kill manual process kdeinit5_shutdown to shutdown other processes.

I'm usually running plasma wayland through sddm. But sometime I do it like this:

Does not help, result is the same.

Why your desktop session is searching for org.freedesktop.locale1? Mine don't have org.freedesktop.locale1 and I believe Slackware does not have it by default.
Correction: Plasma desktop is indeed searching for org.freedesktop.locale1

The update from today does not fix the problem. Before writing, I had found a topic with a similar problem specifically for local1 again for Slackware and Alien had replied that it can be started already, but had not written that the problem was fixed.

BTW, the systemd-localed which the Wayland/Plasma5 wants to contact via DBUS path org.freedesktop.locale1 have a stand-alone implementation:

https://github.com/pierre-labastie/blocaled

It is made for LFS, but probably could be adapted and packaged for Slackware.

Honestly I am also interested by this "elocaled" because it looks like a missing piece of Wayland/Plasma5 on Slackware.

I try it, compiled both libdaemon from http://0pointer.de/lennart/projects/libdaemon/ and blocaled-0.3. With startplasma-wayland is not started. I got error Could not start D-Bus. Can you call qdbus? With startkwayland the error for locale1 is not appear, but on logout process still leaved and fire up cpu. I think something else is not work correct, because kdeinit5_shutdown and /usr/lib64/drkonqi is not loaded if I use startx.

Hello,

here us update. I can start now startplasma-wayland without libdaemon and blocaled library witch does not not want to start with error:

I use follow shell script.

The problem is after exit with Log out, leave the process /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session and need to be killed manual. Don't know how to resolve this issue. Also I see in debug log file that Driver and GPU class is unknown, not no idea from where this is taken.

About the GPU log, it's just an informative log. As long as your GPU is using the correct driver, you can check using lspci -k, no worries. My intel haswell gpu is also labeled as unknown in GPU class.
About the dbus-daemon session, I think you should modified the script like this:
Or just use That way your 'exec' command will replace the bash script process and controlling the whole process (including the session dbus) until it exits.

Thanks, that help but these processes again was leaved after exit. Оnce every 30 times happens as opposed to starting startkwayland each time. It's seems they crash for something and then is happened. I will try to look in forum if have kde5 group to ask them how to debug that problem.