SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
After I click log out to exit in shell, wayland leave few processes that fire up load average to 3.40.
Quote:
user 1520 0.0 0.0 159604 4740 ? Sl 18:45 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
user 1523 0.0 0.0 7528 4300 tty1 Ss 18:45 0:00 -bash
user 1650 0.0 0.0 143492 19984 ? Sl 18:45 0:00 /usr/lib64/startplasma-waylandsession
user 1756 57.2 0.1 388452 34144 ? Sl 18:45 0:49 /usr/lib64/kactivitymanagerd
user 1790 107 0.1 276748 49776 ? Sl 18:45 1:32 /usr/lib64/kdeconnectd
user 1805 56.1 0.2 387124 66260 ? Sl 18:45 0:48 /usr/bin/korgac
user 2188 0.0 0.0 133740 13332 ? Sl 18:46 0:00 /usr/bin/kdeinit5_shutdown
user 2190 0.0 0.0 90300 27364 ? S 18:46 0:00 /usr/lib64/drkonqi -platform wayland --appname kdeconnectd --apppath /usr/lib64 --signal 6 --pid 1790 --appversion 20.12.3 --programname KDE Connect Daemon --bugaddr
ess submit@bugs.kde.org --startupid 0
user 2191 0.0 0.0 90300 27196 ? S 18:46 0:00 /usr/lib64/drkonqi -platform wayland --appname korgac --apppath /usr/bin --signal 6 --pid 1805 --appversion 5.16.3 (20.12.3) --programname KOrganizer Reminder Daemon
--bugaddress submit@bugs.kde.org --startupid 0
user 2192 0.0 0.0 90300 27388 ? S 18:46 0:00 /usr/lib64/drkonqi -platform wayland --appname kactivitymanagerd --apppath /usr/lib64 --signal 6 --pid 1756 --startupid 0
user 2193 0.0 0.0 69100 14476 ? S 18:46 0:00 /usr/bin/kdeinit5 --suicide
user 2194 0.0 0.0 69100 6492 ? Ss 18:46 0:00 /usr/bin/kdeinit5 --suicide
user 2195 0.0 0.0 89144 27580 ? S 18:46 0:00 /usr/lib64/kf5/klauncher --fd=8
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.
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.
Code:
user 1520 0.0 0.0 159604 4740 ? Sl 18:45 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
user 1523 0.0 0.0 7528 4300 tty1 Ss 18:45 0:00 -bash
user 1650 0.0 0.0 143492 19984 ? Sl 18:45 0:00 /usr/lib64/startplasma-waylandsession
user 1756 57.2 0.1 388452 34144 ? Sl 18:45 0:49 /usr/lib64/kactivitymanagerd
user 1790 107 0.1 276748 49776 ? Sl 18:45 1:32 /usr/lib64/kdeconnectd
user 1805 56.1 0.2 387124 66260 ? Sl 18:45 0:48 /usr/bin/korgac
user 2188 0.0 0.0 133740 13332 ? Sl 18:46 0:00 /usr/bin/kdeinit5_shutdown
user 2190 0.0 0.0 90300 27364 ? S 18:46 0:00 /usr/lib64/drkonqi -platform wayland --appname kdeconnectd --apppath /usr/lib64 --signal 6 --pid 1790 --appversion 20.12.3 --programname KDE Connect Daemon --bugaddr
ess submit@bugs.kde.org --startupid 0
user 2191 0.0 0.0 90300 27196 ? S 18:46 0:00 /usr/lib64/drkonqi -platform wayland --appname korgac --apppath /usr/bin --signal 6 --pid 1805 --appversion 5.16.3 (20.12.3) --programname KOrganizer Reminder Daemon
--bugaddress submit@bugs.kde.org --startupid 0
user 2192 0.0 0.0 90300 27388 ? S 18:46 0:00 /usr/lib64/drkonqi -platform wayland --appname kactivitymanagerd --apppath /usr/lib64 --signal 6 --pid 1756 --startupid 0
user 2193 0.0 0.0 69100 14476 ? S 18:46 0:00 /usr/bin/kdeinit5 --suicide
user 2194 0.0 0.0 69100 6492 ? Ss 18:46 0:00 /usr/bin/kdeinit5 --suicide
user 2195 0.0 0.0 89144 27580 ? S 18:46 0:00 /usr/lib64/kf5/klauncher --fd=8
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.
Last edited by LuckyCyborg; 04-05-2021 at 11:56 AM.
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 ?
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 ?
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...
Quote:
Originally Posted by gildbg
Here is my inxi:
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.
Last edited by LuckyCyborg; 04-05-2021 at 03:10 PM.
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.
Code:
not a reply org.freedesktop.locale1 QDBusMessage(type=Error, service="org.freedesktop.DBus", error name="org.freedesktop.DBus.Error.ServiceUnknown", error message="The name org.freedesktop.locale1 was not provided by any .service
files", signature="s", contents=("The name org.freedesktop.locale1 was not provided by any .service files") )
I need to kill manual process kdeinit5_shutdown to shutdown other processes.
Code:
/usr/bin/xprop: unable to open display ':0'
"xprop" ("-root", "-remove", "KDE_FULL_SESSION") exited with code 1
/usr/bin/xprop: unable to open display ':0'
"xprop" ("-root", "-remove", "KDE_SESSION_VERSION") exited with code 1
startplasma-waylandsession: Starting up...startplasma-waylandsession: Shutting down...
startplasma-waylandsession: Done.
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
kf.init.klauncher: No D-Bus session-bus found. Check if you have started the D-Bus server.
kdeinit5: Communication error with launcher. Exiting!
qt.qpa.wayland: Failed to initialize EGL display 3001
qt.qpa.wayland: Failed to initialize EGL display 3001
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = drkonqi path = /usr/lib64 pid = 2164
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = drkonqi path = /usr/lib64 pid = 2163
KCrash: Arguments: /usr/lib64/drkonqi KCrash: Arguments: /usr/lib64/drkonqi --appname kdeconnectd --appname korgac --apppath /usr/lib64 --apppath /usr/bin --signal 6 --signal 6 --pid 1828 --pid 2059 --appversion 20.12.3 --appversi
on 5.16.3 (20.12.3) --programname --programname KDE Connect Daemon --bugaddress KOrganizer Reminder Daemon --bugaddress submit@bugs.kde.org submit@bugs.kde.org --startupid --startupid 0
0 KCrash: Attempting to start /usr/lib64/drkonqi
KCrash: Attempting to start /usr/lib64/drkonqi
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, webgl, xcb.
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, webgl, xcb.
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.
Code:
$ gdbus introspect --system --dest org.freedesktop.locale1 --object-path /org/freedesktop/locale1
Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.locale1 was not provided by any .service files
FAIL
$ qdbus | grep -i org.freedesktop
org.freedesktop.secrets
org.freedesktop.ScreenSaver
org.freedesktop.PowerManagement
org.freedesktop.PowerManagement.Inhibit
org.freedesktop.Notifications
org.freedesktop.portal.Fcitx
org.freedesktop.portal.Desktop
org.freedesktop.portal.Documents
org.freedesktop.impl.portal.PermissionStore
org.freedesktop.impl.portal.desktop.gtk
org.freedesktop.impl.portal.desktop.kde
org.freedesktop.DBus
Correction: Plasma desktop is indeed searching for org.freedesktop.locale1
Last edited by walecha; 04-06-2021 at 11:55 PM.
Reason: correction
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.
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.
here us update. I can start now startplasma-wayland without libdaemon and blocaled library witch does not not want to start with error:
Code:
not a reply org.freedesktop.locale1 QDBusMessage(type=Error, service="org.freedesktop.DBus", error name="org.freedesktop.DBus.Error.ServiceUnknown", error message="The name org.freedesktop.locale1 was not provided by any .service
files", signature="s", contents=("The name org.freedesktop.locale1 was not provided by any .service files") )
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.
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 dbus-daemon session, I think you should modified the script like this:
Code:
if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
eval $(dbus-launch --sh-syntax --exit-with-session)
fi
exec /usr/bin/startplasma-wayland
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.
Code:
user 1650 0.0 0.0 143492 19984 ? Sl 18:45 0:00 /usr/lib64/startplasma-waylandsession
user 1756 57.2 0.1 388452 34144 ? Sl 18:45 0:49 /usr/lib64/kactivitymanagerd
user 1790 107 0.1 276748 49776 ? Sl 18:45 1:32 /usr/lib64/kdeconnectd
user 1805 56.1 0.2 387124 66260 ? Sl 18:45 0:48 /usr/bin/korgac
user 2188 0.0 0.0 133740 13332 ? Sl 18:46 0:00 /usr/bin/kdeinit5_shutdown
user 2190 0.0 0.0 90300 27364 ? S 18:46 0:00 /usr/lib64/drkonqi -platform wayland --appname kdeconnectd --apppath /usr/lib64 --signal 6 --pid 1790 --appversion 20.12.3 --programname KDE Connect Daemon --bugaddr
ess submit@bugs.kde.org --startupid 0
user 2191 0.0 0.0 90300 27196 ? S 18:46 0:00 /usr/lib64/drkonqi -platform wayland --appname korgac --apppath /usr/bin --signal 6 --pid 1805 --appversion 5.16.3 (20.12.3) --programname KOrganizer Reminder Daemon
--bugaddress submit@bugs.kde.org --startupid 0
user 2192 0.0 0.0 90300 27388 ? S 18:46 0:00 /usr/lib64/drkonqi -platform wayland --appname kactivitymanagerd --apppath /usr/lib64 --signal 6 --pid 1756 --startupid 0
user 2193 0.0 0.0 69100 14476 ? S 18:46 0:00 /usr/bin/kdeinit5 --suicide
user 2194 0.0 0.0 69100 6492 ? Ss 18:46 0:00 /usr/bin/kdeinit5 --suicide
user 2195 0.0 0.0 89144 27580 ? S 18:46 0:00 /usr/lib64/kf5/klauncher --fd=8
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
