Slow to start KDE side-bar: how to troubleshoot?

0BADC0DE · 2022-12-01 06:21:00

I use a side-bar to host my start menu, task manager and system tray.
It is normally displayed in a second external monitor, unless I am no the move, then it is of course displayed in the built-in display.
I never had issues with that but since some time now it is getting a lot of time to show up, about 5-10 seconds.
This happens with both 1 and 2 monitors.
This is not a big deal, of course, but just annoying.
How do I troubleshoot this?
This is my system (fully updated):

Kernel Version : 6.0.10.zen2-1
Plasma Version : 5.26.4-1
KDE Version : 22.08.3-1
Frameworks Version : 5.100.0-1
Qt5 Version : 5.15.7+kde+r6-1
Wayland Version : 1.21.0-1
Mesa Version : 22.2.3-1

Last edited by 0BADC0DE (2022-12-01 06:27:20)

seth · 2022-12-01 09:10:02

What makes you believe this is a "side-bar" issue?
Is the rest of your plasma desktop (other bars, icons, widgadgethingies) there and usable before?

V1del · 2022-12-01 09:17:09

Check the journal on whether an obvious reason for the delay shows and check/post your plasma config:

qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.dumpCurrentLayoutJS #Needs qt5-tools

do you use some non-standard theme? Maybe also some kscreen screen detection logic that gets delayed for some reason.

0BADC0DE · 2022-12-01 09:22:27

seth wrote:

What makes you believe this is a "side-bar" issue?

Because this is the only weird thing I see now.
I mean, it is related to the "side-bar" (a panel actually) for sure.
Of course the culprit could be anything in the stack.
It used to be drawn immediately after login along with the wallpaper and some icons.
I have the same single color wallpaper in both displays and some icons due to the folder view on the built-in display.
Now the side-bar is drawn with a large delay after login.

seth wrote:

Is the rest of your plasma desktop (other bars, icons, widgadgethingies) there and usable before?

It seems so.

0BADC0DE · 2022-12-01 09:30:52

V1del wrote:

Check the journal on whether an obvious reason for the delay shows and check/post your plasma config:
qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.dumpCurrentLayoutJS #Needs qt5-tools
do you use some non-standard theme? Maybe also some kscreen screen detection logic that gets delayed for some reason.

I see a number of plasmashell-related things there: but I don't know which one could be related to the behavior.
And this is the configuration.
Any hint?

Last edited by 0BADC0DE (2022-12-01 09:59:20)

seth · 2022-12-01 09:45:01

You links say "bash: plasmashell.txt: command not found" and "bash: plasmashell.json: command not found"

0BADC0DE · 2022-12-01 09:59:41

seth wrote:

You links say "bash: plasmashell.txt: command not found" and "bash: plasmashell.json: command not found"

Fixed! Wrong alias! :-/

seth · 2022-12-01 10:13:02

Same on a plasma/xorg session?

Edit: cross-ref, https://bbs.archlinux.org/viewtopic.php?id=281704

Last edited by seth (2022-12-01 10:14:39)

0BADC0DE · 2022-12-01 10:24:39

seth wrote:

Same on a plasma/xorg session?

I don't use X: I need logout and re-login. But this is my work station: cannot afford this now. Will do asap.
The other guy is on Xorg, though.

seth wrote:

Edit: cross-ref, https://bbs.archlinux.org/viewtopic.php?id=281704

Sorry, I was not ware of that...

Last edited by 0BADC0DE (2022-12-01 10:30:19)

seth · 2022-12-01 14:37:47

10s gap

dic 01 07:13:31 Feynman plasmashell[975]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
dic 01 07:13:41 Feynman plasmashell[975]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml"

Your panel doesn't look very complicated - what if you remove and readd it.
If you want to throw a bet, just remove the systray widget.

0BADC0DE · 2022-12-01 15:23:26

seth wrote:

10s gap

dic 01 07:13:31 Feynman plasmashell[975]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
dic 01 07:13:41 Feynman plasmashell[975]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml"

Your panel doesn't look very complicated - what if you remove and readd it.
If you want to throw a bet, just remove the systray widget.

The panel has been setup at the very beginning and it has worked fine so far.
Then, about complication, I "just"(tm) laid the widgets out in the panel with my mouse.
So, if any complication occurred, it must have been added by the panel editing feature.
I will try to recreate it and report back.

seth · 2022-12-01 15:42:38

seth actually wrote:

panel doesn't look very complicated

0BADC0DE · 2022-12-01 17:49:54

I removed the widgets from my panel one by one.
With an empty panel I get back the speed: login is just immediate.
Even just the clock widget is enough to trigger the "slow" behaviour.
I can also see that adding and removing widgets is a little bit unresponsive and weird.
When I put the "edit mode" on, sometimes (but not always) there is no way to click on the red trash can because it disappears as soon as I move the mouse.
I think something is wrong with the widget management. But have no way to prove it.

Movimng from Wayland to Xorg doesn't make any difference.
Adding widgets does.

Another note.
I added for convenience a menu widget as an "Application menu" to the desktop. It doesn't work well as it doesn't show the menu items.
If I switch it to "Application Launcher" then it works as expected.

Last edited by 0BADC0DE (2022-12-01 18:02:56)

seth · 2022-12-01 20:10:25

Even just the clock widget is enough to trigger the "slow" behaviour.

What about only other, not the clock widgets?
How doe the panel behave when it's horizontally aligned (top/bottom)?

0BADC0DE · 2022-12-02 07:51:34

It is not possible to test anything anymore. :-(
Now I consistently have 2 panels: 1 vertical and 1 horizontal.
Removing either one from the "Enter edit mode" doesn't help as after reboots or logout the panels are back there.
All my home dir is owned by me and with proper permissions (rw for me).
Nonetheless I cannot remove all panels any more.
In which files/dirs do these things reside?

seth · 2022-12-02 08:08:36

Inspect the journal, does plasma crash on logout?
If you kill (-15, NOT -9!) the plasmashell process and restart it, can you effectively remove the panels?

pkill plasmashell; sleep 1; plasmashell &

The configs are somewhere in ~/.config/plasma*

0BADC0DE · 2022-12-02 08:44:10

seth wrote:

Inspect the journal, does plasma crash on logout?
If you kill (-15, NOT -9!) the plasmashell process and restart it, can you effectively remove the panels?
pkill plasmashell; sleep 1; plasmashell &
The configs are somewhere in ~/.config/plasma*

I see a number of "errors" and "warnings". But figuring out which one belongs to what is a different thing.
I only see a few crashes of sddm-helper. No plasma crashes, I think.

seth · 2022-12-02 08:48:27

You "see" where and when?
You want to look at the system journal after a re-login to see the previous session.
The (current) session journal will be meaningless (potential crash not yet happened)

0BADC0DE · 2022-12-02 09:32:50

I did a few logouts and reboots this morning.
The file I put in the link is whatever my journal contains about "plasma".
I used the grep, Luke!

I did that pkill command and got new journal data back.
And got back 2 panels, despite I had removed 1.
These are two qdbus dumps:
One taken just before logging out to sddm. Only vertical panel was present.
One taken soon after logging back in. Both vertical and horizontal panel were present.
Then I removed the horizontal panel, did a logout+login and grabbed the journal. All of it (no grepping) since sometime before removing the panel.
Useless to say that after loggin back in I have got back 2 panels! :-/

Last edited by 0BADC0DE (2022-12-02 10:17:09)

seth · 2022-12-02 09:48:06

I used the grep, Luke!

0BADC0DE · 2022-12-02 10:01:42

Added some more details. See previous post.

Last edited by 0BADC0DE (2022-12-02 10:01:52)

seth · 2022-12-02 10:18:36

dic 02 10:56:41 Feynman plasmashell[16369]: The Wayland connection broke. Did the Wayland compositor die?
dic 02 10:56:41 Feynman systemd[811]: plasma-plasmashell.service: Main process exited, code=exited, status=1/FAILURE

Doesn't look like an overly clean exit to me…

w/o timestamp context it's not possible to say what happened for killing & restarting plasmashell.

0BADC0DE · 2022-12-02 10:26:57

seth wrote:

dic 02 10:56:41 Feynman plasmashell[16369]: The Wayland connection broke. Did the Wayland compositor die?
dic 02 10:56:41 Feynman systemd[811]: plasma-plasmashell.service: Main process exited, code=exited, status=1/FAILURE
Doesn't look like an overly clean exit to me…
w/o timestamp context it's not possible to say what happened for killing & restarting plasmashell.

I did a

pkill plasmashell; sleep 1; plasmashell &

If the compositor is KWin, then that message can make some sense:
plasmashell died and so KWin did.
Is there any other information I can gather?

Last edited by 0BADC0DE (2022-12-02 10:27:38)

seth · 2022-12-02 10:38:24

I did a pkill plasmashell; sleep 1; plasmashell &

Yeah, but what is logged in that situation.

If the compositor is KWin, then that message can make some sense:

No, doesn't.
Plasma is supposed to terminate, not crash out of the session.

0BADC0DE · 2022-12-02 10:48:04

seth wrote:

I did a pkill plasmashell; sleep 1; plasmashell &
Yeah, but what is logged in that situation.
If the compositor is KWin, then that message can make some sense:
No, doesn't.
Plasma is supposed to terminate, not crash out of the session.

It indeed crashed everything was running in graphics. KDE and GTK+ (like chromium).

Arch Linux

#1 2022-12-01 06:21:00

Slow to start KDE side-bar: how to troubleshoot?

#2 2022-12-01 09:10:02

Re: Slow to start KDE side-bar: how to troubleshoot?

#3 2022-12-01 09:17:09

Re: Slow to start KDE side-bar: how to troubleshoot?

#4 2022-12-01 09:22:27

Re: Slow to start KDE side-bar: how to troubleshoot?

#5 2022-12-01 09:30:52

Re: Slow to start KDE side-bar: how to troubleshoot?

#6 2022-12-01 09:45:01

Re: Slow to start KDE side-bar: how to troubleshoot?

#7 2022-12-01 09:59:41

Re: Slow to start KDE side-bar: how to troubleshoot?

#8 2022-12-01 10:13:02

Re: Slow to start KDE side-bar: how to troubleshoot?

#9 2022-12-01 10:24:39

Re: Slow to start KDE side-bar: how to troubleshoot?

#10 2022-12-01 14:37:47

Re: Slow to start KDE side-bar: how to troubleshoot?

#11 2022-12-01 15:23:26

Re: Slow to start KDE side-bar: how to troubleshoot?

#12 2022-12-01 15:42:38

Re: Slow to start KDE side-bar: how to troubleshoot?

#13 2022-12-01 17:49:54

Re: Slow to start KDE side-bar: how to troubleshoot?

#14 2022-12-01 20:10:25

Re: Slow to start KDE side-bar: how to troubleshoot?

#15 2022-12-02 07:51:34

Re: Slow to start KDE side-bar: how to troubleshoot?

#16 2022-12-02 08:08:36

Re: Slow to start KDE side-bar: how to troubleshoot?

#17 2022-12-02 08:44:10

Re: Slow to start KDE side-bar: how to troubleshoot?

#18 2022-12-02 08:48:27

Re: Slow to start KDE side-bar: how to troubleshoot?

#19 2022-12-02 09:32:50

Re: Slow to start KDE side-bar: how to troubleshoot?

#20 2022-12-02 09:48:06

Re: Slow to start KDE side-bar: how to troubleshoot?

#21 2022-12-02 10:01:42

Re: Slow to start KDE side-bar: how to troubleshoot?

#22 2022-12-02 10:18:36

Re: Slow to start KDE side-bar: how to troubleshoot?

#23 2022-12-02 10:26:57

Re: Slow to start KDE side-bar: how to troubleshoot?

#24 2022-12-02 10:38:24

Re: Slow to start KDE side-bar: how to troubleshoot?

#25 2022-12-02 10:48:04

Re: Slow to start KDE side-bar: how to troubleshoot?

Board footer